metal3: mariadb remove hostNetwork: true (#27)

We connect to the mariadb endpoint via Service/ClusterIP so the container should not need to listen on the hostNetwork. AFAICS this exists because the downstream container image listened only on localhost which has now been fixed[1] so combined with this change ClusterIP access should now work correctly. [1] https://build.opensuse.org/package/rdiff/isv:metal3:BCI:ironic/mariadb?linkrev=base&rev=4
suse-edge · Sep 4, 2023 · b1598df · b1598df
1 parent c61c0c3
commit b1598df
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 3 deletions.
diff --git a/assets/metal3-deploy/metal3-deploy-0.1.0.tgz b/assets/metal3-deploy/metal3-deploy-0.1.0.tgz
diff --git a/charts/metal3-deploy/0.1.0/charts/mariadb/templates/deployment.yaml b/charts/metal3-deploy/0.1.0/charts/mariadb/templates/deployment.yaml
@@ -25,7 +25,6 @@ spec:
       serviceAccountName: {{ include "mariadb.serviceAccountName" . }}
       securityContext:
         {{- toYaml .Values.podSecurityContext | nindent 8 }}
-      hostNetwork: true
       containers:
       - name: mariadb
         image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"

diff --git a/packages/mariadb/charts/templates/deployment.yaml b/packages/mariadb/charts/templates/deployment.yaml
@@ -25,7 +25,6 @@ spec:
       serviceAccountName: {{ include "mariadb.serviceAccountName" . }}
       securityContext:
         {{- toYaml .Values.podSecurityContext | nindent 8 }}
-      hostNetwork: true
       containers:
       - name: mariadb
         image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
@@ -72,4 +71,4 @@ spec:
         volumeMounts:
             {{- $volmounts }}
       volumes:
-        {{- $volumes }}
+        {{- $volumes }}