Interoperability with ExternalDNS¶
In a Kubernetes environment, you can expose your deployment using a service of type
LoadBalancer. Also, an IP address can be assigned to the service using Citrix IPAM controller. The Citrix IPAM controller assigns IP address to the service from a defined pool of IP addresses. For more information, see Expose services of type LoadBalancer with IP addresses assigned by the IPAM controller.
The service can be accessed using the IP address assigned by the IPAM controller and for service discovery you need to manually register the IP address to a DNS provider. If the IP address assigned to the service changes, the associated DNS record must be manually updated and the entire process becomes cumbersome. In such cases, you can use a ExternalDNS to keep the DNS records synchronized with your external entry points. Also, ExternalDNS allows you to control DNS records dynamically through Kubernetes resources in a DNS provider-agnostic way.
For the ExternalDNS integration to work, the
external-dns.alpha.kubernetes.io/hostname annotation must contain the host name.
Important: For ExtenalDNS to work, ensure that you add the annotation
external-dns.alpha.kubernetes.io/hostnamein the service specification and specify a host name for the service using the annotation.
To integrate with ExternalDNS:
Install the ExternalDNS with Infoblox provider.
Note: The interoperability solution has been tested with Infoblox provider and the solution might work for other providers as well.
Specify the domain name in the ExternalDNS configuration.
In the service of type
LoadBalancerspecification, add the following annotation and specify a host name for the service using the annotation:
Deploy the service using the following command:
kubectl create -f <service-name>.yaml