-
Bug
-
Resolution: Done
-
Blocker
-
OSC 1.5.z, OSC 1.4.0
-
None
-
False
-
-
False
-
-
-
3
-
HCIDOCS 2024#5, HCIDOCS 2024#6
-
2
-
Moderate
Users can't update the config map (such as instance sizes) without restarting the daemonset, which results in recreating peer pods.
Need to add not to this effect in docs.
From KATA bug comments
Pradipta: "Dynamic changes to the peer-pods-cm configMap is not supported. The peerpodconfig-ctrl-caa-daemon daemonset needs to be started after changing the peer-pods-cm configMap. Note that restarting the daemonset will result in the (peer) pods being recreated"
From Cameron:
"I just noticed this in the internal docs:
If you need to modify any of the parameters in peer-pods-cm and peer-pods-secret object you can follow these steps
Change the values in the respective yaml files
Deploy the files using oc apply -f <yaml-file>
Restart the cloud-api-adaptor pods by running the following command:
oc set env ds/peerpodconfig-ctrl-caa-daemon -n openshift-sandboxed-containers-operator REBOOT="$(date)"
So seems like this is just a docs issue bccause I can't find it in the published docs."
- duplicates
-
KATA-2964 unable to update AZURE_INSTANCE_SIZES without restarting peerpod controller and webhook
- Closed
- mentioned on