-
Notifications
You must be signed in to change notification settings - Fork 21.7k
Alternate Fix for Ingress #126594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Alternate Fix for Ingress #126594
Conversation
There is always a requirement to route the Ingress traffic without using an Azure Firewall and DNAT rule. This solution is not available in any document. Hence I have added the option to help users to use Load Balancer for incoming traffic and also the alternate solution as Application Gateway
I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer. |
Learn Build status updates of commit 29fa32f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
@anandazaugust Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks! #label:"aq-pr-triaged" |
@anandazaugust please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
There is always a requirement to route the Ingress traffic without using an Azure Firewall and DNAT rule. This solution is not available in any document. Hence I have added the option to help users to use Load Balancer for incoming traffic and also the alternate solution as Application Gateway