Skip to content

Update istio-deploy-ingress.md #204

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

Conversation

pratiksharma-dev
Copy link

One of my customers was trying to provision istio ingress gateway in a custom subnet, but the annotations kept getting overwritten. They spent nearly two hours troubleshooting the issue before I stepped in and resolved it by updating the configuration using kubectl apply, which worked successfully. The customer initially attempted to modify the annotations using K9s and kubectl edit, but those changes didn’t persist and were overwritten by the controller. Based on their experience, they suggested that the documentation should explicitly call out this behavior to help others avoid similar confusion.

One of my customers was trying to provision istio ingress gateway in a custom subnet, but the annotations kept getting overwritten. They spent nearly two hours troubleshooting the issue before I stepped in and resolved it by updating the configuration using kubectl apply, which worked successfully. The customer initially attempted to modify the annotations using K9s and kubectl edit, but those changes didn’t persist and were overwritten by the controller. Based on their experience, they suggested that the documentation should explicitly call out this behavior to help others avoid similar confusion.
Copy link
Contributor

@pratiksharma-dev : 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 a25ac60:

✅ Validation status: passed

File Status Preview URL Details
articles/aks/istio-deploy-ingress.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@shashankbarsin

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

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.

3 participants