Kubernetes has a concept of cluster network, as it can be
IPv4 only, IPv6 only or dual stack depending on the IP famliies
configured for their Pod , Services and Node objects.
Signed-off-by: Antonio Ojea <aojea@google.com>
This PR modifies the "what's next" section of the networking concept
page. The pointer to the **archived** design proposals is only about
the original design and it was archived two years ago. For people
interested on "future plans", they should be redirected to the KEPs
for SIG-Network.
This PR also fixes the line wrapping problems in two paragraphs
(no content changes there).
* Update hyperlinks to point to main branch
* Revert changes to post older than a year ⏪
* Update link to point to localize document 📝
* Fix fragement in the link 📝
change "#the-kubernetes-network-model" to "#how-to-implement-the-kubernetes-networking-model"
* Revert changes in zh localization pages
* Remove changes in files of other localization
Removing this content seems to be appropriate:
Content does not contain a link to a CNI.
Content is not required for k8s to function.
Content seems to be replicated in longer form on the Google Cloud docs site.
Open vSwitch is in no way required for Kubernetes to function. Kubernetes is not mentioned once on this project's website, nor are there any instructions for how you might use this in a k8s environment.
This entry is not necessary for Kubernetes to function. Entry provides a link to the main corporate website, not to any relevant information. No CNI. Acronym refers to product marketing, not an actual technology.
Apstra AOS (now owned by Juniper) has no direct integration with Kubernetes.
No CNI, no operator, no CRDs, nothing.
Kubernetes is not natively supported in the product, there is no mention of any k8s construct in the product.
This entry should be removed because it does not follow https://github.com/kubernetes/website/issues/20232
* Revise Pod concept
Adapt the existing Pod documentation to suit the Docsy theme, by
promoting the Pod concept itself to /docs/concepts/workloads/pods/
Following on from this, update the Pod Lifecycle page to cover the
lifecycle of a Pod and follow on directly from the Pod concept,
for readers keen to understand things in detail.
This change also removes the automatic contents list from the Pod
overview page. Instead, the new page links to all the pages
inside the Pod section.
* Update links to Pod concept
Link to updated content
* Incorporate Pod concept suggestions
Co-authored-by: Celeste Horgan <celeste@cncf.io>
* Revise StatefulSet suggestion for Pod concept
Co-authored-by: Celeste Horgan <celeste@cncf.io>
Co-authored-by: Celeste Horgan <celeste@cncf.io>
* Added a new section on Azure CNI
Azure provides a CNI for native integration of Kubernetes Pods in a Virtual Network. I have added a short description of this CNI and provided links to important documentation
* Update networking.md
* Made updates based on comments
This is much closer to what you are recommending. Please take a look
* Extend Cilium CNI plugin description
Mention that it works on top of other CNI plugins due to the CNI
chaining [1].
[1]: http://docs.cilium.io/en/v1.6/gettingstarted/cni-chaining/
Signed-off-by: Martynas Pumputis <m@lambda.lt>
* Update Cilium installation steps for kubeadm
- Use the latest v1.6 Cilium.
- By default, Cilium no longer needs/deploys ETCD store.
Signed-off-by: Martynas Pumputis <m@lambda.lt>
* Update Cilium NetworkPolicy guide
- Update minikube min version requirement.
- Use Cilium v1.6.
- Remove the etcd store bits, as Cilium v1.6 no longer depend on
it by default.
Signed-off-by: Martynas Pumputis <m@lambda.lt>
* Update Cilium installation steps for kubeadm
- How to run without kube-proxy.
Signed-off-by: Martynas Pumputis <m@lambda.lt>
Co-authored-by: Martynas Pumputis <m@lambda.lt>