mirror of https://github.com/istio/istio.io.git
fce84eae28
Minikube does the right thing (as of 0.28.1 at least) with creating the embedded CA. The extra-config parameters appear to have been necessary previously and were resolved to use the "right" credentials built by Minikube directly. In fact, passing those parameters appears to break current minikube deployments, making it impossible to create new service accounts and resources that rely on them. (like a tiller service account for a helm deployment of Istio...) I found this bug that referenced this issue: https://github.com/kubernetes/minikube/issues/1647 which is now closed. |
||
|---|---|---|
| .. | ||
| advanced-install | ||
| ansible-install | ||
| download-release | ||
| helm-install | ||
| mesh-expansion | ||
| minimal-install | ||
| multicluster-install | ||
| platform-setup | ||
| quick-start | ||
| quick-start-alicloud-ack | ||
| quick-start-gke-dm | ||
| quick-start-ibm | ||
| sidecar-injection | ||
| spec-requirements | ||
| upgrading-istio | ||
| _index.md | ||