Skip to content

Update istio-deploy-ingress.md#204

Closed
pratiksharma-dev wants to merge 1 commit intoMicrosoftDocs:mainfrom
pratiksharma-dev:patch-1
Closed

Update istio-deploy-ingress.md#204
pratiksharma-dev wants to merge 1 commit intoMicrosoftDocs:mainfrom
pratiksharma-dev:patch-1

Conversation

@pratiksharma-dev
Copy link
Copy Markdown

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.
@prmerger-automator
Copy link
Copy Markdown
Contributor

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

@learn-build-service-prod
Copy link
Copy Markdown
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
Copy Markdown
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

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2025

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@v-dirichards
Copy link
Copy Markdown
Contributor

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

Thanks!

@github-actions github-actions Bot removed the inactive label May 2, 2025
@github-actions
Copy link
Copy Markdown

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@v-dirichards
Copy link
Copy Markdown
Contributor

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

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

@shashankbarsin
Copy link
Copy Markdown
Contributor

@pratiksharma-dev - any spec persisted to etcd is treated the same by the reconciler, irrespective of client/command used to apply that spec. annotations were previously not allowed on ingress entirely, with the documented annotations, only edits to these selective set of annotations were allowed later.

@github-actions github-actions Bot removed the inactive label May 28, 2025
@v-dirichards
Copy link
Copy Markdown
Contributor

#please-close This edit is not accepted.

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