-
Notifications
You must be signed in to change notification settings - Fork 5.1k
document --insecure-registry flag #1047
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document --insecure-registry flag #1047
Conversation
|
Can one of the admins verify this patch? |
25f319e to
bd2e1c0
Compare
Current coverage is 34.65% (diff: 100%)@@ master #1047 diff @@
==========================================
Files 43 43
Lines 2000 2000
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
Hits 693 693
Misses 1170 1170
Partials 137 137
|
README.md
Outdated
| `minikube start` command to enable insecure communication between the docker engine and registries listening to reqeusts from the CIDR range. | ||
|
|
||
| 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 service cluster IP range is known to be available at 10.0.0.0/24, users can pull images from registries |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small nit: I think its 10.0.0.1?
minikube/pkg/util/constants.go
Line 23 in a403a94
| DefaultServiceClusterIP = "10.0.0.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch. I'll fix that/make it more clear :)
bd2e1c0 to
63bd5d8
Compare
r2d4
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
closes #1046