Feature request: Allow cdk addons container tag to be specified instead of forcing #latest
Bug #1841789 reported by
Ed Stewart
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes Control Plane Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
The container image path for cdk addons (which includes the external openstack cloud provider now for example) is currently always set pull the latest tagged container, eg:
image: image-registry.
Although we can override the registry used via a juju config property, we cannot override the "latest" tag.
This is necessary in order to pin environments to a specific container version and allow existing environments to be recreated.
A new juju config property is proposed - cdkaddons-tag which defaults to 'latest'
Revision history for this message
| Lorenzo Cavassa (lorenzo-cavassa) wrote | #1 |
| Changed in charm-kubernetes-master: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
This is related with a possible way to run a local/private registry with date snapshots, to have some CDK environments pointing to one of these snapshots and others pointing to another.
If there is not a way to change this tag, it means to have to maintain multiple registries rather than using the snapshotting functionality in the one registry.