Change domain by clusterDomain

miguelaeh · miguelaeh · commit 4effe5c3b9ac · 2019-07-02T10:10:27.000Z
Signed-off-by: Miguel A. Cabrera Minagorri &lt;macabrera@bitnami.com&gt;
diff --git a/bitnami/consul/README.md b/bitnami/consul/README.md
@@ -74,7 +74,7 @@ The following tables lists the configurable parameters of the HashiCorp Consul c
 | `securityContext.enabled`            | Enable security context                                          | `true`                                                     |
 | `securityContext.fsGroup`            | Group ID for the container                                       | `1001`                                                     |
 | `securityContext.runAsUser`          | User ID for the container                                        | `1001`                                                     |
-| `domain`                             | Kubernetes cluster domain                                        | `cluster.local`                                            |
+| `clusterDomain`                      | Kubernetes cluster domain                                        | `cluster.local`                                            |
 | `updateStrategy.type`                | Statefulset update strategy policy                               | `RollingUpdate`                                            |
 | `persistence.enabled`                | Use a PVC to persist data                                        | `true`                                                     |
 | `persistence.storageClass`           | Storage class of backing PVC                                     | `nil` (uses alpha storage class annotation)                |
diff --git a/bitnami/consul/templates/NOTES.txt b/bitnami/consul/templates/NOTES.txt
@@ -1,6 +1,6 @@
   ** Please be patient while the chart is being deployed **
 
-  Consul can be accessed within the cluster on port {{ .Values.service.serverPort }} at {{ template "consul.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }}
+  Consul can be accessed within the cluster on port {{ .Values.service.serverPort }} at {{ template "consul.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}
 
 {{- if .Values.ui.service.enabled }}
 
diff --git a/bitnami/consul/values-production.yaml b/bitnami/consul/values-production.yaml
@@ -47,7 +47,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 ## Datacenter name for consul. If not supplied, will use the consul
 ## default 'dc1'
diff --git a/bitnami/consul/values.yaml b/bitnami/consul/values.yaml
@@ -47,7 +47,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 ## Datacenter name for consul. If not supplied, will use the consul
 ## default 'dc1'
diff --git a/bitnami/elasticsearch/README.md b/bitnami/elasticsearch/README.md
@@ -88,7 +88,7 @@ The following table lists the configurable parameters of the Elasticsearch chart
 | `securityContext.enabled`                         | Enable security context                                                                                                   | `true`                                                  |
 | `securityContext.fsGroup`                         | Group ID for the container                                                                                                | `1001`                                                  |
 | `securityContext.runAsUser`                       | User ID for the container                                                                                                 | `1001`                                                  |
-| `domain`                                          | Kubernetes cluster domain                                                                                                 | `cluster.local`                                         |
+| `clusterDomain`                                   | Kubernetes cluster domain                                                                                                 | `cluster.local`                                         |
 | `discovery.name`                                  | Discover node pod name                                                                                                    | `discovery`                                             |
 | `coordinating.name`                               | Coordinating-only node pod name                                                                                           | `coordinating-only`                                     |
 | `coordinating.replicas`                           | Desired number of Elasticsearch coordinating-only nodes                                                                   | `2`                                                     |
diff --git a/bitnami/elasticsearch/templates/NOTES.txt b/bitnami/elasticsearch/templates/NOTES.txt
@@ -42,7 +42,7 @@
 
 ** Please be patient while the chart is being deployed **
 
-  Elasticsearch can be accessed within the cluster on port {{ .Values.coordinating.service.port }} at {{ template "elasticsearch.coordinating.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }}
+  Elasticsearch can be accessed within the cluster on port {{ .Values.coordinating.service.port }} at {{ template "elasticsearch.coordinating.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}
 
   To access from outside the cluster execute the following commands:
 
diff --git a/bitnami/elasticsearch/values-production.yaml b/bitnami/elasticsearch/values-production.yaml
@@ -126,7 +126,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 ## Elasticsearch coordinating-only node parameters
 ##
diff --git a/bitnami/elasticsearch/values.yaml b/bitnami/elasticsearch/values.yaml
@@ -126,7 +126,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 ## Elasticsearch coordinating-only node parameters
 ##
diff --git a/bitnami/kafka/README.md b/bitnami/kafka/README.md
@@ -106,7 +106,7 @@ The following tables lists the configurable parameters of the Kafka chart and th
 | `securityContext.enabled`               | Enable security context                                                                                   | `true`                                                             |
 | `securityContext.fsGroup`               | Group ID for the container                                                                                | `1001`                                                             |
 | `securityContext.runAsUser`             | User ID for the container                                                                                 | `1001`                                                             |
-| `domain`                                | Kubernetes cluster domain                                                                                 | `cluster.local`                                                    |
+| `clusterDomain`                         | Kubernetes cluster domain                                                                                 | `cluster.local`                                                    |
 | `service.type`                          | Kubernetes Service type                                                                                   | `ClusterIP`                                                        |
 | `service.port`                          | Kafka port                                                                                                | `9092`                                                             |
 | `service.nodePort`                      | Kubernetes Service nodePort                                                                               | `nil`                                                              |
diff --git a/bitnami/kafka/templates/NOTES.txt b/bitnami/kafka/templates/NOTES.txt
@@ -18,7 +18,7 @@
 
 Kafka can be accessed via port 9092 on the following DNS name from within your cluster:
 
-    {{ template "kafka.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }}
+    {{ template "kafka.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}
 
 To create a topic run the following command:
 
diff --git a/bitnami/kafka/templates/statefulset.yaml b/bitnami/kafka/templates/statefulset.yaml
@@ -101,9 +101,9 @@ spec:
           {{- if .Values.advertisedListeners }}
           value: {{ .Values.advertisedListeners }}
           {{- else if .Values.auth.enabled  }}
-          value: 'SASL_SSL://$(MY_POD_NAME).{{ template "kafka.fullname" . }}-headless.{{.Release.Namespace}}.svc.{{ .Values.domain }}:$(KAFKA_PORT_NUMBER)'
+          value: 'SASL_SSL://$(MY_POD_NAME).{{ template "kafka.fullname" . }}-headless.{{.Release.Namespace}}.svc.{{ .Values.clusterDomain }}:$(KAFKA_PORT_NUMBER)'
           {{- else }}
-          value: 'PLAINTEXT://$(MY_POD_NAME).{{ template "kafka.fullname" . }}-headless.{{.Release.Namespace}}.svc.{{ .Values.domain }}:$(KAFKA_PORT_NUMBER)'
+          value: 'PLAINTEXT://$(MY_POD_NAME).{{ template "kafka.fullname" . }}-headless.{{.Release.Namespace}}.svc.{{ .Values.clusterDomain }}:$(KAFKA_PORT_NUMBER)'
           {{- end }}
         {{- if .Values.listenerSecurityProtocolMap }}
         - name: KAFKA_LISTENER_SECURITY_PROTOCOL_MAP
diff --git a/bitnami/kafka/values-production.yaml b/bitnami/kafka/values-production.yaml
@@ -223,7 +223,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 ## Kubernetes configuration
 ## For minikube, set this to NodePort, elsewhere use LoadBalancer
diff --git a/bitnami/kafka/values.yaml b/bitnami/kafka/values.yaml
@@ -223,7 +223,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.loc
+clusterDomain: cluster.local
 
 ## Kubernetes configuration
 ## For minikube, set this to NodePort, elsewhere use LoadBalancer
diff --git a/bitnami/memcached/README.md b/bitnami/memcached/README.md
@@ -61,7 +61,7 @@ The following tables lists the configurable parameters of the Memcached chart an
 | `memcachedPassword`         | Memcached admin password            | `nil`                                                     |
 | `serviceType`               | Kubernetes Service type             | `ClusterIP`                                               |
 | `resources`                 | CPU/Memory resource requests/limits | Memory: `256Mi`, CPU: `250m`                              |
-| `domain`                    | Kubernetes cluster domain           | `cluster.local`                                           |
+| `clusterDomain`                    | Kubernetes cluster domain           | `cluster.local`                                           |
 | `metrics.enabled`                          | Start a side-car prometheus exporter                                                                           | `false`                                              |
 | `metrics.image.registry`                   | MongoDB exporter image registry                                                                                  | `docker.io`                                          |
 | `metrics.image.repository`                 | MongoDB exporter image name                                                                                      | `prom/memcached-exporter`                           |
diff --git a/bitnami/memcached/templates/NOTES.txt b/bitnami/memcached/templates/NOTES.txt
@@ -1,7 +1,7 @@
 
 ** Please be patient while the chart is being deployed **
 
-Memcached can be accessed on port 11211 on the following DNS name from within your cluster: {{ template "fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }}
+Memcached can be accessed on port 11211 on the following DNS name from within your cluster: {{ template "fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}
 
 {{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
 
diff --git a/bitnami/memcached/values-production.yaml b/bitnami/memcached/values-production.yaml
@@ -68,7 +68,7 @@ resources:
 podAnnotations: {}
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 ## Prometheus Exporter / Metrics
 ##
diff --git a/bitnami/memcached/values.yaml b/bitnami/memcached/values.yaml
@@ -68,7 +68,7 @@ resources:
 podAnnotations: {}
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 ## Prometheus Exporter / Metrics
 ##
diff --git a/bitnami/minio/README.md b/bitnami/minio/README.md
@@ -81,7 +81,7 @@ The following table lists the configurable parameters of the MinIO chart and the
 | `securityContext.enabled`              | Enable security context                                                                      | `true`                                                  |
 | `securityContext.fsGroup`              | Group ID for the container                                                                   | `1001`                                                  |
 | `securityContext.runAsUser`            | User ID for the container                                                                    | `1001`                                                  |
-| `domain`                               | Kubernetes cluster domain                                                                    | `cluster.local`                                         |
+| `clusterDomain`                        | Kubernetes cluster domain                                                                    | `cluster.local`                                         |
 | `livenessProbe.enabled`                | Enable/disable the Liveness probe                                                            | `true`                                                  |
 | `livenessProbe.initialDelaySeconds`    | Delay before liveness probe is initiated                                                     | `60`                                                    |
 | `livenessProbe.periodSeconds`          | How often to perform the probe                                                               | `10`                                                    |
diff --git a/bitnami/minio/templates/NOTES.txt b/bitnami/minio/templates/NOTES.txt
@@ -2,7 +2,7 @@
 
 MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster:
 
-   {{ include "minio.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }}
+   {{ include "minio.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}
 
 To get your credentials run:
 
diff --git a/bitnami/minio/templates/statefulset.yaml b/bitnami/minio/templates/statefulset.yaml
@@ -82,7 +82,7 @@ spec:
           {{- $minioFullname := include "minio.fullname" . }}
           {{- $minioHeadlessServiceName := printf "%s-%s" $minioFullname "headless" | trunc 63  }}
           {{- $releaseNamespace := .Release.Namespace }}
-          value: {{range $i, $e := until $replicaCount }}{{ $minioFullname }}-{{ $e }}.{{ $minioHeadlessServiceName }}.{{ $releaseNamespace }}.svc.{{ .Values.domain }},{{ end }}
+          value: {{range $i, $e := until $replicaCount }}{{ $minioFullname }}-{{ $e }}.{{ $minioHeadlessServiceName }}.{{ $releaseNamespace }}.svc.{{ .Values.clusterDomain }},{{ end }}
         {{- if .Values.useCredentialsFile }}
         - name: MINIO_ACCESS_KEY_FILE
           value: "/opt/bitnami/minio/secrets/access-key"
diff --git a/bitnami/minio/values-production.yaml b/bitnami/minio/values-production.yaml
@@ -138,7 +138,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 ## Configure liveness and readiness probes
 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
diff --git a/bitnami/minio/values.yaml b/bitnami/minio/values.yaml
@@ -132,7 +132,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 ## Configure liveness and readiness probes
 ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
diff --git a/bitnami/mysql/README.md b/bitnami/mysql/README.md
@@ -65,7 +65,7 @@ The following tables lists the configurable parameters of the MySQL chart and th
 | `securityContext.enabled`                 | Enable security context                                                    | `true`                                                            |
 | `securityContext.fsGroup`                 | Group ID for the container                                                 | `1001`                                                            |
 | `securityContext.runAsUser`               | User ID for the container                                                  | `1001`                                                            |
-| `domain`                                  | Kubernetes cluster domain                                                  | `cluster.local`                                                   |
+| `clusterDomain`                           | Kubernetes cluster domain                                                  | `cluster.local`                                                   |
 | `replication.enabled`                     | MySQL replication enabled                                                  | `true`                                                            |
 | `replication.user`                        | MySQL replication user (should be different from db.user)                  | `replicator`                                                      |
 | `replication.password`                    | MySQL replication user password                                            | _random 10 character alphanumeric string_                         |
diff --git a/bitnami/mysql/templates/NOTES.txt b/bitnami/mysql/templates/NOTES.txt
@@ -7,9 +7,9 @@ Tip:
 
 Services:
 
-  echo Master: {{ template "fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }}:{{ .Values.service.port }}
+  echo Master: {{ template "fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}:{{ .Values.service.port }}
 {{- if .Values.replication.enabled }}
-  echo Slave:  {{ template "mysql.slave.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }}:{{ .Values.service.port }}
+  echo Slave:  {{ template "mysql.slave.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}:{{ .Values.service.port }}
 {{- end }}
 
 Administrator credentials:
@@ -25,13 +25,13 @@ To connect to your database:
 
   2. To connect to master service (read/write):
 
-      mysql -h {{ template "fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }} -uroot -p {{ .Values.db.name }}
+      mysql -h {{ template "fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }} -uroot -p {{ .Values.db.name }}
 
 {{- if .Values.replication.enabled }}
 
   3. To connect to slave service (read-only):
 
-      mysql -h {{ template "mysql.slave.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }} -uroot -p {{ .Values.db.name }}
+      mysql -h {{ template "mysql.slave.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }} -uroot -p {{ .Values.db.name }}
 {{- end }}
 
 To upgrade this helm chart:
diff --git a/bitnami/mysql/values-production.yaml b/bitnami/mysql/values-production.yaml
@@ -40,7 +40,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 root:
   ## MySQL admin password
diff --git a/bitnami/mysql/values.yaml b/bitnami/mysql/values.yaml
@@ -40,7 +40,7 @@ securityContext:
   runAsUser: 1001
 
 # Cluster domain
-domain: cluster.local
+clusterDomain: cluster.local
 
 root:
   ## MySQL admin password
diff --git a/bitnami/zookeeper/README.md b/bitnami/zookeeper/README.md
@@ -60,7 +60,7 @@ The following tables lists the configurable parameters of the Zookeeper chart an
 | `updateStrategy`                      | Update strategies                                                   | `RollingUpdate`                                          |
 | `podDisruptionBudget.maxUnavailable`  | Max number of pods down simultaneously                              | `1`                                                      |
 | `rollingUpdatePartition`              | Partition update strategy                                           | `nil`                                                    |
-| `domain`                              | Kubernetes cluster domain                                           | `cluster.local`                                          |
+| `clusterDomain`                       | Kubernetes cluster domain                                           | `cluster.local`                                          |
 | `podManagementpolicy`                 | Pod management policy                                               | `Parallel`                                               |
 | `replicaCount`                        | Number of ZooKeeper nodes                                           | `1`                                                      |
 | `tickTime`                            | Basic time unit in milliseconds used by ZooKeeper for heartbeats    | `2000`                                                   |
diff --git a/bitnami/zookeeper/templates/NOTES.txt b/bitnami/zookeeper/templates/NOTES.txt
@@ -19,7 +19,7 @@
 
 ZooKeeper can be accessed via port 2181 on the following DNS name from within your cluster:
 
-    {{ template "zookeeper.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.domain }}
+    {{ template "zookeeper.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}
 
 To connect to your ZooKeeper server run the following commands:
 
diff --git a/bitnami/zookeeper/templates/metrics-deployment.yaml b/bitnami/zookeeper/templates/metrics-deployment.yaml
diff --git a/bitnami/zookeeper/templates/statefulset.yaml b/bitnami/zookeeper/templates/statefulset.yaml
diff --git a/bitnami/zookeeper/values-production.yaml b/bitnami/zookeeper/values-production.yaml
diff --git a/bitnami/zookeeper/values.yaml b/bitnami/zookeeper/values.yaml
