Fix load balancer with mix protocols issue

bitnami/consul/README.md

@@ -54,7 +54,6 @@ The following tables lists the configurable parameters of the Consul chart and t
 | `image.tag`                          | Consul image tag                                       | `{VERSION}`                                                |
 | `image.pullPolicy`                   | Image pull policy                                      | `Always`                                                   |
 | `image.pullSecrets`                  | Specify image pull secrets                             | `nil`                                                      |
-| `serviceType`                        | Kubernetes Service type                                | `ClusterIP`                                                |
 | `replicas`                           | Number of replicas                                     | `3`                                                        |
 | `httpPort`                           | Consul http listening port                             | `8500`                                                     |
 | `rpcPort`                            | Consul rpc listening port                              | `8400`                                                     |
@@ -234,4 +233,4 @@ helm install bitnami/consul --set tlsEncryptionSecretName=consul-tls-encryption
 
 ## Metrics
 
-The chart can optionally start a metrics exporter endpoint on port `9107` for [prometheus](https://prometheus.io). The data exposed by the endpoint is intended to be consumed by a prometheus chart deployed within the cluster and as such the endpoint is not exposed outside the cluster.
+The chart can optionally start a metrics exporter endpoint on port `9107` for [prometheus](https://prometheus.io). The data exposed by the endpoint is intended to be consumed by a prometheus chart deployed within the cluster and as such the endpoint is not exposed outside the cluster.

bitnami/consul/templates/consul-service.yaml

@@ -10,7 +10,6 @@ metadata:
   annotations:
     service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"
 spec:
-  type: "{{ .Values.serviceType }}"
   ports:
   - name: http
     port: {{ .Values.httpPort }}
@@ -29,10 +28,7 @@ spec:
   - name: consuldns-udp
     protocol: "UDP"
     port: {{.Values.consulDnsPort}}
-  {{- if contains "ClusterIP" .Values.serviceType }}
   clusterIP: None
-  {{- end }}  
   selector:
     app: "{{ template "consul.name" . }}"
     release: {{ .Release.Name | quote }}
-

bitnami/consul/values.yaml

@@ -17,9 +17,6 @@ image:
   # pullSecrets:
   #   - myRegistrKeySecretName
 
-## Kubernetes service type
-serviceType: ClusterIP
-
 ## Consul replicas
 replicas: 3
 
@@ -113,19 +110,19 @@ ui:
   ingress:
     ## Set to true to enable ingress record generation
     enabled: false
-  
+
     ## The list of hostnames to be covered with this ingress record.
     ## Most likely this will be just one host, but in the event more hosts are needed, this is an array
     hosts:
     - name: consul-ui.local
-  
+
       ## Set this to true in order to enable TLS on the ingress record
       ## A side effect of this will be that the backend consul service will be connected at port 443
       tls: false
-  
+
       ## If TLS is set to true, you must declare what secret will store the key/certificate for TLS
       tlsSecret: consul-ui.local-tls
-  
+
       ## Ingress annotations done as key:value pairs
       ## If you're using kube-lego, you will want to add:
       ## kubernetes.io/tls-acme: true
@@ -152,7 +149,7 @@ ui:
     #   certificate:
 
 ## Consul configmap
-#configmap: | 
+#configmap: |
 #    {
 #    "datacenter":"dc2",
 #    "domain":"consul",
@@ -175,8 +172,8 @@ ui:
 
 metrics:
   enabled: false
-  image: 
-    registry: docker.io 
+  image:
+    registry: docker.io
     repository: prom/consul-exporter
     tag: v0.3.0
     pullPolicy: IfNotPresent