strimzi operator fails to start when installed to specific namespace in minikube, with helm #6094
Unanswered
FelipeLujan
asked this question in
Q&A
Replies: 2 comments 2 replies
-
Hello @FelipeLujan. You are only trying to run and watch the pods into the namespace that you created using helm, right? |
Beta Was this translation helpful? Give feedback.
1 reply
-
You have to decide what namespaces you want to watch. The options you mentioned: watchAnyNamespace: true
watchNamespaces:
- logging Do not make any sense. You either want to watch all namespaces or you want to watch the namespace where the operator is installed + the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
When I install the strimzi-kafka-operator (with helm) to a Specific namespace, logging in this case. It enters in a OOMKilled-CrashLoopBackOff loop apparently due to:
I've tried passing no value overrides and passing the following values, I get the same result.
To Reproduce
Steps to reproduce the behavior:
kubectl create ns logging
helm install logging-stack -n logging strimzi/strimzi-kafka-operator
kubectl get po -n logging
Expected behavior
The
strimzi-cluster-operator-
pod starts just fineEnvironment (please complete the following information):
YAML files and logs
Attach or copy paste the custom resources
pod describe
pod logs
Additional context
edit:
The same replication steps in EKS produce a healthy operator
pod description
pod logs
Beta Was this translation helpful? Give feedback.
All reactions