missing StorageClass with juju.io/workload-storage annotation when using AWS integrator
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CDK Addons |
Triaged
|
Wishlist
|
Unassigned | ||
Kubernetes Control Plane Charm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Each node provisioned by a CDK deployment (master or worker) should set a node label:
juju.io/
where cloud is one of "gce", "ec2", "azure", "openstack"
I think this was meant to be done when the integrator charm was related to the master/worker charms.
Juju needs this information to detect the underlying cloud. I am sure this was working since Juju used to not need the --cloud option when using add-k8s.
I also thought CDK would create a storage class with the juju.io/
so maybe there's an issue elsewhere?
I deployed CDK like so:
$ juju deploy charmed-kubernetes --overlay aws-overlay.yaml --trust
Is this a regression or I am doing something wrong? The expectation is that after deploying CDK and relating to the relevant integrator charm, juju add-k8s should Just Work. Node labels and a suitable storage class are needed for this to happen.
Changed in cdk-addons: | |
importance: | Undecided → Wishlist |
Changed in charm-kubernetes-master: | |
importance: | Undecided → Wishlist |
Changed in cdk-addons: | |
status: | New → Triaged |
Changed in charm-kubernetes-master: | |
status: | Confirmed → Triaged |
We already have an open issue regarding the juju.io/cloud node label. Please direct all further discussion of that here: https:/ /bugs.launchpad .net/charm- kubernetes- worker/ +bug/1830119
Let's focus this issue on the StorageClass and juju.io/ workload- storage annotation side of things.