Changes to Azure resource groups/networks after deployment should be reflected in cloud-config.conf

Bug #1915557 reported by Drew Freiberger
10
This bug affects 1 person
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/kube-controller-manager/common/cloud-config.conf.

- 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-manager.daemon does affect the changes necessary to allow for loadbalancer deployment along with the addition of a securityGroupResourceGroup as noted in lp#1915560.

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.

Revision history for this message
Drew Freiberger (afreiberger) wrote : Re: Changes to resource groups/networks after deployment should be reflected in kubernetes-master cloud-config.conf

To note, the relation data from azure-integrator toward it's clients is not updated when the configuration is changed with juju config.

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
Revision history for this message
George Kraft (cynerva) wrote :

Added kubernetes-worker because it also has an azure cloud-config that may need to be updated too.

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
Revision history for this message
Aymen Frikha (aym-frikha) wrote :

Also changes to the azure account password is not reflected in the cloud-config.conf.
The only workaround is to remove and re-add the relation with kubernetes-master.
It's due to that function: https://github.com/juju-solutions/charm-azure-integrator/blob/master/reactive/azure.py#L56 that is only triggered at the initiation of the relation.

Revision history for this message
Aymen Frikha (aym-frikha) wrote :

subscribed ~field-high

George Kraft (cynerva)
Changed in charm-azure-integrator:
importance: Medium → High
Changed in charm-kubernetes-master:
importance: Medium → High
Changed in charm-kubernetes-worker:
importance: Medium → High
George Kraft (cynerva)
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)
Revision history for this message
George Kraft (cynerva) wrote :
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
Adam Dyess (addyess)
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 post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.