* 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>
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>
Make 100% clear, that according to the k8s networking model pods are supposed to get their own unique IP address. I always thought this was the case. But then faced debugging issue where some pods are being assigned the same IP addresses. Came here to review my understanding of it, and confirm this is expected behaviour or not. But it was not stated unequivocally. This change makes it so.