OCPBUGS-76560: [release-4.18]: cherry pick to few fixes that needed for missing services and configuration#5653
Conversation
- Added `hostIP: 127.0.0.1` to the containerPort 8798 to explicitly indicate
that the health port is only bound to localhost.
- Matches the existing behavior in logs:
"Starting health listener on 127.0.0.1:8798"
and address config: Addr: "127.0.0.1:8798"
- This is informational and clarifies that this port is not externally exposed.
|
@aabughosh: This pull request references Jira Issue OCPBUGS-67264, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@aabughosh: No Jira issue is referenced in the title of this pull request. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira cherrypick OCPBUGS-67264 |
|
@yuqi-zhang: Jira Issue OCPBUGS-67264 has been cloned as Jira Issue OCPBUGS-76560. Will retitle bug to link to clone. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@aabughosh: This pull request references Jira Issue OCPBUGS-76560, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
yuqi-zhang
left a comment
There was a problem hiding this comment.
/lgtm
/label backport-risk-assessed
Should be a safe backport, only diff was the arbiter template which didn't exist in 4.18
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aabughosh, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/verified later @aabughosh |
|
@yuqi-zhang: This PR has been marked to be verified later by DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
|
@aabughosh: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
d4eb710
into
openshift:release-4.18
|
@aabughosh: Jira Issue OCPBUGS-76560: All pull requests linked via external trackers have merged: This pull request has the DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
Fix included in accepted release 4.18.0-0.nightly-2026-02-12-181411 |
This is an automated cherry-pick of #5490
/assign yuqi-zhang
- What I did
- How to verify it
- Description for the changelog