What problem does this solve?
Currently, if someone runs k8s-operator outside GKE, there's no native way to give access to a private Docker registry. One workaround is to use e.g. ClusterSecret operator on top, but it would be nice if we could have the flexibility to do more generic configuration.
Proposed solution
We may want to look into supporting additional fields part of ChallengeInstance:
- ConfigMap
- Secret
- PersistentVolumeClaim
Workarounds or alternatives
No response
What problem does this solve?
Currently, if someone runs k8s-operator outside GKE, there's no native way to give access to a private Docker registry. One workaround is to use e.g. ClusterSecret operator on top, but it would be nice if we could have the flexibility to do more generic configuration.
Proposed solution
We may want to look into supporting additional fields part of ChallengeInstance:
Workarounds or alternatives
No response