[bitnami/scylladb] Fix networkpolicy when use extraContainerPorts

[dragonzeen]

Description of the change

Fixed the invalid handling of the .extraContainerPorts values in the generated NetworkPolicy

Benefits

The NetworkPolicy no longer errors when the extraContainerPorts is defined

Possible drawbacks

None

Applicable issues

• fixes [bitnami/scylladb] Error occurred generated networkpolicy when use extraContainerPorts #36286

Additional information

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
• Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• All commits signed off and in agreement of Developer Certificate of Origin (DCO)

[fmulero]

Good catch!! thanks a lot @dragonzeen for taking care of this issue.

Checking your changes, I've just detected exactly the same issue in ingress section, affecting also to jmxProxy.extraContainerPorts (some lines below your current change):

charts/bitnami/scylladb/templates/networkpolicy.yaml

Lines 61 to 68 in 5c2c475

	{{- range .Values.extraContainerPorts }}
	- port: {{ . }}
	{{- end }}
	{{- if .Values.jmxProxy.enabled }}
	- port: {{ .Values.containerPorts.jmx }}
	{{- range .Values.jmxProxy.extraContainerPorts }}
	- port: {{ . }}
	{{- end }}

Would you mind apply the same change there?

[dragonzeen]

Good catch!! thanks a lot @dragonzeen for taking care of this issue.

Checking your changes, I've just detected exactly the same issue in ingress section, affecting also to jmxProxy.extraContainerPorts (some lines below your current change):

charts/bitnami/scylladb/templates/networkpolicy.yaml

Lines 61 to 68 in 5c2c475

	{{- range .Values.extraContainerPorts }}
	- port: {{ . }}
	{{- end }}
	{{- if .Values.jmxProxy.enabled }}
	- port: {{ .Values.containerPorts.jmx }}
	{{- range .Values.jmxProxy.extraContainerPorts }}
	- port: {{ . }}
	{{- end }}

Would you mind apply the same change there?

I updated same issue in ingress section.