helm & minikube & istio have a bad day on windows.
BarDweller opened this issue · 1 comments
BarDweller commented
I need to look more into which versions are affected here.
But at least with
MInikube v0.33.1
Helm v2.(11.0|12.1|13.0-rc2)
Istio 1.0.6
Using virtualbox as a vm provider.
Attempting to follow these instructions (based from Istio minikube setup)
minikube start --cpus=4 --memory=8192
-- Dont add the certificate paths as Istio docs state, otherwise minikube's controller will crashloop.kubectl apply -f Istio/install/kubernetes/helm/helm-service-account.yaml
helm init --service-account tiller
helm install Istio/kubernetes/helm/istio --name istio --namespace istio-system
Would fail at the last step, because istio would discover that a random customresourcedefinitions.apiextensions.k8s.io
already exists. This behavior was known to occur with helm 2.12.0 and various helm charts including istio. It is reported fixed at 2.12.1 onwards.
BarDweller commented
As a workaround for now, I edited my local k8s-functions
to use the demo yaml deploy instead.
kubectl apply -f install/kubernetes/istio-demo.yaml
Which deploys istio to minikube without using helm.