It's currently mandatory to use a SecretClass, which might make sense in some cases, but for many cases it's an unnecessary hoop users have to jump through. They have to create a dummy SecretClass just to point it to the Secret. We should at least provide the option to simply use a Secret instead.
Current state:
spec:
credentials:
secretClass: s3-credentials-class # mandatory
scope: {} # optionalIdea from @sbernauer :
spec:
credentials:
secret:
name: my-secret # mandatory
accessKeyKey: accessKey # defaults to accessKey
secretKeyKey: secretKey # defaults to secretKey
# OR
secretClass:
name: s3-credentials-class # mandatory
scope: {} # optional
It's currently mandatory to use a
SecretClass, which might make sense in some cases, but for many cases it's an unnecessary hoop users have to jump through. They have to create a dummySecretClassjust to point it to theSecret. We should at least provide the option to simply use aSecretinstead.Current state:
Idea from @sbernauer :