Contact details
No response
Is your feature request related to a problem? Please describe
I need to add new secret to the kubernetes cluster in SIMPIPE. I can create one from commandline.
However adding secret from frontend limits the possibilities to creating one, storing the secret as a dockerconfigjson:
$ kubectl get secret mysecret -o yaml
$ echo b64-encoded-string | base64 --decode
{"auths":{"https://myserver.com":{"username":"yolo","password":"yolo123","auth":"eW9sbzp5b2xvMTIz"}}}
This is the correct way to store a secret for a docker registry (so that kubernetes correctly authenticates agains the specified docker registry) Kubernetes | pull image from private registry
However, if I'd like to create another type of secret you have to follow other format: kubernetes | secrets
Describe the solution you'd like
First of all. The name "secret" in the frontend is misleading.
Secrets in Kubernetes can have several formats and can be used for different purposes. API-tokens, image registry credentials, opaque secrets, etc.
It would be good to provide a proper name that represents that the current secrets in SIMPIPE frontend, are docker image registry secrets.
It would be good to be able to add opaque type secrets withg key-value pairs. These can easily be referenced and used in pipelines.
Describe alternatives you've considered
No response
Additional context
No response
Contact details
No response
Is your feature request related to a problem? Please describe
I need to add new secret to the kubernetes cluster in SIMPIPE. I can create one from commandline.
However adding secret from frontend limits the possibilities to creating one, storing the secret as a dockerconfigjson:
This is the correct way to store a secret for a docker registry (so that kubernetes correctly authenticates agains the specified docker registry) Kubernetes | pull image from private registry
However, if I'd like to create another type of secret you have to follow other format: kubernetes | secrets
Describe the solution you'd like
First of all. The name "secret" in the frontend is misleading.
Secrets in Kubernetes can have several formats and can be used for different purposes. API-tokens, image registry credentials, opaque secrets, etc.
It would be good to provide a proper name that represents that the current secrets in SIMPIPE frontend, are docker image registry secrets.
It would be good to be able to add opaque type secrets withg key-value pairs. These can easily be referenced and used in pipelines.
Describe alternatives you've considered
No response
Additional context
No response