* Adding annotation example
Adding example to show how annotation looks like in manifest. This will help users to understand where exactly we can use the annotations whose details are already given on this page. Annotation `imageregistry: https://hub.docker.com/` used intentionally to make it more relevant as earlier section talk about registry address annotation.
* Resolving review comments
Resolving review comments
* Add zh/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md
Add zh/examples/pods/lifecycle-events.yaml
Translate zh/includes/task-tutorial-prereqs.md to chinese
* Apply suggestions from code review
Thanks for tengqm's review
Co-Authored-By: Qiming <tengqim@cn.ibm.com>
* Apply suggestions from code review
Thanks for tengqm's help again
Co-Authored-By: Qiming <tengqim@cn.ibm.com>
* Modify the order of text in markdown format
* Unified translation into 处理函数
This patch promotes re-use of the existing kube-proxy glossary
definition by referencing it from overview/components.md. Similarly, we
move the definition of Container Runtime into a new glossary definition
so that other pages may refer to it.
* Update images.md
* Update content/en/docs/concepts/containers/images.md
That works fine and thank you.
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
**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
* Reword glossary entry for Service
New wording should be more suitable for inclusion via a
glossary_definition shortcode.
* Improve What's Next section for Service concept
* Rename Services concept to singular
This matches other concept documentation, eg Deployment.
* Use documentation IP address range
1.2.3.4 is outside the blocks reserved for documentation.
* Reword Service concept description
Services direct traffic to Pods, not containers
* Write IPVS in uppercase
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
* Improve Pivotal row in Production Setup table.
- Provider column should contain company name
- Change check marks to product links to match other rows
Co-authored-by: Danny Berger <dberger@pivotal.io>
* Spell out PKS abbreviation.
Co-authored-by: Danny Berger <dberger@pivotal.io>
* Tweak glossary definition for Node
The services (eg kubelet) that run on a Node are not the kind of
Service that the Kubernetes API knows about. Reword accordingly.
Also, highlight that Docker is one container runtime and that
there are others.
* Adopt suggestions from https://github.com/kubernetes/website/pull/14523
Co-Authored-By: Rael Garcia <me@rael.io>
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
Minor updates:
- Add a full stop.
- Removed the 'Start the tutorial›' section. The sections are already linked from 1 to 6 and this section doe not add any value after point 6.
* 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