GitLab

Given:

• a deployed OAS cluster

• a change to i.e. the prometheus-config

• an upgrade of your cluster using python3 -m openappstack oas.varac.net install --ansible-param='--tags=prometheus' The secret prometheus-settings in namespace oas contains the new config:

  kubectl view-secret -n oas prometheus-settings values.yaml

But the configmap prometheus-server didn't update, see the latest timestamp:

kubectl -n oas get cm prometheus-server -o jsonpath='{range .metadata.managedFields[*]}{.operation}{"\t"}{.time}{"\n"}{end}'                     

In order to update this configmap we need to force a helm upgrade for prometheus. Because there are no git changes which the helm-operator can act upon, there's no other way than to restart helm-operator pod:

kubectl -n oas delete pods -l 'app in (helm-operator)                                                                                            

In the helm-operator FAQ there's a section about Notifying the Helm Operator about Git changes, but in this case there's no git change.

I wonder how we can deal with this the best way. Should we trigger a helm-operator pod deletion every time we update the app secrect ?