Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-53064

Missing ports Field in Container Spec

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • 4.16, 4.17, 4.18, 4.19
    • Etcd
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

       We are working on the Communication Matrix project (commatrix)https://github.com/openshift-kni/commatrix , using EndpointSlice to list all open ports in the cluster. We extract which pod and container are using each port, and we noticed that your pod operator doesn’t have a port assigned in the container spec—it's only specified in the command. Could you please add the port number to the container spec

      Version-Release number of selected component (if applicable):

          

      How reproducible:

          get the pod describe of the cluster verison or get yaml pod info    

      Steps to Reproduce:

          1. kubectl describe pod etcd-clus0-0 -n openshift-etcd      2.
          3.
          

      Actual results:

          Port:          <none>  
      Port is set to <none>, meaning there is no port defined in the container spec. Instead, the port is only specified in the command arguments, which makes it harder for us to determine which container is using the port.

      Expected results:

          expected to have on the container of that port the port number
      talking about port 9979 and 2379 that are just mentioned on the container command

      Additional info:

          

              dwest@redhat.com Dean West
              aabugosh amal abu gosh
              None
              None
              Ge Liu Ge Liu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: