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
Fix Helm Broker port names in services to comply with Istio convention #13065
Fix Helm Broker port names in services to comply with Istio convention #13065
Conversation
/retest |
✔️ 🥰 Documentation preview ready! 🥰 🔨 Explore the source changes: b847beb 🔍 Inspect the deploy log: https://app.netlify.com/sites/kyma-project-docs-preview/deploys/61f12f80d48b0a0007729b84 😎 Browse the preview: https://deploy-preview-13065--kyma-project-docs-preview.netlify.app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
given helm broker is deprecated and will be completely removed from kyma, I would like to propose we don't touch it unless absolutely necessary.
@wozniakjan our motivation is to fix all istioctl analyze warnings/infos and to use that in command in pipeline. i wouldn't say this change is harmful or dangerous in any way, more i would say it's cosmetics |
/test pre-main-kyma-gardener-azure-alpha-prod |
@mjakobczyk: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Description
We should follow official Istio documentation about port naming convention. After editing both services there is a similar spec which indicates that the used protocol is TCP.
Changes proposed in this pull request:
helm-broker-etcd-stateful
service to include protocol prefixhelm-broker-etcd-stateful-client
service to include protocol prefixRelated issue(s)
See: #11686