**your.private.registry.example.com** is a better choice of domain name for a non-existing sample domain name than calling it **yourprivateregistry.com**
refer #14283
Using `rm -Rf ~/.minikube` is not necessary in modern (v1.x) versions of minikube, and is highly discouraged as may can leave dangling VM's running, which minikube will fail to recover from.
Example issue: https://github.com/kubernetes/minikube/issues/4377
without specifying registry details for `image` value, You will get following error if you are using a private registry even when your private images are hosted in docker.hub and you have valid credentials configured for the same.
Failed to pull image "xxx/xxx-app:0.0.1": rpc error: code = Unknown desc = Error response from daemon: pull access denied for xxx/xxx-app, repository does not exist or may require 'docker login'
* document version changes of critical pod
* document system priority class name version requirement
* Update guaranteed-scheduling-critical-addon-pods.md
* Link to 'Add image pull secret to service account'
This page does not mention the fact that image pull secrets can be specified through a service account. So adding link to the section which gives details about 'adding image pull secret to service account'.
* Correcting link url
Correcting link url
* Corrects procedure to get tab completion on Mac
Tab completion only requires the installation of bash-completion and sourcing the bash_completion script.
Installing bash-completion@2 doesn't work and source <(kubectl completion bash) is no longer necessary in the .bash_profile.
* Removed reference to other methods that don't work
* Update install-kubectl.md
The link https://github.com/kubernetes/minikube#other-ways-to-install doesn't exist anymore.
So either we remove the link to it or we fix the minikube README and add a new section for alternative ways to install minikube.
What do you think?
* Link upgrade to skewed version page
It provides the order of upgrade and shows which versions are supported.
Solves (at least partially ) #14420
* Update cluster-management.md
* Update cluster-management.md
* document pod downwardAPI fieldRef & resourceRef values of en version
* document pod downwardAPI fieldRef & resourceRef values of zh version
* typo correction
Both local and pod port number are same i.e. 6379 which causes confusion to first time reader. This can be easily avoided by using two different port number.
* Correcting order of display for daemon set tasks
Correcting order of display for daemon set tasks
* Correcting display order of daemon set task
Correcting display order of daemon set task
here apt installs both kubelet and kubectl but just holds kubelet. I think kubectl should alse be held by apt-mark.
```
# replace x in 1.14.x-00 with the latest patch version
apt-mark unhold kubelet && \
apt-get update && apt-get install -y kubelet=1.14.x-00 kubectl=1.14.x-00 && \
apt-mark hold kubelet
```
This patch swaps all uses with extensions/v1beta1 with the new
networking.k8s.io/v1beta1 apiVersion for the Ingress resource.
Signed-off-by: Christopher M. Luciano <cmluciano@us.ibm.com>
Tim Bannister
Seth
Raja Anbazhagan
Matthew Gallagher
Thomas Strömberg
RA489
Daniel Weibel
Yucheng Wu
icheikhrouhou
Rajesh Deshpande
wangyamei
Misty Linville
Atif Mahmood
Oussema CHERNI
Lennart Jern
Christian Rebischke
Steven Sherry
Prankul
codyc
好风
Oleksandr Slynko
Byron.wang
Karen Bradshaw
Himanshu Pandey
Suhwan Cha
Raj Vaibhav Dubey
Rajesh Deshpande
Neville George
Vitaly R. Samigullin
silenceshell
Vageesha17
Kenichi Omichi
s-ito-ts
Kohei Toyoda
cmluciano