reboot breaks microk8s deployments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Thomas Miller |
Bug Description
As reported in microk8s
https:/
Oct 05 13:30:10 imsdev microk8s.
https:/
https:/
We need to figure out what juju might do to allow a change in IP address. Ideally there'd be something we could look a to make Juju aware of the host microk8s address and propagate updates like we do for controller IP addresses via the peer grouper.
Changed in juju: | |
milestone: | none → 2.8.5 |
Changed in juju: | |
milestone: | 2.8.5 → 2.8.6 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Have narrowed the problem down. I am currently adding a negation label selector to the admission model so that the agent can at least start.