The migration to PowerDNS as the authoritative DNS source and the introduction of Bifurcated CAN (Customer Access Network) will result in some changes to the node and service naming conventions.
Fully qualified domain names will be introduced for all DNS records.
Canonical name: hostname.network-path.system-name.site-domain
hostname - The hostname of the node or servicenetwork-path - The network path used to access the node
system-name - The customer defined name of the systemsite-domain - The top-level domainIt will be possible to refer to a hostname via a short name consisting of hostname.network-path, for example ncn-w001.nmn.
Underscores (_) will be removed from all names in favor of hyphens (-) to ensure compliance with RFC 1035.
Network paths such as -nmn and -hmn in the hostname will be removed. The fully qualified domain name will be used to define the network path.
Kubernetes services that were accessed via the .local domain will now be accessed via a fully qualified domain name.
The old service and node names will not be migrated to PowerDNS however they will be maintained in Unbound as local records for the purpose of backwards compatibility. These records will be removed entirely in a future release when the cray-dns-unbound-manager job is deprecated. Unbound will remain as the front-end cache.
The user and administrative traffic segregation introduced by Bifurcated CAN has changed the URLs for certain services as it is now necessary to include the network path in the fully qualified domain name.
In the following table of examples the Backwards Compatible column indicates whether the old DNS name can be expected to function in CSM 1.2.
The following table of examples assumes that the system was configured with a system-name of shasta and a site-domain of dev.cray.com
| Old Name | New Name | Short name | Backwards Compatible |
|---|---|---|---|
| api-gw-service-nmn.local | api.nmnlb.shasta.dev.cray.com | api.nmnlb | Yes |
| registry.local | registry.nmnlb.shasta.dev.cray.com | registry.nmnlb | Yes |
| packages.local | packages.nmnlb.shasta.dev.cray.com | packages.nmnlb | Yes |
| spire.local | spire.nmnlb.shasta.dev.cray.com | spire.nmnlb | Yes |
| rgw-vip.nmn rgw-vip.nmn.local |
rgw-vip.nmn.shasta.dev.cray.com | rgw-vip.nmn | Yes |
| rgw-vip.hmn rgw-vip.hmn.local |
rgw-vip.hmn.shasta.dev.cray.com | rgw-vip.hmn | Yes |
| ncn-w001 | ncn-w001.nmn.shasta.dev.cray.com | ncn-w001.nmn | Yes |
| ncn-w001-mgmt | ncn-w001-mgmt.hmn.shasta.dev.cray.com | ncn-w001-mgmt.hmn | Yes |
| nid000001-nmn | nid000001.nmn.shasta.dev.cray.com | nid000001.nmn | Yes |
| x3000c0s2b0 | x3000c0s2b0.hmn.shasta.dev.cray.com | x3000c0s2b0.hmn | Yes |
| x3000c0s2b0n0 | x3000c0s2b0n0.nmn.shasta.dev.cray.com | x3000c0s2b0n0.nmn | Yes |
| x1000c5s0b0n0h0 | x1000c5s0b0n0h0.hsn.shasta.dev.cray.com | x1000c5s0b0n0h0.hsn | Yes |
| x1000c5s0b0n0h1 | x1000c5s0b0n0h1.hsn.shasta.dev.cray.com | x1000c5s0b0n0h1.hsn | Yes |
| auth.shasta.dev.cray.com | auth.cmn.shasta.dev.cray.com | No | |
| nexus.shasta.dev.cray.com | nexus.cmn.shasta.dev.cray.com | No | |
| grafana.shasta.dev.cray.com | grafana.cmn.shasta.dev.cray.com | No | |
| prometheus.shasta.dev.cray.com | prometheus.cmn.shasta.dev.cray.com | No | |
| alertmanager.shasta.dev.cray.com | alertmanager.cmn.shasta.dev.cray.com | No | |
| vcs.shasta.dev.cray.com | vcs.cmn.shasta.dev.cray.com | No | |
| kiali-istio.shasta.dev.cray.com | kiali-istio.cmn.shasta.dev.cray.com | No | |
| s3.shasta.dev.cray.com | s3.cmn.shasta.dev.cray.com | No | |
| sma-grafana.shasta.dev.cray.com | sma-grafana.cmn.shasta.dev.cray.com | No | |
| sma-kibana.shasta.dev.cray.com | sma-kibana.cmn.shasta.dev.cray.com | No | |
| api.shasta.dev.cray.com | api.cmn.shasta.dev.cray.com api.chn.shasta.dev.cray.com api.can.shasta.dev.cray.com |
No |