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.

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

post-install job uses hard-coded cluster.local DNS suffix #116

Closed
kaiburjack opened this issue May 9, 2023 · 0 comments · Fixed by #119
Closed

post-install job uses hard-coded cluster.local DNS suffix #116

kaiburjack opened this issue May 9, 2023 · 0 comments · Fixed by #119

Comments

@kaiburjack
Copy link

Describe the bug
When using a Kubernetes setup with a custom DNS cluster domain suffix (like is required with a GKE VPC-scoped Cloud DNS), the post-install job will fail because of a hard-coded cluster.local domain part.

While it is possible to override the DNS clusterDomainSuffix as a Helm value dns.clusterDomainSuffix, this value apparently is not used by the post-install job (only in the ConfigMap used by the couchdb pods).

Version of Helm and Kubernetes:
(irrelevant)

What happened:
(see description above)

What you expected to happen:
Helm chart working with a custom cluster domain suffix.

How to reproduce it (as minimally and precisely as possible):
Install couchdb in a Kubernetes cluster with a non-default DNS suffix (i.e. not cluster.local).

Anything else we need to know:

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

Successfully merging a pull request may close this issue.

1 participant