Update istio-deploy-ingress.md #204
Conversation
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
bot
requested review from
shashankbarsin and
chasedmicrosoft
|
@pratiksharma-dev : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit a25ac60: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
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. |
|
@shashankbarsin - Could you review this proposed update to your article and enter Thanks! |
|
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. |
|
@shashankbarsin Can you review this old PR and determine whether it needs to be closed or merged? @MicrosoftDocs/public-repo-pr-review-team |
|
@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. |
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 usingK9sandkubectl 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.