Details: See Slack thread at the following link (includes pictures): https://redhat-internal.slack.com/archives/CUPJTHQ5P/p1713377001087529

When creating a dual stack IPv4/IPv6 cluster, users are unable to enter both IPv4 and IPv6 addresses for their ingress and api VIPs.

For example, if using manifests to create a dual stack cluster, here's the mapping with an `agentclusterinstall` manifests:

spec:
  provisionRequirements:
    controlPlaneAgents: 3
    workerAgents: 11
  ingressVIPs:
    - 10.92.68.29
    - '2600:6ce6:4406:4100::29'
  imageSetRef:
    name: img4.14.20-multi-appsub
  platformType: BareMetal
  sshPublicKey: <REDACTED>
  apiVIPs:
    - 10.92.68.28
    - '2600:6ce6:4406:4100::28'
  networking:
    clusterNetwork:
      - cidr: 10.128.0.0/14
        hostPrefix: 23
      - cidr: 'fd05::/48'
        hostPrefix: 64
    machineNetwork:
      - cidr: 10.92.68.0/27
      - cidr: '2600:6ce6:4406:4100::/64'
    networkType: OVNKubernetes
    serviceNetwork:
      - 172.30.0.0/16
      - 'fd06::/112'
    userManagedNetworking: false
  clusterDeploymentRef:
    name: wce-os-mixed-v4
  holdInstallation: true

The fields that are not showing up in the UI at all are the:

• ingressVIPs
• apiVIPs

The user will not be able to continue with their installation, since they will not be able to enter these fields in the UI. They do not show up at all when the user selected the "dual stack" radio button under the networking sections in the Assisted-Service.

Documentation URL: Not sure how to complete this field. I think everything above should help enough though. Please let me know if it isn't (bjozsa@redhat.com or via Slack).