Pato Arvizu
Pato Arvizu
Create a Terraform module to have an alternative to Helm as a way to deploying the operator
Currently, the Helm chart only allows the creation of a single `ClusterRole` and `ClusterRoleBinding`, which would create collisions if a chart is installed multiple times in the same Kubernetes cluster....
If the operator is cluster-scoped, it's currently not possible to have secrets that need to be written to more than one Vault cluster. If `KMSVaultSecret` objects can be extended to...
It would be great to have a way to support deploying multiple `KMSVaultSecret`s that are writing to the same path and merge the content of both to avoid contention, similar...
The path `secret/` is hard-coded [here](https://github.com/patoarvizu/kms-vault-operator/blob/master/pkg/controller/kmsvaultsecret/kmsvaultsecret_kvv2.go#L47). The operator should generalize the operation to support any path.
It should be somewhat easy to translate from reading `.circleci/config.yaml`
| Q | A | --------------- | --- | Bug fix? | no | New feature? | yes | API breaks? | no | Deprecations? | no | Related tickets...
I started exploring Notary a couple of days ago and I personally find it easier to run things locally on Kubernetes (with minikube or k3s) rather than docker-compose, but I...
Addressing #1502 I started exploring Notary a couple of weeks ago and while docker-compose was helpful, I was trying to run it with something more natural to me and I...