Merge remote-tracking branch 'origin/master' into ambassador-helm3-support-crds

stable/ambassador/templates/deployment.yaml

@@ -17,7 +17,7 @@ metadata:
       {{- toYaml .Values.deploymentAnnotations | nindent 4 }}
     {{- end }}
 spec:
-{{- if not .Values.daemonSet }}
+{{- if and (not .Values.autoscaling.enabled) (not .Values.daemonSet) }}
   replicas: {{ .Values.replicaCount }}
 {{- end }}
   selector:

stable/postgresql/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v1
 name: postgresql
-version: 7.7.0
+version: 7.7.1
 appVersion: 11.6.0
 description: Chart for PostgreSQL, an object-relational database management system (ORDBMS) with an emphasis on extensibility and on standards-compliance.
 keywords:

stable/postgresql/templates/networkpolicy.yaml

@@ -22,15 +22,15 @@ spec:
         - podSelector:
             matchLabels:
               {{ template "postgresql.fullname" . }}-client: "true"
+          {{- if .Values.networkPolicy.explicitNamespacesSelector }}
+          namespaceSelector:
+{{ toYaml .Values.networkPolicy.explicitNamespacesSelector | indent 12 }}
+          {{- end }}
         - podSelector:
             matchLabels:
               app: {{ template "postgresql.name" . }}
               release: {{ .Release.Name | quote }}
               role: slave
-        {{- if .Values.networkPolicy.explicitNamespacesSelector }}
-        - namespaceSelector:
-{{ toYaml .Values.networkPolicy.explicitNamespacesSelector | indent 12 }}
-        {{- end }}
       {{- end }}
     # Allow prometheus scrapes
     - ports:

stable/postgresql/values-production.yaml

@@ -351,10 +351,10 @@ networkPolicy:
   ##
   allowExternal: true
 
-  ## if explicitNamespacesSelector is missing or set to {}, only Pods that are in the networkPolicy's namespace
-  ## and that match other criteria, the ones that can be selected by one of the podSelectors, can reach the DB.
-  ## But sometimes, we want the DB to be accessible from other namespaces, in this case, we can use this
-  ## LabelSelector to select these namespaces, note that the networkPolicy's should also be explicitly added.
+  ## if explicitNamespacesSelector is missing or set to {}, only client Pods that are in the networkPolicy's namespace
+  ## and that match other criteria, the ones that have the good label, can reach the DB.
+  ## But sometimes, we want the DB to be accessible to clients from other namespaces, in this case, we can use this
+  ## LabelSelector to select these namespaces, note that the networkPolicy's namespace should also be explicitly added.
   ##
   # explicitNamespacesSelector:
     # matchLabels:

stable/postgresql/values.yaml

@@ -359,10 +359,10 @@ networkPolicy:
   ##
   allowExternal: true
 
-  ## if explicitNamespacesSelector is missing or set to {}, only Pods that are in the networkPolicy's namespace
-  ## and that match other criteria, the ones that can be selected by one of the podSelectors, can reach the DB.
-  ## But sometimes, we want the DB to be accessible from other namespaces, in this case, we can use this
-  ## LabelSelector to select these namespaces, note that the networkPolicy's should also be explicitly added.
+  ## if explicitNamespacesSelector is missing or set to {}, only client Pods that are in the networkPolicy's namespace
+  ## and that match other criteria, the ones that have the good label, can reach the DB.
+  ## But sometimes, we want the DB to be accessible to clients from other namespaces, in this case, we can use this
+  ## LabelSelector to select these namespaces, note that the networkPolicy's namespace should also be explicitly added.
   ##
   # explicitNamespacesSelector:
     # matchLabels: