Update and rename cnf-best-practices-application-dns-configuration-requirements.adoc to k8s-best-practices-application-dns-configuration-requirements.adoc

Author: mwlinca

modules/cnf-best-practices-application-dns-configuration-requirements.adoc renamed to modules/k8s-best-practices-application-dns-configuration-requirements.adoc

@@ -1,8 +1,8 @@
-[id="cnf-best-practices-application-dns-configuration-requirements"]
+[id="k8s-best-practices-application-dns-configuration-requirements"]
 [id="application-dns-configuration-requirements"]
 = Application DNS configuration requirements
 
-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.
+Workloads 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.
 
 .Example
 [source,terminal]
@@ -17,13 +17,11 @@ If an application deploys a service in the namespace `clspcoykvzwcscp-y-xx-w1-00
 
 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.
 
-.VCP CNF requirement - Doors Id 94182
 [IMPORTANT]
 ====
-CNFs must use the service name only as a configuration parameter for attaching to a service within your namespace
+Workloads must use the service name only as a configuration parameter for attaching to a service within your namespace
 ====
 
-.VCP CNF requirement - Doors Id 94183
 [IMPORTANT]
 ====
 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