Merge pull request #14512 from johngmyers/kubenet-doc

Remove obsolete kubenet information from networking.md
This commit is contained in:
Kubernetes Prow Robot 2022-11-08 22:52:23 -08:00 committed by GitHub
commit 40a9b20544
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 17 deletions

View File

@ -13,7 +13,7 @@ listed below, are available which implement and manage this abstraction.
The following table provides the support status for various networking providers with regards to kOps version:
| Network provider | Experimental | Stable | Deprecated | Removed |
| ------------ | -----------: | -----: | ---------: | ------: |
|------------------|-------------:|-------:|-----------:|----------------:|
| AWS VPC | 1.9 | 1.21 | - | - |
| Calico | 1.6 | 1.11 | - | - |
| Canal | 1.12 | - | - | - |
@ -60,8 +60,6 @@ Kubenet is the default networking option because of its simplicity, however, it
production clusters which expect a gradual increase in traffic and/or workload over time. Such clusters
will eventually "out-grow" the `kubenet` networking provider.
For more on the `kubenet` networking provider, please see the [`kubenet` section of the Kubernetes documentation](https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#kubenet).
### CNI
[Container Network Interface](https://github.com/containernetworking/cni) provides a specification
@ -111,7 +109,6 @@ You will notice that `kube-dns` and similar pods that depend on pod networks fai
Here are some steps items that will confirm a good CNI install:
- `kubelet` is running with the with `--network-plugin=cni` option.
- The CNS provider started without errors.
- `kube-dns` daemonset starts.
- Logging on a node will display messages on pod create and delete.