[GitHub] [couchdb-helm] kaiburjack opened a new issue, #116: post-install job uses hard-coded cluster.local DNS suffix

["kaiburjack (via GitHub)" <gi...@apache.org>]

kaiburjack opened a new issue, #116:
URL: https://github.com/apache/couchdb-helm/issues/116

   **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**:
   -


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@couchdb.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [couchdb-helm] willholley closed issue #116: post-install job uses hard-coded cluster.local DNS suffix

["willholley (via GitHub)" <gi...@apache.org>]

willholley closed issue #116: post-install job uses hard-coded cluster.local DNS suffix
URL: https://github.com/apache/couchdb-helm/issues/116


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@couchdb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org