fix: add containerPort declaration for webhook in helm chart

[zevisert]

Adds a missing port declaration for the container port serving the webhook to the helm chart. Bumps the chart version for this fix.

Notice that this port is correctly declared in the kustomize patches, it's just the helm chart that didn't expose this.

Here's the port being declared for the kustomize manifests that enable the webhook:

spark-operator/manifest/spark-operator-with-webhook.yaml

Lines 51 to 52 in 252eddd

	ports:
	- containerPort: 8080

But here, the helm chart only creates a port for metrics, with no condition to add a port when .Values.webhook.enable is true

spark-operator/charts/spark-operator-chart/templates/deployment.yaml

Lines 49 to 53 in 252eddd

	{{- if .Values.metrics.enable }}
	ports:
	- name: metrics
	containerPort: {{ .Values.metrics.port }}
	{{ end }}

Closes: #1962

[MasonLegere]

@zevisert Eek I broke the CLA by being attached to that commit. Will sign in a second

[zevisert]

Thanks, I'm not sure if anyone knows yet what will happen with the CLA now that Google has donated this project to kubeflow; for now it's part of the CI that came with the donation and everyone is still signing it.

I can rebase you off that suggestion and use my name if you'd prefer not to sign the CLA at this time.

[andreyvelich]

Hi Folks, sorry for the confusions around Google CLA.
We are in the transition period to turn off Google CLA and fully rely on DCO when we add that as required check for all of Kubeflow repos.
We will disable the Google CLA check for Spark Operator repo soon.

cc @kubeflow/kubeflow-steering-committee

[yuchaoran2011]

/lgtm

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yuchaoran2011, zevisert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [yuchaoran2011]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[AndrewChubatiuk]

@yuchaoran2011 could you please drop tag v1beta2-1.4.0-3.5.0 from repo and rerun pipeline of this commit? CI was just fixed, but no charts or images were published yet

[yuchaoran2011]

Yeah I noticed that. I don't have the admin permissions and hence am unable to delete an existing tag. That said, bumping up the chart version without changing the appVersion is common. What would that prevent the chart from being published?

[zevisert]

Is that something I caused here? I had a merge conflict with master over the chart version; I resolved it by keeping the appVersion from master (v1beta2-1.4.0-3.5.0) and the bumped chart version from here (1.2.3)

[AndrewChubatiuk]

@zevisert just wanted to retrigger a build and put a tag here, cause it's the latest merged commit

[AndrewChubatiuk]

@zevisert created MR to publish chart independently #1964, but bumped both image and chart versions, cause v1beta2-1.4.0-3.5.0 doesn't exist in registry