[release-4.8] Bug 2109329: Avoid kubernetes node port range #187
Conversation
Per [0], the range 30000-32767 is used for kubernetes node ports. We should not have haproxy listening in that range to avoid possible conflicts. Setting the port to 20000 higher than the service port, per the network team convention[1]. 0: https://github.com/openshift/openshift-docs/blob/main/modules/installation-network-user-infra.adoc 1: openshift/enhancements#1076 (comment)
|
@openshift-cherrypick-robot: Bugzilla bug 2101794 has been cloned as Bugzilla bug 2109329. Retitling PR to link against new bug. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci
bot
changed the title
openshift-ci
bot
added
bugzilla/severity-medium
|
@openshift-cherrypick-robot: This pull request references Bugzilla bug 2109329, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/retest |
|
/retest |
openshift-ci
bot
added
the
backport-risk-assessed
|
/retest-required |
openshift-ci
bot
added
bugzilla/valid-bug
|
@cybertron: This pull request references Bugzilla bug 2109329, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/lgtm @reihl Can you approve this cherry-pick please? |
openshift-ci
bot
added
lgtm
|
/cherry-pick-approved |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cybertron, openshift-cherrypick-robot, siserafin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest @reihl It looks like that didn't take. You may have to do "/label cherry-pick-approved". |
|
@openshift-cherrypick-robot: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/cherry-pick-approved |
|
@reihl The bot doesn't seem to have a dedicated command for this. I think you need to use an explicit /label command. |
|
/label cherry-pick-approved |
openshift-ci
bot
added
the
cherry-pick-approved
|
@openshift-cherrypick-robot: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with Bugzilla bug 2109329 has not been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build ose-baremetal-runtimecfg-container-v4.8.0-202311261141.p0.gc50d793.assembly.stream for distgit baremetal-runtimecfg. |
This is an automated cherry-pick of #182
/assign cybertron