-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random failure publishing new secrets on changes #29
Comments
Hey @mkherlakian, thanks for reporting this! When the operator is in the "stuck" state, could you share the output from Did you check out the operator manager logs with this script? https://github.com/DopplerHQ/kubernetes-operator/blob/main/tools/operator-logs.sh They're a bit verbose but often tell the whole story. |
Hi @mkherlakian, Are you still running into this issue? |
Hi @nmanoogian, AS it turns out I had to do a deployment in a namespace that we don't use often, and sure enough that one was not picking up the changes. Here's a
Getting the logs now. |
Thanks, @mkherlakian! Any luck on getting those logs? Things are looking normal from the CRD describe. |
We've successfully deployed the Doppler Operator to our environments a little over 2 months ago.
We're noticing however that while everything works as it should post-deployment (we can change a secret in our config, and run
kubectl describe secrets --selector=secrets.doppler.com/subtype=dopplerSecret
, we will see the changes almost immediately), after a while (days) the operator doesn't seem to pick up the new secrets anymore.In order to fix this, we have to delete the CRD for that environment and recreate it.
We dug through the logs, but didn't notice anything out of the ordinary.
Happy to provide more info/details/logs that would help in diagnosing this. We are on GKE, k8s 1.23.
The text was updated successfully, but these errors were encountered: