Init Containers were specified using custom annotations in k8s 1.5. In
k8s 1.6, these annotations were replaced with the
`Pod.Spec.initContainers` collection and the old annotations were
deprecated in 1.6 and no longer supported in 1.8. There's no reason to
clutter the docs with the old annotation syntax.
Removed ambiguous word 'temporarily', as namespace set using that method, is not temporary. It is permanent for a current resource and there is no concept of a temporary namespace in K8s.
Also, for consisteny '--namespace' flag added after the actual command.
* Updates HAProxy Ingress Controller information to point to new controller supported by haproxytech
* Update content/en/docs/concepts/services-networking/ingress-controllers.md
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* Added listing for AWS VPC CNI
Added listing for AWS VPC CNI under "How to implement the Kubernetes networking model".
* Added AWS VPC CNI
* Added AWS VPC CNI to Installing a pod network add-on
* Updated tabs to alphabetical order
* Adding what's new section to namespace concepts
To learn more about namespaces and give better navigation this section is added.
* Update namespaces.md
* Updates the What is Kubernetes page
* Adds content to the what is kubernetes used for section.
* Updates the ordered list.
* Formats the content.
* Update the content as per the comments
* Fix a broken link
* Highlight feature state for Ingress concept
* Fix command output marked as shell script
* Write "load balancer" as two words
* Clarify prerequisites for Ingress
* Tidy & reword
* Add link to Ingress Controllers topic
(further reading)
* Use a glossary tooltip for Secret
(readers may not have encountered that concept yet)
* Update term definitions in Ingress concept
- Adopt wording from glossary
(NB: glossary_definition shortcode didn't seem suitable)
- Replace terms with glossary_tooltip where appropriate
* feat: add job application has some error and restartPolicy is not Nerver pod will be delete note
* feat: optimize delete pods related suggestion
* Update jobs-run-to-completion.md
* clarify Conditions section in arch/nodes.md
The field name is `conditions` (plural), so have the section name match
the field name. In addition, updates the JSON output of an individual
Condition to match all the fields returned in k8s 1.14+.
* add information about Allocatable to nodes.md
Since k8s 1.6, a Node object returns information about both the node's
capacity as well as the allocatable resources on the node. The latter is
a representation of the resources that are available for normal pods to
consume.
This patch adds information about capacity vs. allocatable to the
documentation about nodes and provides a link to where the reader can
find more information about reserving compute resources.
* Correction: sysctl entries aren't annotations
First, thank you for your work on this documentation. It means so much to so many users. I found that the sysctl documentation linked here explains that sysctl pod security policy entries are in the spec field, not done via annotation. This corrects it, using as much of the original language as possible from the linked sysctl documentation.
* Update pod-security-policy.md
* Adding example to show labels in POD yaml
This page talk about labels and its usage. Also it talk about syntax for specifying labels. But it does not show how we can have labels in resource manifest. So with this PR i am adding example which shows that how we can have labels in pod manifest.
* Changes to resolve review comments
Changes to resolve review comments
* 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
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>
* 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
* Use glossary references where appropriate
* Link from Pod overview to detailed Pod concept
* Assume that privileged containers are stable
* Improve wording
* Write Pod in upper case
As Pod is an API object, write it in upper case.
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>