charm cannot go active without a CNI configured/related
Bug #2009525 reported by
Stone Preston
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes Control Plane Charm |
Fix Released
|
High
|
Stone Preston | ||
Kubernetes Worker Charm |
Fix Released
|
High
|
George Kraft |
Bug Description
kcp cannot go active without a CNI configured or provided via relation. This was a problem for CAPI development as a CNI is forbidden as part of the bootstrap process, and is expected to be installed by the user after the workload cluster is created.
A config option (ignore-
https:/
Changed in charm-kubernetes-master: | |
milestone: | 1.26+ck3 → 1.27 |
Changed in charm-kubernetes-worker: | |
status: | In Progress → Fix Committed |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-worker: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
PR for kubernetes-worker: https:/ /github. com/charmed- kubernetes/ charm-kubernete s-worker/ pull/137