Skip to content

Commit d812b11

Browse files
authored
Add files via upload
1 parent 44df09c commit d812b11

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
[id="cnf-best-practices-application-dns-configuration-requirements"]
2+
[id="application-dns-configuration-requirements"]
3+
= Application DNS configuration requirements
4+
5+
CNFs should use the service name only as a configuration parameter for attaching to a service within your namespace, the cluster will append namespace name and kubernetes service nomenclature on behalf of the application via search string in DNS. This allows a generic name for a service that works in all clusters no matter what the namespace name is and what the cluster base FQDN is.
6+
7+
.Example
8+
[source,terminal]
9+
----
10+
search clspcoykvzwcscp-y-xx-w1-001.svc.cluster.local
11+
svc.cluster.local cluster.local kub2-4.csp-1.vzwops.com
12+
nameserver 198.223.0.10
13+
options ndots:5
14+
----
15+
16+
If an application deploys a service in the namespace `clspcoykvzwcscp-y-xx-w1-001` and is attempting to access a service named `worker`, the application should just configure the client of the service with an FQDN of `worker`.
17+
18+
The DNS search suffix will append `clspcoykvzwcscp-y-xx-w1-001.svc.cluster.local` to the end of the name and result in a successful query for `worker.clspcoykvzwcscp-y-xx-w1-001.svc.cluster.local`. This allows an application to be less aware of the application's namespace name and genericize the configuration of the application.
19+
20+
.VCP CNF requirement - Doors Id 94182
21+
[IMPORTANT]
22+
====
23+
CNFs must use the service name only as a configuration parameter for attaching to a service within your namespace
24+
====
25+
26+
.VCP CNF requirement - Doors Id 94183
27+
[IMPORTANT]
28+
====
29+
For FQDNs that are outside of their namespace (in another cluster or in the same cluster), applications must append a . at the end of the FQDN so as not to trigger search strings for the FQDN
30+
====
31+
32+
.Example
33+
[source,terminal]
34+
----
35+
nnrfe1-000.bbtpnj33.ne.nrf.5gc.vzims.com
36+
clspcoykvzwcscp-y-xx-w1-001-scp-cache-headless.clspcoykvzwcscp-y-xx-w1-001.svc.cluster.local
37+
----
38+
39+
For more information, see link:https://kubernetes.io/docs/concepts/services-networking/dns-pod-service[Kubernetes upstream reference for pod/service names and DNS].

0 commit comments

Comments
 (0)