You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?
When management-api is configured to use mutual TLS authentication, we are unable to use Kubernetes' httpGet for liveness and readiness probes, since Kubernetes does not allow us to use mutual auth TLS. Thus, in this case we replace the calls by executing wget on the pod that then has access to both of these certificates (since they're mounted to the pods).
If the calls never reach the target for some reason, this wget call was never exiting itself. This caused multiple wget processes to live in the pod, as they would live longer than the interval for those calls.
Did you expect to see something different?
Each wget call should have a timeout that's shorter than (or equal to) the probing interval.
How to reproduce it (as minimally and precisely as possible):
Environment
Cass Operator version:
Insert image tag or Git SHA here
* Kubernetes version information:
kubectl version
* Kubernetes cluster kind:
insert how you created your cluster: kops, bootkube, etc.
Manifests:
insert manifests relevant to the issue
Cass Operator Logs:
insert Cass Operator logs relevant to the issue here
Anything else we need to know?:
┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1667
┆priority: Medium
The text was updated successfully, but these errors were encountered:
What happened?
When management-api is configured to use mutual TLS authentication, we are unable to use Kubernetes' httpGet for liveness and readiness probes, since Kubernetes does not allow us to use mutual auth TLS. Thus, in this case we replace the calls by executing wget on the pod that then has access to both of these certificates (since they're mounted to the pods).
If the calls never reach the target for some reason, this wget call was never exiting itself. This caused multiple wget processes to live in the pod, as they would live longer than the interval for those calls.
Did you expect to see something different?
Each wget call should have a timeout that's shorter than (or equal to) the probing interval.
How to reproduce it (as minimally and precisely as possible):
Environment
Cass Operator version:
* Kubernetes version information:Insert image tag or Git SHA here
* Kubernetes cluster kind:kubectl version
Anything else we need to know?:
┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1667
┆priority: Medium
The text was updated successfully, but these errors were encountered: