Description of problem: Hello Team, with OpenShift 4.4, we enabled NodePortService on ingresscontrollers, spec: endpointPublishingStrategy: type: NodePortService replicas: 2 status: availableReplicas: 2 conditions: - lastTransitionTime: "2020-09-21T19:14:52Z" reason: Valid status: "True" type: Admitted - lastTransitionTime: "2020-09-21T19:15:11Z" The NodePort service created post then does not include nodePort for 1936 port, spec: clusterIP: 172.30.200.47 externalTrafficPolicy: Local ports: - name: http nodePort: 31322 port: 80 protocol: TCP targetPort: http - name: https nodePort: 31048 port: 443 protocol: TCP targetPort: https selector: ingresscontroller.operator.openshift.io/deployment-ingresscontroller: default sessionAffinity: None type: NodePort status: loadBalancer: {} Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Setting the target release to the current development branch so we can identify the problem. We will consider backports once the issue is understood.
WIP PR: https://github.com/openshift/cluster-ingress-operator/pull/466
Target set to next release version while investigation is either ongoing or pending. Will be considered for earlier release versions when diagnosed and resolved. We need to have a discussion about the implications of running out of node ports if we chose to backport this fix.
Fix is posted but may require some design discussion or a release note for handling upgrades. We'll try to get this done in the upcoming sprint.
Still need to investigate and guard against or document migration issues.
Didn't have time to work on this. I'll try to get to it in the upcoming sprint.
No update. Still need to test the proposed fix.
verified with 4.8.0-0.nightly-2021-06-03-221810 and passed. # oc -n openshift-ingress get svc/router-nodeport-nodeport -oyaml <---snip---> spec: clusterIP: 172.30.114.242 clusterIPs: - 172.30.114.242 externalTrafficPolicy: Local ipFamilies: - IPv4 ipFamilyPolicy: SingleStack ports: - name: http nodePort: 30028 port: 80 protocol: TCP targetPort: http - name: https nodePort: 31626 port: 443 protocol: TCP targetPort: https - name: metrics nodePort: 30431 port: 1936 protocol: TCP targetPort: metrics selector: ingresscontroller.operator.openshift.io/deployment-ingresscontroller: nodeport sessionAffinity: None type: NodePort sh-4.4# curl -u dXNlcnBrbGx3:cGFzczQ1cTk3 http://127.0.0.1:30431/metrics | head % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0# HELP go_gc_duration_seconds A summary of the pause duration of garbage collection cycles. # TYPE go_gc_duration_seconds summary go_gc_duration_seconds{quantile="0"} 4.1739e-05 go_gc_duration_seconds{quantile="0.25"} 7.6564e-05 go_gc_duration_seconds{quantile="0.5"} 8.9163e-05
Hi, does this bug require doc text? If so, please update the doc text field.
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438