vault-operator
vault-operator copied to clipboard
coreos
Run and manage Vault on Kubernetes simply and securely
### Problem Description Kubernetes has been deprecating API(s), which will be removed and are no longer available in 1.22. Operators projects using [these APIs](https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22) versions will **not** work on Kubernetes...
It would fail due to `the server could not find the requested resource` which access a non-valid versioning namespace for deployment
Create deplyments , role and rolebinding in vault namespace by default Include vault serviceaccount and bindings in that namespace to avoid using the default serviceaccount and default namespace Add support...
I've gone through the example of setting up k8s vault auth backend, up until the Authentication step works fine. When I get to this point https://github.com/coreos/vault-operator/blob/master/doc/user/kubernetes-auth-backend.md#authenticate-requests-using-the-service-account-token and try to "Log...
Is this project still active? i see no issues after Apr 2019 for this project. I am trying to setup vault in kubernetes, unfortunately I could not deploying using vault-helm...
Vault [0.10.0](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#0100-april-10th-2018) has been out for a while and the default Vault base image used by the operator needs to be updated to 0.10.0. The vault-operator [by default](https://github.com/coreos-inc/vault-operator/blob/847468db1645d02a2ea35c1ac891de0b49e036e9/pkg/apis/vault/v1alpha1/types.go#L9-L11) uses a...
fix : https://github.com/coreos/vault-operator/issues/366 I tried `Getting start` on README.md and apply configs on `example/` dir. but, vault didn't start. Because etcd-operator fail to exit init container and don't start. This...
It looks like the namespace on line 13 of vault-tokenreview-binding.yaml should be "default" instead of "vault-services". I have followed the documentation steps to deploy vault-operator and configure k8s auth, but...
As described in https://github.com/coreos/vault-operator/issues/320 setting the namespace to "default" fixes the broken login behaviour.
Hi, When I try to create vault-operator per namespace it gives following error. `Error: release vault-operator failed: customresourcedefinitions.apiextensions.k8s.io "vaultservices.vault.security.coreos.com" already exists`. Is this known issue? Thanks
