Skip to content

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

fangzj1991
Copy link

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.

add limitation for externalname service
Copy link
Contributor

@fangzj1991 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 7c5ad4c:

✅ Validation status: passed

File Status Preview URL Details
articles/application-gateway/ingress-controller-overview.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-regandowner
Copy link
Contributor

@greg-lindsay - Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Apr 18, 2025
Copy link
Contributor

@fangzj1991 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@v-ccolin
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

@greg-lindsay Could you review this proposed update to your article and enter #sign-off in a comment if it's ready to merge?

Thanks!

@v-dirichards
Copy link
Contributor

@greg-lindsay

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants