mirror of https://github.com/knative/docs.git
ad4d987f60
The docs for setting up minikube were using the namespaces and resource names from elafros instead of knative. The naming changed slightly, e.g. a knative controller is now called `controller` instead of `knative-serving-controller`, so one of the loops had to be broken into 2 statements. Added steps about redeploying pods after setting up GCR secrets b/c there is a chicken and egg problem where the namespaces must exist before you can setup the secrets, but the secrets must exist before the images can be pulled. The PR that enabled `MutatingAdmissionWebhook` by default (https://github.com/kubernetes/minikube/pull/2547) was merged, but the latest minikube (0.28.0) still did not enable this option by default b/c providing any arugments overrides all of the defaults, so we must still set it explicitly. Made it clear in the setting up knative serving docs that the cluster admin binding is required, not just for istio. Use a `NodePort` instead of a `LoadBalancer` (see https://github.com/kubernetes/minikube/issues/384) - another step along the road to #608. |
||
|---|---|---|
| debugging | ||
| images | ||
| product | ||
| roadmap | ||
| scaling | ||
| spec | ||
| creating-a-kubernetes-cluster.md | ||
| project-checklist.md | ||
| resources-overview.md | ||
| setting-up-a-docker-registry.md | ||
| setting-up-a-logging-plugin.md | ||
| setting-up-ingress-static-ip.md | ||
| telemetry.md | ||