From 9eae14a0e5d16beb1e76bbe25998659631fb949c Mon Sep 17 00:00:00 2001 From: Claudio Kuenzler Date: Fri, 8 Oct 2021 07:33:34 +0200 Subject: [PATCH] New service creation behaviour (needs Port configuration) Update documentation according to the new "Explorer" UI behaviour. Creating a new workload alone is not enough that a Kubernetes service is created in the background. The new workload needs to have at least one port configured. See also https://github.com/rancher/rancher/issues/34653 --- .../rancher/v2.6/en/k8s-in-rancher/service-discovery/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/k8s-in-rancher/service-discovery/_index.md b/content/rancher/v2.6/en/k8s-in-rancher/service-discovery/_index.md index 5b76fd43355..106bce3715d 100644 --- a/content/rancher/v2.6/en/k8s-in-rancher/service-discovery/_index.md +++ b/content/rancher/v2.6/en/k8s-in-rancher/service-discovery/_index.md @@ -5,7 +5,7 @@ weight: 3045 Pod configuration is managed by Deployments, StatefulSets and Daemonsets, whereas services direct traffic to pods using selectors. -For every workload created, a complementing Service Discovery entry is created. This Service Discovery entry enables DNS resolution for the workload's pods using the following naming convention: +For every workload (with at least one port configured) created, a complementing Service Discovery entry is created. This Service Discovery entry enables DNS resolution for the workload's pods using the following naming convention: `..svc.cluster.local`. You can create additional services so that a given namespace resolves with one or more external IP addresses, an external hostname, an alias to another DNS record, other workloads, or a set of pods that match a selector that you create.