UMA agent upgrade has failed using the helm approach as below, resulting lack of metrics:
helm upgrade uma . -n dx-uma -f values.yamlRelease "uma" has been upgraded. Happy Helming!NAME: umaLAST DEPLOYED: ###NAMESPACE: dx-umaSTATUS: deployedREVISION: 2TEST SUITE: None
Causing issues with deployments and finally pods:
apmia-http-collector-5c9547d5f4-x4f8l 0/1 CreateContainerConfigError 0 9m1scluster-performance-prometheus-64659dbfd-4bx77 0/1 CreateContainerConfigError 0 9m1s
The following events are logged for both:
Warning Failed 8m50s (x8 over 10m) kubelet Error: couldn't find key agentNaming.deployment.httpCollector.host in ConfigMap dx-uma/caaiops-config-common Warning Failed 5m18s (x8 over 6m44s) kubelet Error: couldn't find key agentNaming.deployment.httpCollector.host in ConfigMap dx-uma/caaiops-config-common
Rollback the runbook to previous version by executing command shown below:
helm rollback uma --namespace dx-umaRollback was a success! Happy Helming!
Execute the upgrade without adding "-f values.yaml" as below:
helm upgrade uma . -n dx-umaRelease "uma" has been upgraded. Happy Helming!NAME: umaLAST DEPLOYED: Wed Jul 9 12:38:25 2025NAMESPACE: dx-umaSTATUS: deployedREVISION: 4TEST SUITE: None
As a result, your UMA agent will be updated without any issues.