search

k8ssandra / k8ssandra-operator

The Kubernetes operator for K8ssandra
https://k8ssandra.io/
Apache License 2.0
169 stars 78 forks source link

k8ssandra-operator should define all bound ports in pod spec #655

Open petercable opened 2 years ago

petercable commented 2 years ago

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

┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: K8OP-202

petercable commented 2 years ago

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

jsanda commented 2 years ago

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

jsanda commented 2 years ago

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

jsanda commented 2 years ago

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