Open shamil opened 5 years ago
Hi!
Thanks for reporting this.
Unfortunately API documentation does not mention that this field is immutable.
I would be happy to add some validation of EncryptedSecret
in this regard and I am actually planning to do that in future.
Currently Kubernetes - Open API to be precise - is not capable of validating immutable fields for custom resource objects. Yet it is possible to do that via a validating webhook.
Maybe having an optional param in EncryptedSecret
resource to force recreate the secret, this can help and let people decide what to do in such cases;
Hi,
When a secret type changes, let's say from
Opaque
tokubernetes.io/tls
, secreter failing to update the secret.I think it should handle such changes, and recreate secret if needed. Or make
EncryptedSecret
to honortype
field as immutable same as insecret
resources