Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Bug] Helm install strimzi/strimzi-kafka-operator pod fails with error ErrImagePull in minikube
See original GitHub issueDescribe the bug I tried to install helm chart strimzi/strimzi-kafka-operator in minikube but pod failed with error ErrImagePull (reference document https://strimzi.io/blog/2018/11/01/using-helm/)
To Reproduce
//Install minikube
minikube --memory 20g --cpus 3 start
//add repo
helm repo add strimzi https://strimzi.io/charts/
//install chart
helm install strimzi-kafka strimzi/strimzi-kafka-operator
Output of above command NAME: strimzi-kafka-operator-1590524093 LAST DEPLOYED: Tue May 26 15:14:55 2020 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: Thank you for installing strimzi-kafka-operator-0.18.0
Now, if I do
kubectl get pods
NAME READY STATUS RESTARTS AGE
strimzi-cluster-operator-54565f8c56-5rjp4 0/1 ErrImagePull 0 19s
Expected behavior Pod strimzi-cluster-operator should be in running status. Why the Imagepull failed.?
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ok. TBH I’m afraid there is not much more I can do … I can pull the image fine from DockerHub, so that should be fine. Can you pull any other images from DockerHub? Do you have any proxies or admission controller which can be checking this and not allowing you to pull it?
Great, glad it works.