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.

Sign up for GitHub

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

Jump to bottom

Introduction of kube-router CNI in MKE 4.0.1 #279

Open
KoryKessel-Mirantis opened this issue Jan 3, 2025 · 0 comments · May be fixed by #295
Open

Introduction of kube-router CNI in MKE 4.0.1 #279

KoryKessel-Mirantis opened this issue Jan 3, 2025 · 0 comments · May be fixed by #295
Assignees
@KoryKessel-Mirantis
Labels
Docs-A Must Do

Comments

@KoryKessel-Mirantis
Copy link
Collaborator

As first submitted by @quadespresso in https://mirantis.jira.com/browse/ENGDOCS-2573.

Support for the kube-router CNI is new as of MKE v4.0.1.

Per @vikramhh in BOP-1697, support for the kube-router CNI in v4.0.1 is limited to fresh installs only. This means that if a v4.0.1 cluster is already running with the Calico CNI, it is not possible to migrate the MKE4 config from using the Calico CNI to using the kube-router CNI.

To attempt such a CNI migration is unsupported in v4.0.1. This also applies to any cluster upgraded from v4.0.0 → v4.0.1.
@KoryKessel-Mirantis KoryKessel-Mirantis added the Docs-A Must Do label Jan 3, 2025
@KoryKessel-Mirantis KoryKessel-Mirantis self-assigned this Jan 3, 2025
@KoryKessel-Mirantis KoryKessel-Mirantis linked a pull request Jan 31, 2025 that will close this issue
CNI Tigera Operator content #295
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KoryKessel-Mirantis KoryKessel-Mirantis

Labels
Docs-A Must Do
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

CNI Tigera Operator content Mirantis/mke-docs
1 participant
@KoryKessel-Mirantis