You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm going through the process of replacing manually created secrets in ns1-ns4 with the Reflector managed versions. My process has been:
Add a new namespace to reflection-allowed-namespaces (Reflector will do nothing as the destination already exists)
Delete existing destination secret
Wait for Reflector to replace the secret, but it never does
Restart the Reflector pod, which causes the secret to be reflected
Is this how Reflector works? I assumed that it would always be "watching" the destination secrets on a short interval - essentially some form of drift-detection, but it looks like some operations only happen once or on startup.
I'm using Helm chart v9.1.7 with the same image version.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a secret in a source namespace with these annotations:
I'm going through the process of replacing manually created secrets in
ns1
-ns4
with the Reflector managed versions. My process has been:reflection-allowed-namespaces
(Reflector will do nothing as the destination already exists)Is this how Reflector works? I assumed that it would always be "watching" the destination secrets on a short interval - essentially some form of drift-detection, but it looks like some operations only happen once or on startup.
I'm using Helm chart v9.1.7 with the same image version.
Beta Was this translation helpful? Give feedback.
All reactions