Skip to content

OCPBUGS-61097: Remove port 9447 from documented network flow matrix#99334

Merged
slovern merged 1 commit intoopenshift:enterprise-4.17from
shirmoran:remove-9447-from-network-flow-matrix
Oct 2, 2025
Merged

OCPBUGS-61097: Remove port 9447 from documented network flow matrix#99334
slovern merged 1 commit intoopenshift:enterprise-4.17from
shirmoran:remove-9447-from-network-flow-matrix

Conversation

@shirmoran
Copy link

@shirmoran shirmoran commented Sep 18, 2025

As it was decided that the machine api webhook port (9447) should not be exposed to the host (see PR), it should be removed from the official doc.

Version(s):

4.17

Issue:

https://issues.redhat.com/browse/OCPBUGS-61097

Link to docs preview:

OpenShift Container Platform network flow matrix -- Remove a line from Table 2.1.

QE review:

  • QE has approved this change.

Additional information:

As it was decided that the machine api webhook port (9447) should not be exposed to the host (see [PR](openshift/cluster-baremetal-operator#505)), it should be removed from the official doc.
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 18, 2025
@shirmoran shirmoran changed the title Remove port 9447 from documented network flow matrix OCPBUGS#61097: Remove port 9447 from documented network flow matrix Sep 18, 2025
@shirmoran
Copy link
Author

/label peer-review-needed

@openshift-ci
Copy link

openshift-ci bot commented Sep 18, 2025

@shirmoran: The label(s) /label peer-review-needed cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, ok-to-test, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, stability-fix-approved, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label peer-review-needed

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-sigs/prow repository.

@shirmoran
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@shirmoran: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

/jira refresh

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.

@shirmoran shirmoran changed the title OCPBUGS#61097: Remove port 9447 from documented network flow matrix OCPBUGS-61097: Remove port 9447 from documented network flow matrix Sep 18, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 18, 2025
@openshift-ci-robot
Copy link

@shirmoran: This pull request references Jira Issue OCPBUGS-61097, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

As it was decided that the machine api webhook port (9447) should not be exposed to the host (see PR), it should be removed from the official doc.

Version(s):

4.17

Issue:

https://issues.redhat.com/browse/OCPBUGS-61097

Link to docs preview:

OpenShift Container Platform network flow matrix -- Remove a line from Table 2.1.

QE review:

  • QE has approved this change.

Additional information:

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.

@shirmoran
Copy link
Author

/label peer-review-needed

@openshift-ci
Copy link

openshift-ci bot commented Sep 18, 2025

@shirmoran: The label(s) /label peer-review-needed cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, ok-to-test, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, stability-fix-approved, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label peer-review-needed

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-sigs/prow repository.

@ocpdocs-previewbot
Copy link

🤖 Thu Sep 18 14:26:47 - Prow CI generated the docs preview:

https://99334--ocpdocs-pr.netlify.app/

@openshift-ci
Copy link

openshift-ci bot commented Sep 18, 2025

@shirmoran: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@jadhaj
Copy link

jadhaj commented Sep 30, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 30, 2025
@openshift-ci-robot
Copy link

@shirmoran: This pull request references Jira Issue OCPBUGS-61097, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

As it was decided that the machine api webhook port (9447) should not be exposed to the host (see PR), it should be removed from the official doc.

Version(s):

4.17

Issue:

https://issues.redhat.com/browse/OCPBUGS-61097

Link to docs preview:

OpenShift Container Platform network flow matrix -- Remove a line from Table 2.1.

QE review:

  • QE has approved this change.

Additional information:

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.

@slovern slovern added this to the Continuous Release milestone Oct 2, 2025
@slovern slovern merged commit 6dadda5 into openshift:enterprise-4.17 Oct 2, 2025
2 checks passed
@openshift-ci-robot
Copy link

@shirmoran: Jira Issue OCPBUGS-61097 is in an unrecognized state (Closed) and will not be moved to the MODIFIED state.

Details

In response to this:

As it was decided that the machine api webhook port (9447) should not be exposed to the host (see PR), it should be removed from the official doc.

Version(s):

4.17

Issue:

https://issues.redhat.com/browse/OCPBUGS-61097

Link to docs preview:

OpenShift Container Platform network flow matrix -- Remove a line from Table 2.1.

QE review:

  • QE has approved this change.

Additional information:

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.

@shirmoran
Copy link
Author

/cherry-pick enterprise-4.16

@openshift-cherrypick-robot

@shirmoran: #99334 failed to apply on top of branch "enterprise-4.16":

Applying: Remove port 9447 from documented network flow matrix As it was decided that the machine api webhook port (9447) should not be exposed to the host (see [PR](https://github.com/openshift/cluster-baremetal-operator/pull/505)), it should be removed from the official doc.
Using index info to reconstruct a base tree...
M	snippets/network-flow-matrix.csv
Falling back to patching base and 3-way merge...
Auto-merging snippets/network-flow-matrix.csv
CONFLICT (content): Merge conflict in snippets/network-flow-matrix.csv
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Remove port 9447 from documented network flow matrix As it was decided that the machine api webhook port (9447) should not be exposed to the host (see [PR](https://github.com/openshift/cluster-baremetal-operator/pull/505)), it should be removed from the official doc.

Details

In response to this:

/cherry-pick enterprise-4.16

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-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.17 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants