Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

for each DNS Update Record find the KV pair for this intent in either the logical cloud or a cluster prepare a list of clusters that apply
Code Block
themeMidnight
titleDNS Endpoint CRD generation algorithm
Intent processing algorithm
collapsetrue
	Get the TC Intent Set - and acquire the Inbound Intents
	Get the Generic Placement Intents to find the list of logical-clouds for this intentcomposite app
	For each inbound forintent eachin clusterthe TC set (e.g. each App with an inbound for each sub-app with an external FQDN definedintent)
		If externalName and publicDomain (e.g. in an ISTIO gateway)
            acquire the IP(s)FQDN: <externalName>.<publicDomain>) are set
			Identify the logical-cloud associated with the App
			Query the logical-cloud KV for the DNS Update Record list associated with clusterthe andlogical scope of thecloud
			For all DNS ProviderUpdate Records
				Create an external-dns deployment for the Provider information in the DNS Update Record
					Source will be DNSendpointCRs labeled with  create DNSendpointCRD(s) manifests including a label with the DNSproviderNamethis composite-app/dns-context (e.g. logical cloud context)
			For each cluster in which this app is deployed
				Obtain the IP address for public network access
				Create/Update the DNSendpointCRD with endpoints for this App
		If externalName and localDomain (e.g. FQDN: <externalName>.<localDomain>) are set
			Query the cluster KV for the DNS Update Record list associated with the cluster
			For each logical cloud this app is deployed to
				For each cluster this app is deployed to
					For all DNS Update Records in the logical cloud 'dns-update-record-list' KV pair
						Create an external-dns deployment
							Source will be DNSendpointCRs labeled with this composite-app/dns-context (e.g. cluster context)
Create DNSendpointCRD records to be handled by this deployment

Notes:

  • There will need to be a way to find the appropriate set of IPs to use.  Some IPs will be appropriate for a public scope (e.g. update a DNS Provider associated with the logical cloud) and others may be local to the cluster network (e.g. cluster DNS Providers).

...