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
This commit is contained in:
Claudio Kuenzler
2021-10-08 07:33:34 +02:00
committed by GitHub
parent 7a86366f2b
commit 9eae14a0e5
@@ -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:
`<workload>.<namespace>.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.