K8SSAND-1742 ⁃ k8ssandra-operator should define all bound ports in pod spec

[petercable]

What is missing? The k8ssandra-operator defined in the helm chart binds three TCP ports but only one of those ports (the webhook) is defined in the deployment's pod spec.

Why do we need it? In some environments any workload providing a validating or mutating webhook must be run on the host network (for example, EKS with an alternative CNI). Without all ports being defined, kubernetes cannot deconflict other host network workloads that attempt to bind the same port, leading to failures.

Environment

• K8ssandra Operator version:

  1.2.0

  **Anything else we need to know?**:

┆Issue is synchronized with this Jira Story by Unito

[petercable]

Oops, I see the helm chart is in k8ssandra/k8ssandra, closing this and opening an issue there instead.

[jsanda]

For reference https://github.com/k8ssandra/k8ssandra/issues/1488

[jsanda]

I'm reopening this because we need to the changes to the kustomize manifests which live in this repo.

[jsanda]

@petercable Would you mind creating similar issues for cass-operator?