Operations performed on cpServer in environment.yaml file are not reflected
Operations such as add/remove/comment/uncomment performed on cpServer in cloudscale-values.yaml file are not reflected even after applying them. The reasons and solutions for the same are as follow:
Check if the action is reflected in cpServer CRO (Custom Resource Object) by using the following command:
kubectl describe cpserver n $ENVIRONMENT_NAMESPACE
If changes are not reflected then , check environment operator logs and if changes are reflected then follow the next steps.
Check if the flexsnap operator is running by using the following command:
kubectl get pods -n $OPERATOR_NAMESPACE | grep flexsnap-operator | awk '{printf $1" " }
The flexsnap operator is running and is already processing the event (Update, Upgrade, Create, Delete).
To check logs of running operator, use the following command:
kubectl logs -f $(kubectl get pods -n $OPERATOR_NAMESPACE | grep flexsnap-operator | awk '{printf $1" " }')
If you still want to go ahead with new action, you can stop the processing of the current event so that the new events are processed. To do so delete the flexsnap operator pod using the following command:
kubectl delete pod $(kubectl get pods -n $OPERATOR_NAMESPACE | grep flexsnap-operator | awk '{printf $1" " }')
This will re-create the flexsnap-operator pod which will be ready to serve new events.
Note:
The newly created pod might have missed the event which was performed before re-creation of pod. In this case you may have to reapply
cloudscale-values.yaml.