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
I have stood up a minikube cluster on Windows 11 host with WSL2 using the following command: minikube start --profile='test-cluster' --ports=80,443 --container-runtime=containerd
See node details from kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
test-cluster Ready control-plane 78s v1.26.3 192.168.49.2 <none> Ubuntu 20.04.5 LTS 5.15.90.1-microsoft-standard-WSL2 containerd://1.6.20
After the cluster is available, I attempted to install NeuVector 5.1.3 via Helm with the command:
Both the controller and enforcer pods never come up and stay in CrashLoopBackOff state. See attached logs. controller-logs.txt enforcer-logs.txt
I've tried various configurations using Minikube and K3s as well as downgrading both K8s and NeuVector versions. Google has not provided any value added recommendations and/or solutions at this time. All examples merely state to update container runtime and the default configuration should work. I've reviewed both open and closed GitHub issues with no luck. Please let me know if there is any additional information I can provide to help resolve what is probably a small detail. I do not have access to AWS, GCP, or Azure cluster at this time to try cloud based installations.
Adding a getting started with Minikube or K3s tutorial to the docs (or YouTube video) would be super helpful to budding DevOps engineers as well. Thank you for your time.
The text was updated successfully, but these errors were encountered:
emucker
changed the title
Controller and Enforcer pods fail to start in Minikube cluster with containerd runtime
Controller and Enforcer pods fail to start in WSL2 Windows environment
Jun 21, 2023
I have stood up a minikube cluster on Windows 11 host with WSL2 using the following command:
minikube start --profile='test-cluster' --ports=80,443 --container-runtime=containerd
See node details from
kubectl get nodes -o wide
After the cluster is available, I attempted to install NeuVector 5.1.3 via Helm with the command:
Both the controller and enforcer pods never come up and stay in CrashLoopBackOff state. See attached logs.
controller-logs.txt
enforcer-logs.txt
I've tried various configurations using Minikube and K3s as well as downgrading both K8s and NeuVector versions. Google has not provided any value added recommendations and/or solutions at this time. All examples merely state to update container runtime and the default configuration should work. I've reviewed both open and closed GitHub issues with no luck. Please let me know if there is any additional information I can provide to help resolve what is probably a small detail. I do not have access to AWS, GCP, or Azure cluster at this time to try cloud based installations.
Adding a getting started with Minikube or K3s tutorial to the docs (or YouTube video) would be super helpful to budding DevOps engineers as well. Thank you for your time.
The text was updated successfully, but these errors were encountered: