-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Documentation: add migration document #23751
Conversation
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.
Contents seem all good to me, I just have a few minor comments on formatting (plus nits on case and punctuation, for consistency).
For you playing along at home: this won't work until #23743 is merged. |
Hah. #23743. Updated. |
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.
Overall I think it's fine for us to include this in the documentation. I definitely think that describing this process as simple would be a mistake. There will always be edge cases that make this difficult to manage.
b43e161
to
ffed2a7
Compare
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.
Looks good from my side. Thanks!
Need one more PR to merge, then this doc should be ready to go: #24009 |
7f678f1
to
15f81db
Compare
13febd1
to
d44fb6f
Compare
I made a few small changes. @mauilion, would you mind giving this a quick read? Then, we can merge this. |
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.
looks great with a minor nit.
This document explains the basics of how to migrate Cilium on a running cluster. It includes a copy-and-paste example for migrating off of Flannel. It utilizes the per-node-configuration override feature to gradually roll out Cilium. It configures a hybrid cluster with multiple overlays so that all pods have full connectivity until migration is complete. Signed-off-by: Casey Callendrello <cdc@isovalent.com> Co-authored-by: Duffie Cooley <dcooley@isovalent.com> Co-authored-by: Quentin Monnet <qmonnet+github@qoba.lt>
@mauilion updated, thanks! |
docs PR with approvals, marking as ready-to-merge |
@squeed , are these docs live anywhere docs.cilium.io? I recall there was a conversation on how this is behind a feature in Cilium v1.13.1 (or maybe 1.13.2?). I was trying to find them but no luck |
@mohahmed13 It is rendered at https://docs.cilium.io/en/latest/installation/k8s-install-migration/#migrating-a-cluster-to-cilium. @squeed Could we backport it to v1.13? I see it relies on the per-node configurations but that looks available on v1.13: https://docs.cilium.io/en/stable/configuration/per-node-config/#per-node-configuration. |
Tagged for backport, good catch. |
This document explains the basics of how to migrate Cilium on a running cluster. It includes a copy-and-paste example for migrating off of Flannel.
It utilizes the per-node-configuration override feature to gradually roll out Cilium. It configures a hybrid cluster with multiple overlays so that all pods have full connectivity until migration is complete.