* 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>
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.
* fix: add missing word 📝
* apply suggestions from code review
Co-authored-by: Jihoon Seo <46767780+jihoon-seo@users.noreply.github.com>
Co-authored-by: Jihoon Seo <46767780+jihoon-seo@users.noreply.github.com>
Credit to Tim Bannister <tim@scalefactory.com> for the same improvements
in load-balancer-nodeport-allocation above.
Signed-off-by: Paul "TBBle" Hampson <Paul.Hampson@Pobox.com>
Looks like this was overlooked to be updated when the feature gate documentation was updated in #28770.
Signed-off-by: Paul "TBBle" Hampson <Paul.Hampson@Pobox.com>
1. Remove examples contrasting k8s networking with Docker networking
from concept document explaining connecting applications using services
2. Remove reference to dockerlinks in favor of English description
of the env vars autocreated for every Service.
Use tabs for the two different options that an IngressClass can use to
refer to another object, in order to specific parameters that relate to
that IngressClass:
- namespaced scope
- cluster scope (the default / historical behavior)
* Fix broken anchor link of #type-nodeport in service.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in overview.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in ingress.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in troubleshooting-kubeadm.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in connecting-frontend-backend.md
* Update anchor link from #nodeport to #type-nodeport
Update anchor link from #nodeport to #type-nodeport in source-ip.md