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>
* 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
* Update network doc for ip-per-pod reqs
As per SIG-Network discussion, we can relax the requirement for all
nodes to be able to reach all pods on those platforms that do not
support hostNetwork.
The current thinking on Windows support is that hostNetwork is not a
requirement for Window users. As such, satisfying the old requirement
is very difficult and has no practical benefit.
This DOES NOT change the requirements for platforms that support
hostNetwork (e.g. Linux) nor does it make hostNetwork optional for Linux
nodes.
This PR also removes most comparisons to Docker, as they are stale and
no longer germane, and cleans up some of the text.
* Feedback on contents
* OpenContrail -> Tungsten Fabric
OpenContrail has joined the Linux Foundation Networking Fund and rebranded as Tungsten Fabric to better reflect its open community engagement separate from its Juniper Network roots.
This edit updates the doc to reflect the name change and that Tungsten Fabric is a separate entity from Juniper's Contrail product.
* Include TF in the header
To further reinforce that Contrail and TF are different things.
* Adding DANM
Adding a new item to the list of cluster networking
solutions.
Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
* Corrections of received comments
for https://github.com/kubernetes/website/pull/10679
Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
* add Jaguar project description
[Jaguar](https://gitlab.com/sdnlab/jaguar) is an open source solution for Kubernetes's network based on OpenDaylight.
Jaguar provides overlay network using vxlan and Jaguar CNIPlugin provides one IP address per pod.
* Minor newline tweak
Antonio Ojea
Kubernetes Prow Robot
Jesse Butler
ixodie
Bridget Kromhout
Tim Allclair
Ritikaa96
mateusz
bl-ue
Yamamoto, Hirotaka
Laurence Man
Celeste Horgan
Qiming Teng
Tim Bannister
Karen Bradshaw
Kuralamudhan Ramakrishnan
Aanand Ramachandran
André Martins
GoodGameZoo
Yasen Simeonov
Andrew Sy Kim
Oilbeater
Nate Taber
yanghaichao12
Shashank Patel
Tim Hockin
Andy Randall
Roy Lenferink
Becca Powell
VM Brasseur
Gergely Csatari
MengZeLee
Yuexiao Wang
Gianpaolo Macario
PONOUBA