-
Notifications
You must be signed in to change notification settings - Fork 21.8k
add limitation for AGIC #126586
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?
add limitation for AGIC #126586
Conversation
add limitation for externalname service
@fangzj1991 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit 7c5ad4c: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
@greg-lindsay - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
@fangzj1991 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
@greg-lindsay Could you review this proposed update to your article and enter Thanks! |
Can you review this old PR and determine whether it needs to be closed or merged? @MicrosoftDocs/public-repo-pr-review-team |
add limitation for externalname service:
Azure/application-gateway-kubernetes-ingress#1567 (comment)
I notice several situations that user use externalname service as AGIC backend, although they can set hostname in AG manually but after AGIC pod restart it will revert and the configuration cannot load correctly.