Skip to content
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

Remove support for disable-external-name-alias annotation #1064

Open
11 of 17 tasks
strekm opened this issue Oct 9, 2024 · 0 comments
Open
11 of 17 tasks

Remove support for disable-external-name-alias annotation #1064

strekm opened this issue Oct 9, 2024 · 0 comments
Assignees
Labels
area/service-mesh Issues or PRs related to service-mesh kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@strekm
Copy link
Collaborator

strekm commented Oct 9, 2024

Description

Istio discontinues support for ENABLE_EXTERNAL_NAME_ALIAS on main branch that will be released with 1.24 release. As a consequence Istio module will discontinue disable-external-name-alias annotation. Remove support for annotation and make sure that ENABLE_EXTERNAL_NAME_ALIAS is set to default value.

Motivation

Remove functionality not supported by Istio

TODOs:

  • remove code which reacts to the annotation presence and applies the env var
  • adjust tests
  • append RN
  • remove stale docs

ACs:

  • disable-external-name-alias annotation set on Istio CR does not change default value
  • disable-external-name-alias annotation is ignored by Istio module
  • ENABLE_EXTERNAL_NAME_ALIAS is removed from IstioOperator file
  • disable-external-name-alias annotation is removed from documentation
  • provide user friendly release notes

PRs:

DoD:

  • Provide unit and integration tests.
  • Provide documentation.
  • Verify if the solution works for both open-source Kyma and SAP BTP, Kyma runtime.
  • If you changed the resource limits, explain why it was needed.
  • If the default configuration of Istio Operator has been changed, you performed a manual upgrade test to verify that the change can be rolled out correctly.
  • Verify that your contributions don't decrease code coverage. If they do, explain why this is the case.
  • Add release notes.

Attachments

@strekm strekm added kind/feature Categorizes issue or PR as related to a new feature. area/service-mesh Issues or PRs related to service-mesh labels Oct 9, 2024
@strekm strekm added this to the 1.10.0 milestone Oct 9, 2024
@videlov videlov self-assigned this Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/service-mesh Issues or PRs related to service-mesh kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

5 participants