keystone relation missing in 1.29
Bug #2068770 reported by
Kevin W Monroe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CDK Addons |
Fix Released
|
Undecided
|
Adam Dyess | ||
Kubernetes Control Plane Charm |
Fix Released
|
High
|
Adam Dyess |
Bug Description
In charmed k8s 1.28, we had the ability to relate to keystone. In 1.29+ we want to provide the ability to do an upgrade from 1.28 whilst informing the admin that keystone (and other authn) should now be managed externally.
Let's include a ks-creds relations for 1.29+ to ensure upgradability with instructions on how to migrate to our new recommendations for managing authn.
Changed in charm-kubernetes-master: | |
assignee: | nobody → Adam Dyess (addyess) |
milestone: | none → 1.30 |
status: | New → In Progress |
importance: | Undecided → High |
Changed in cdk-addons: | |
status: | New → In Progress |
milestone: | none → 1.30 |
assignee: | nobody → Adam Dyess (addyess) |
Changed in cdk-addons: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
PR to main:
https:/ /github. com/charmed- kubernetes/ charm-kubernete s-control- plane/pull/ 350
Backported to release_1.30 and release_1.29.