Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

crd inclusion in helm chart prevents subsequent deployments to alternate namespaces #261

Closed
jckeogh opened this issue Oct 3, 2018 · 2 comments
Closed

crd inclusion in helm chart prevents subsequent deployments to alternate namespaces #261

jckeogh opened this issue Oct 3, 2018 · 2 comments

Comments

@jckeogh
Copy link
Contributor

jckeogh commented Oct 3, 2018

As documented at https://github.com/arangodb/kube-arangodb/blob/master/docs/Manual/Deployment/Kubernetes/Helm.md#alternate-namespaces we should be able to deploy the arango operator to multiple namespaces in the same K8S cluster.
Since the inclusion of the CRD in 0.3.1 we can no longer do this and subsequent deployments fail with

failed: customresourcedefinitions.apiextensions.k8s.io "arangodeploymentreplications.replication.database.arangodb.com" already exists
@jckeogh jckeogh changed the title crd inclusion in helm chart prevents subsequent deployments to alternate namespace crd inclusion in helm chart prevents subsequent deployments to alternate namespaces Oct 3, 2018
@kvahed
Copy link
Contributor

kvahed commented Oct 3, 2018

Will try to reproduce and get back to you. Many thx.

@maierlars
Copy link
Contributor

Fixed with #287

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kvahed @jckeogh @maierlars