Uploaded image for project: 'OpenStack as Infra'
  1. OpenStack as Infra
  2. OSASINFRA-3549

Switch controlPlaneEndpoint to use FQDN instead of IP

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • BU Product Work
    • 3
    • False
    • None
    • False

      Right now, the API is a NodePort that is backed by an Octavia Load balancer (managed by CCM) and we expose that IP in the HostedCluster.Spec.ControlPlaneEndpoint.

       

      Other platforms don't expose the IP but their FQDN, e.g.

        controlPlaneEndpoint:
          host: api-example-q4s4h.service.hypershift.azure.devcluster.openshift.com
          port: 443 

      Ideally we would like to do the same with OpenStack.

      Because we run on-prem and that DNS is decentralized from the platform, this would very likely mean that the user would provide the desired IP address for the API endpoint. Exactly like we do in the installer.

      Or we rely on the management cluster Ingress like: 

      api.<hosted-cluster-name>.apps.mgmt-cluster.example.com

              Unassigned Unassigned
              emacchi@redhat.com Emilien Macchi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: