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
Is it possible that the secret created / owned / managed by the Sealed Secrets Controller is protected against PATCH operations on the target K8S cluster so that any modification must be done via the SealedSecret object? Or is there a reason why this would not make any sense?
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
-
Is it possible that the secret created / owned / managed by the Sealed Secrets Controller is protected against PATCH operations on the target K8S cluster so that any modification must be done via the SealedSecret object? Or is there a reason why this would not make any sense?
Beta Was this translation helpful? Give feedback.
All reactions