Skip to content

RFE-9862: Document Podman default subnet overlap on RHCOS nodes - #119747

Open
DeokarT wants to merge 1 commit into
openshift:mainfrom
DeokarT:rfe-9862-podman-subnet-docs
Open

RFE-9862: Document Podman default subnet overlap on RHCOS nodes#119747
DeokarT wants to merge 1 commit into
openshift:mainfrom
DeokarT:rfe-9862-podman-subnet-docs

Conversation

@DeokarT

@DeokarT DeokarT commented Sep 11, 2026

Copy link
Copy Markdown

RFE-9862. Same collision as OCPBUGS-9296: oc debug plus a plain podman run brings up 10.88.0.0/16, and that route can stay after the container is gone.

This PR only documents the workaround. It does not change the default CIDR in MCO.

  • New procedure on Gathering data about your cluster: --network host / --network none, delete leftover podman0 / cni-podman0, optional MachineConfig drop-in for default_subnet.
  • Short warnings on RHCOS features, Agent installer networking, toolbox, and oc debug host access.

Test plan

  • Preview Gathering data about your cluster and check the new "Running Podman on a cluster node" section after toolbox.
  • Preview RHCOS key features: IMPORTANT under container tools.
  • Preview Agent-based installer networking: extra sentence on the 10.88 note.
  • Preview command-line host access: IMPORTANT after chroot /host.

Related: https://redhat.atlassian.net/browse/RFE-9862, https://redhat.atlassian.net/browse/OCPBUGS-9296, https://redhat.atlassian.net/browse/RHEL-34282, https://access.redhat.com/solutions/6961655, podman-container-tools/podman#17847

A plain podman run on a node creates 10.88.0.0/16 and can black-hole
production traffic. Spell out --network host, leftover bridge cleanup,
and a MachineConfig drop-in so we do not change the MCO default.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 11, 2026
@openshift-ci-robot

openshift-ci-robot commented Sep 11, 2026

Copy link
Copy Markdown

@DeokarT: This pull request references RFE-9862 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature request to target the "5.1.0" version, but no target version was set.

Details

In response to this:

RFE-9862. Same collision as OCPBUGS-9296: oc debug plus a plain podman run brings up 10.88.0.0/16, and that route can stay after the container is gone.

This PR only documents the workaround. It does not change the default CIDR in MCO.

  • New procedure on Gathering data about your cluster: --network host / --network none, delete leftover podman0 / cni-podman0, optional MachineConfig drop-in for default_subnet.
  • Short warnings on RHCOS features, Agent installer networking, toolbox, and oc debug host access.

Test plan

  • Preview Gathering data about your cluster and check the new "Running Podman on a cluster node" section after toolbox.
  • Preview RHCOS key features: IMPORTANT under container tools.
  • Preview Agent-based installer networking: extra sentence on the 10.88 note.
  • Preview command-line host access: IMPORTANT after chroot /host.

Related: https://redhat.atlassian.net/browse/RFE-9862, https://redhat.atlassian.net/browse/OCPBUGS-9296, https://redhat.atlassian.net/browse/RHEL-34282, https://access.redhat.com/solutions/6961655, podman-container-tools/podman#17847

Made with Cursor

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.

@openshift-ci openshift-ci Bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 11, 2026
@openshift-ci

openshift-ci Bot commented Sep 11, 2026

Copy link
Copy Markdown

Hi @DeokarT. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

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

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants