Uploaded image for project: 'openstack-k8s'
  1. openstack-k8s
  2. OSPK8-820

Suggested OSPdO OpenStackProvisionServer port can conflict with OCP cluster network operator

XMLWordPrintable

    • 1
    • False
    • None
    • False
    • Moderate

      In OCP 4.16+, the cluster network operator now listens on port 8080 on one of the master nodes. So in a 3-node master/worker combo scenario, we could run into a collision with the default 8080 port we suggest for the OpenStackProvisionServer:

      tcp   LISTEN     0      4096                                         *:8080                        *:*     users:(("cluster-network",pid=100006,fd=9))  

      Let's use 6190 instead, as we do in the newer RHOSO OpenStack Baremetal operator.

              abays@redhat.com Andrew Bays
              abays@redhat.com Andrew Bays
              rhos-dfg-ospk8s
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: