在启用K8S namespase注入后，ISTIO SIDECAR注入了卡住的容器创建
当启用Sidecar Istio在Minikube本地群集上启用SIDECAR ISTIO时，我会
问题
1. kubectl label namespace udemy istio-injection=enabled
2. kubecl apply -f mydeployment.yaml
6s Normal Scheduled pod/kiada Successfully assigned udemy/kiada to minikube
4s Normal Pulled pod/kiada Container image "docker.io/istio/proxyv2:1.10.3" already present on machine
4s Normal Created pod/kiada Created container istio-init
4s Normal Started pod/kiada Started container istio-init
2s Warning BackOff pod/kiada Back-off restarting failed container
遇到
I'm running into a problem when enable sidecar istio-injection over minikube local cluster, after apply a deployment manifest the pod never start
Steps reproduced...
1. kubectl label namespace udemy istio-injection=enabled
2. kubecl apply -f mydeployment.yaml
6s Normal Scheduled pod/kiada Successfully assigned udemy/kiada to minikube
4s Normal Pulled pod/kiada Container image "docker.io/istio/proxyv2:1.10.3" already present on machine
4s Normal Created pod/kiada Created container istio-init
4s Normal Started pod/kiada Started container istio-init
2s Warning BackOff pod/kiada Back-off restarting failed container
Stay stuck
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我可以得到确切的部署。yaml吗？
您是否在其中附加了任何卷/configmaps/秘密？如果是，请确保所有这些都可以在部署之前可用。
Can I get the exact deployment.yaml ?
Did you attach any volumes/configmaps/secrets in it? if yes, please make sure all those are available before you deploy.