Bartosz Jakubski

yeah, can't manage it with TF (without hacks to patch), can't use helm (does not want to modify resources it does not own). I'm trying (also hackish) solution to use...

Hi @pintohutch @shpml described the issue nicely. I'll only add that it is not easily possible to manage OperatorConfig with helm too due to the same issue - this object...

I'm on 0.3.1 and the `.managedAlertManager` field is present and set in OperatorConfig (although we didn't set it): ``` kubectl get -ngmp-public operatorconfigs.monitoring.googleapis.com config -ojsonpath='{.managedAlertmanager}' ``` returns ``` {"configSecret":{"key":"alertmanager.yaml","name":"alertmanager"}}% ```...

FWIW this problem was only present in couple of GKE clusters where we were making changes (out of ~15). In clusters where it happened workoaround of: # kubectl edit operatorconfig...

@spinnakerbot remove-label stale