Changes to Azure resource groups/networks after deployment should be reflected in cloud-config.conf
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Azure Integrator Charm |
Fix Released
|
High
|
George Kraft | ||
| Kubernetes Control Plane Charm |
Fix Released
|
High
|
George Kraft | ||
| Kubernetes Worker Charm |
Fix Released
|
High
|
George Kraft | ||
Bug Description
Changes to azure-integrator charm configuration for the following configuration is not reflected in the running kubernetes-master /var/snap/
- subnetName
- vnetName
- vnetResourceGroup
- vnetSecurityGroup
While this is documented as not being able to be updated after deployment, we have found environments where subnets are migrated to different vnets or vnets are moved to shared resource groups after deployments are unable to support creation of loadbalancers in the changed network topology.
I've found while working with a customer deployment that making the modifications manually to the cloud-config.conf and restarting the snap service kube-controller
It would be very helpful if changes to this charm could trigger the appropriate cloud-config.conf changes and recycle the controller-manager service on kubernetes-master units.
| Drew Freiberger (afreiberger) wrote Re: Changes to resource groups/networks after deployment should be reflected in kubernetes-master cloud-config.conf | #1 |
| description: | updated |
| summary: |
- If operator changes config after deployment, charm should enter blocked - state and refuse to config-change + Changes to resource groups/networks after deployment should be reflected + in kubernetes-master cloud-config.conf |
| George Kraft (cynerva) wrote | #2 |
| Changed in charm-azure-integrator: | |
| importance: | Undecided → Medium |
| Changed in charm-kubernetes-master: | |
| importance: | Undecided → Medium |
| Changed in charm-azure-integrator: | |
| status: | New → Triaged |
| Changed in charm-kubernetes-master: | |
| status: | New → Triaged |
| summary: |
- Changes to resource groups/networks after deployment should be reflected - in kubernetes-master cloud-config.conf + Changes to Azure resource groups/networks after deployment should be + reflected in cloud-config.conf |
| Changed in charm-kubernetes-worker: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Aymen Frikha (aym-frikha) wrote | #3 |
| Aymen Frikha (aym-frikha) wrote | #4 |
| Changed in charm-azure-integrator: | |
| importance: | Medium → High |
| Changed in charm-kubernetes-master: | |
| importance: | Medium → High |
| Changed in charm-kubernetes-worker: | |
| importance: | Medium → High |
| Changed in charm-azure-integrator: | |
| assignee: | nobody → George Kraft (cynerva) |
| Changed in charm-kubernetes-worker: | |
| assignee: | nobody → George Kraft (cynerva) |
| Changed in charm-kubernetes-master: | |
| assignee: | nobody → George Kraft (cynerva) |
| George Kraft (cynerva) wrote | #5 |
| Changed in charm-azure-integrator: | |
| status: | Triaged → In Progress |
| Changed in charm-kubernetes-master: | |
| status: | Triaged → In Progress |
| Changed in charm-kubernetes-worker: | |
| status: | Triaged → In Progress |
| Changed in charm-azure-integrator: | |
| milestone: | none → 1.26 |
| Changed in charm-kubernetes-master: | |
| milestone: | none → 1.26 |
| Changed in charm-kubernetes-worker: | |
| milestone: | none → 1.26 |
| Changed in charm-azure-integrator: | |
| status: | In Progress → Fix Committed |
| Changed in charm-kubernetes-worker: | |
| status: | In Progress → Fix Committed |
| Changed in charm-kubernetes-master: | |
| status: | In Progress → Fix Committed |
| Changed in charm-azure-integrator: | |
| status: | Fix Committed → Fix Released |
| Changed in charm-kubernetes-master: | |
| status: | Fix Committed → Fix Released |
| Changed in charm-kubernetes-worker: | |
| status: | Fix Committed → Fix Released |
To note, the relation data from azure-integrator toward it's clients is not updated when the configuration is changed with juju config.