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

2.10 deprecate rancher istio #4979

Draft
wants to merge 2 commits into
base: dev-v2.10
Choose a base branch
from

Conversation

diogoasouza
Copy link
Contributor

@diogoasouza diogoasouza commented Jan 17, 2025

This PR is just a draft. We plan to deprecate Rancher Istio:

  • Rancher 2.11: Deprecation announcement
  • Rancher 2.12: Deprecation configuration
  • Rancher 2.13: It won't be included

📚 SUSE Rancher Prime - Deprecation Policy

Copy link

Validation steps

  • Ensure all container images have repository and tag on the same level to ensure that all container images are included in rancher-images.txt which are used by airgap customers.
  Ex:-
    longhorn-controller:
      repository: rancher/hardened-sriov-cni
      tag: v2.6.3-build20230913
  
  • Add a 👍 (thumbs up) reaction to this comment once done. CI won't pass without this reaction to the github-action bot's latest validation comment.
  • Approve the PR to run the CI check.

@@ -11,9 +12,10 @@ annotations:
catalog.cattle.io/requests-memory: 2314Mi
catalog.cattle.io/type: cluster-tool
catalog.cattle.io/ui-component: istio
catalog.cattle.io/upstream-version: 1.23.2
catalog.cattle.io/upstream-version: 1.24.1
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is unrelated, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's just updating the upstream version annotation and has no impact on any functionality

@recena
Copy link
Collaborator

recena commented Jan 17, 2025

@diogoasouza This change will go against 2.12 when it is available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants