A debugging rabbit hole lead me to digging around kublet's behavior
regarding certain DNS Policies.
This commit updates some potentially misleading wordings to more
correctly convey kubelet's behavior which was discovered after some
rabbit hole debugging of DNS Policies.
The ClusterFirst policy documentation would imply that the resolve.conf
of a Pod would contain a fallback to the Node's nameserver. This is not
the cause, [kubelet explicitly
mentions](4276ed3628/pkg/kubelet/network/dns/dns.go (L403-L407))
that the fallback is handled by whatever system is running kube-dns or
coredns which dramatically changes the behavior of the system when the
cluster's DNS is unavailable.
The ClusterFirstWithHostNet policy is lacking any amount of detail as to
why one would desire to use it. This commit doesn't go into complete
detail but adds an important note about the behavior of `hostNetwork`
when not using the `ClusterFirstWIthHostNet` Policy.
The feature gate MixedProtocolLBService moves to GA state in 1.26.
The documentation of the support of different protocols in the same LB Service is updated.
The existing text implied that creating a node port or load balanced
Service would actually add an extra Service object that you could see in
the Kubernetes API. This isn't true, so avoid implying that it is.
Document EndpointSlice as the preferred and most appropriate mechanism
to record the backing endpoints of a Service.
Co-authored-by: Rob Scott <rob.scott87@gmail.com>
Co-authored-by: Shannon Kularathna <ax3shannonkularathna@gmail.com>
* Make example service account output match 1.24+ output with auto-generated tokens omitted
* Prefer `kubectl create token` as token creation mechanism
* Move Windows storage concepts to a new page
- Move FlexVolume plugins section to docs/concepts/storage/volumes.md
- Move CSI plugins section to en/docs/concepts/storage/volumes.md
- Move in-tree plugins section to en/docs/concepts/storage/volumes.md
* Moving networking related content in
/docs/setup/production-environment/windows to various locations
- Moving windows DNS limitations to/docs/concepts/services-networking/dns-pod-service.md
- Moving windows session sticky time disclaimer to /docs/concepts/services-networking/service.md
- Moving windows dual stack support info to /docs/concepts/services-networking/dual-stack.md
- Moving generic Windows content to
/docs/concepts/services-networking/windows-networking.md
Signed-off-by: Mark Rossetti <marosset@microsoft.com>
* Moving Windows troubleshooting topics to /tasks/debug-application-cluster/
Signed-off-by: Mark Rossetti <marosset@microsoft.com>
* Moving windows containers user guide out of /setup/production-environment/
Signed-off-by: Mark Rossetti <marosset@microsoft.com>
* fixup! Moving windows containers user guide out of /setup/production-environment/
* moving intro-windows-in-kubernetes content out of /setup/production-environment/
Signed-off-by: Mark Rossetti <marosset@microsoft.com>
Co-authored-by: Aravindh Puthiyaparambil <aravindh@redhat.com>
I fixed an imagepulling error in the service.md example on the website. nginx:11.14.2 is no longer on Nginx docker hub: https://hub.docker.com/_/nginx?tab=tags&page=1&name=11.14.2 so I changed the image tag to the latest. please let me know if the latest tag is not the right image to use or if I'm wrong.
For Services without selectors, there is no mention of the requirement that the name of the associated Endpoint object must be the same as the Service name. Thus, I have added that note.
* Feature flag change when moving from alpha to beta
Signed-off-by: Bridget Kromhout <bridget@kromhout.org>
* Update content/en/docs/reference/command-line-tools-reference/feature-gates.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Clarifying default as of beta.
Signed-off-by: Bridget Kromhout <bridget@kromhout.org>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Minor edit for clarity
The previous phrasing didn't emphasize the point that the reason you define a Service with no selectors is to point to a backend that's not a Pod, and the emphasis on the external nature of the backend
* Add note that Services w/o selectors, but +Endpoints is the technique to use for abstracting external backends
Co-authored-by: Rey Lejano <rlejano@gmail.com>
Co-authored-by: Rey Lejano <rlejano@gmail.com>