Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Namespace vault-operator error #352

Open
GeekOnGadgets opened this issue Oct 11, 2018 · 2 comments
Open

Namespace vault-operator error #352

GeekOnGadgets opened this issue Oct 11, 2018 · 2 comments

Comments

@GeekOnGadgets
Copy link

GeekOnGadgets commented Oct 11, 2018

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

@veenabenoy
Copy link

I am also facing this issue . I created helm chart for hashicorp vault operator. Used stable/vault helm chart as reference.
https://github.com/helm/charts/tree/master/stable/vault-operator
First time if I could install as:
helm install . --name vaulttest. (I pointed to the current folder where helm chart is stored locally and running)
It succeeds.
After sometime,again I try with another namespace as:
helm install . --name vaulttest2
Got error as:
Error: release vaulttest2 failed: customresourcedefinitions.apiextensions.k8s.io "vaultservices.vault.security.coreos.com" already exists.

CAn any one please help me?

@srleyva
Copy link

srleyva commented Aug 2, 2019

It’s running into a conflict because the CRDs already exist. This can be resolved by adding the following to any subsequent helm installs ‘—set rbac.create=false’

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants