Describe the bug
When kubernetes-secret-generator controller is explicitly configured to use some encoding different from base64 then the secrets generated from custom resources with no encoding field specified are still created with base64 encoding.
To Reproduce
Deploy kubernetes-secret-generator controller with the parameter to use e.g. hex encoding by default.
Expected behavior
The expected behaviour is similar to the secrets which items are generated with the annotations - the default encoding is used if no secret-generator.v1.mittwald.de/encoding annotation is specified. E.g. this is the password generated in the secret generated with annotations:
Describe the bug When
kubernetes-secret-generator
controller is explicitly configured to use some encoding different frombase64
then the secrets generated from custom resources with noencoding
field specified are still created withbase64
encoding.To Reproduce
kubernetes-secret-generator
controller with the parameter to use e.g.hex
encoding by default.encoding
specified.hex
encoding which is configured for controller):Expected behavior The expected behaviour is similar to the secrets which items are generated with the annotations - the default encoding is used if no
secret-generator.v1.mittwald.de/encoding
annotation is specified. E.g. this is the password generated in the secret generated with annotations:Environment: