APIServerLB DNS name resolution causes deploy failure on air-gapped systems #4975
Labels
kind/bug
Categorizes issue or PR as related to a bug.
needs-priority
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
/kind bug
What steps did you take and what happened:
After CAPA creates the APIServer Load Balancer and it gets a DNS name, CAPA waits for the DNS name to resolve before continuing the installation [1][2]. I think this check was never reconsidered when support for a secondary LB was added.
Now consider the scenario where a cluster is deployed on an air-gapped system. Trying to resolve the LB DNS name will never succeed .
[1] #1641
[2] #1651
What did you expect to happen:
Only check for DNS name resolution when the APIServer LB is public.
Anything else you would like to add:
Air-gapped installations are a requirement in C2S/SC2S secret regions.
Environment:
kubectl version
): 1.29/etc/os-release
):The text was updated successfully, but these errors were encountered: