* 'master' of https://github.com/kubernetes/kubernetes.github.io:
  Add no_proxy settings to use minikube and kubectl (#4108)
  Fix installing autocompletion documentation (#4189)
  Set storageClassName to match earlier manual disk creation
reviewable/pr4224/r1
Andrew Chen 2017-06-28 16:39:36 -07:00
commit b9593e8e1d
3 changed files with 9 additions and 4 deletions

View File

@ -281,6 +281,12 @@ $ minikube start --docker-env HTTP_PROXY=http://$YOURPROXY:PORT \
--docker-env HTTPS_PROXY=https://$YOURPROXY:PORT
```
If your Virtual Machine address is 192.168.99.100, then chances are your proxy settings will prevent kubectl from directly reaching it.
To by-pass proxy configuration for this IP address, you should modify your no_proxy settings. You can do so with:
```shell
$ export no_proxy=$no_proxy,$(minikube ip)
```
## Known Issues
* Features that require a Cloud Provider will not work in Minikube. These include:

View File

@ -16,6 +16,7 @@ metadata:
spec:
accessModes:
- ReadWriteOnce
storageClassName: ""
resources:
requests:
storage: 20Gi

View File

@ -183,12 +183,10 @@ Follow the "caveats" section of brew's output to add the appropriate bash comple
If you've installed kubectl using the [Homebrew instructions](#install-with-homebrew-on-macos) then kubectl completion should start working immediately.
If you have installed kubectl manually, then run: `source <(kubectl completion bash)`
To add kubectl autocompletion to your profile (so it is automatically loaded in future shells):
If you have installed kubectl manually, you need to add kubectl autocompletion to the bash-completion:
```shell
echo "source <(kubectl completion bash)" >> ~/.bash_profile
kubectl completion bash > $(brew --prefix)/etc/bash_completion.d/kubectl
```
The Homebrew project is independent from kubernetes, so the bash-completion packages are not guaranteed to work.