kubernetes
/
minikube
mirror of https://github.com/kubernetes/minikube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #11471 from EmandM/patch-1 

Update registry.md with instructions to avoid common pitfalls
pull/11567/head
Sharif Elgamal 2021-06-02 13:16:45 -07:00 committed by GitHub
parent d76259e86f c8a6fdfc83
commit 45ee2dbacb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
site/content/en/docs/handbook/registry.md
View File

@ -42,7 +42,8 @@ You can use the `--insecure-registry` flag on the
One nifty hack is to allow the kubelet running in minikube to talk to registries deployed inside a pod in the cluster without backing them
with TLS certificates. Because the default service cluster IP is known to be available at 10.0.0.1, users can pull images from registries
deployed inside the cluster by creating the cluster with `minikube start --insecure-registry "10.0.0.0/24"`.
deployed inside the cluster by creating the cluster with `minikube start --insecure-registry "10.0.0.0/24"`. Ensure the cluster
is deleted using `minikube delete` before starting with the `--insecure-registry` flag.
### docker on macOS
@ -53,6 +54,7 @@ The first step is to enable the registry addon:
```shell
minikube addons enable registry
```
> Note: Minikube will generate a port and request you use that port when enabling registry. That instruction is not related to this guide.
When enabled, the registry addon exposes its port 5000 on the minikube's virtual machine.