-
Notifications
You must be signed in to change notification settings - Fork 4.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
Fix cilium etcd migration #9451
Fix cilium etcd migration #9451
Conversation
|
||
if err := b.buildBPFMount(c); err != nil { | ||
return err | ||
for _, cluster := range b.Cluster.Spec.EtcdClusters { |
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.
Perhaps move this to a new method on KopsModelContext
?
Co-authored-by: John Gardiner Myers <[email protected]>
/lgtm |
/assign @rifelpet |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus, rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…1-origin-release-1.18 Automated cherry pick of #9451: Deploy cilium etcd credentials if the cilium cluster
This PR fixes two issues:
etcdManaged
instead of testing for the the existence of the cilium cluster making a graceful migration from CRD to etcd impossible.This PR also adds some documentation around migrating to etcd and about migrating to/from nodeport.
Fixes #9448
Fixes #9446