Description of problem: No 'egressip' column when run 'oc get hostsubnet' or 'oc get netnamespaces' Version-Release number of selected component (if applicable): 4.1.0-0.nightly-2019-05-07-233329 How reproducible: always Steps to Reproduce: 1. oc get hostsubnet 2. oc get netnamespaces 3. Actual results: no egressip column Expected results: egressip should be shown. Additional info: The egressip function works well. just the client side cannot be shown the egressip, it's not convenient. I guess we just add one column in crd. eg: additionalPrinterColumns: - JSONPath: .host description: The name of the node name: Host type: string - JSONPath: .hostIP description: The IP address to be used as a VTEP by other nodes in the overlay network name: Host IP type: string - JSONPath: .subnet description: The CIDR range of the overlay network assigned to the node for its pods name: Subnet type: string conversion: strategy: None group: network.openshift.io names:
Strikes me as an RFE, but a good idea.
Oh duh, I misunderstood this bug. Yes, we should update the CRD to include these columns. The CRDs defined in openshift-sdn should have, as much as possible, the same printer columns as they did in 3.11.
Hi A PR addressing this has been merged: https://github.com/openshift/cluster-network-operator/pull/241 Best regards Alexander
Verified this bug on 4.2.0-0.nightly-2019-07-24-000310 The egress ip can be shown. oc get hostsubnet ip-10-0-141-238.ap-northeast-1.compute.internal -o wide NAME HOST HOST IP SUBNET EGRESS CIDRS EGRESS IPS ip-10-0-141-238.ap-northeast-1.compute.internal ip-10-0-141-238.ap-northeast-1.compute.internal 10.0.141.238 10.128.2.0/23 [10.66.146.1/24] [10.66.146.100] $ oc get netnamespaces z1 NAME NETID EGRESS IPS z1 16032885 [10.66.146.100]
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922