-
Notifications
You must be signed in to change notification settings - Fork 21.9k
Document limitations for shared Application Gateway usage #127861
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?
Conversation
There is no defined limitation on multiple AGIC usage, but there is also no guidance on how to achieve it. Added limitations for sharing an Application Gateway across multiple AGIC instances, including YAML configuration example and notes on hostname/path management.
|
Learn Build status updates of commit 8ba9de3: 💡 Validation status: suggestions
articles/application-gateway/ingress-controller-install-existing.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
@microsoft-github-policy-service agree company="Microsoft" |
|
@jamesonhearn : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There is no defined limitation on multiple AGIC usage, but there is also no guidance on how to achieve it.
Added limitations for sharing an Application Gateway across multiple AGIC instances, including YAML configuration example and notes on hostname/path management.