As part of the 4.1 rebase, we need to add support for the api-int DNS name. Unfortunately, because this is used during ignition (before we configure nodes to point at coredns) just adding a static entry in coredns is not sufficient. #523 is adding it to the libvirt dnsmasq, but this essentially makes it a required external record. Since it's actually for internal use only, we shouldn't be requiring that.
This issue is to track the tech debt associated with api-int and provide a reference for the work to remove the external DNS requirement. Currently the plan is to point ignition directly at the VIP and then switch to using api-int once we've configured the nodes to point at coredns.
As part of the 4.1 rebase, we need to add support for the api-int DNS name. Unfortunately, because this is used during ignition (before we configure nodes to point at coredns) just adding a static entry in coredns is not sufficient. #523 is adding it to the libvirt dnsmasq, but this essentially makes it a required external record. Since it's actually for internal use only, we shouldn't be requiring that.
This issue is to track the tech debt associated with api-int and provide a reference for the work to remove the external DNS requirement. Currently the plan is to point ignition directly at the VIP and then switch to using api-int once we've configured the nodes to point at coredns.