Pod is the object to be scheduled, So "pod to schedule onto a node " and "pod to schedule on" are not suitable in the doc. "pod to be scheduled onto a node" is better.
Made updates for files, related to IPv6. Note: The release notes
cover 1.9. When 1.10 release notes are added, the comment about
the /66 restriction for IPv6 can be removed.
* fixed the interacting with cluster section for the ubuntu installation
* made changes as per request from zacharysarah
* added rancher stub
* added rancher documentation
* fixed missing capture tag
* added ingress example, fixed languages as per changes in the PR
* fixed page index as per pr
* fixed rancher readme
* Add a note on availability of tcp_syncookies syctl
Sysctl `net.ipv4.tcp_syncookies` is not availalbe on 4.4 kernel
as it's not namespaced yet.
* updating to use {: .note} notation
per https://kubernetes.io/docs/home/contribute/style-guide/#note
This list on the sidebar isn't very useful:
- it's not an exhaustive list
- it's not an up-to-date list either
- design docs are not documentation (they're already stale)
- we already link to the full list from https://kubernetes.io/docs/reference/
home page
Also removing the 'docs/admin/ovs-networking.md' document as per
the pull request comments, it's no longer necessary.
Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>
A common source of beffudlement when using local hypervisors or cloud
providers with peculiar interface setups, IP adressing, or network
policies for which kubelet cannot guess the right IP to use.
`awk` is being used so that the example works in CoreOS Container Linux
too.
Requested in kubernetes/kubeadm#203.
* Please explain N/A's meaning
Because N/A's meaning probably is Not Available/ Not applicable or Name and Address
* all "N/A" change to "Not Available"
all "N/A" change to "Not Available"
* "Available" change to "Applicable"
all "Available" change to "Applicable"
- Moved details of recent releases (1.8 and onward) to the top
- added missing "with" in "compatible with the Kubernetes Container Runtime Interface (CRI)"
* Updating troubleshooting
Changed debug method over to CDK Field Agent and replaced old logging suggestion with the logging page.
* Rewording to hopefully clarify
Please let me know if this still isn't clear. It's a deceptively dense word soup and I wonder if I need to just expand on it some to remove assumptions.