Skip to content

Conversation

@lgarciaaco
Copy link
Contributor

Summary

Convert 3 images from network_mode: open to hermetic mode by removing konflux network_mode configuration, allowing them to use the default hermetic build isolation.

Problem

Before: Three images (openshift-enterprise-hyperkube, ose-insights-runtime-extractor, and openstack-resource-controller) were configured with network_mode: open in their konflux section, allowing network access during builds.
After: Images now use the default hermetic mode, providing build isolation and improved security by preventing network access during container builds.

Changes

  • images/openshift-enterprise-hyperkube.yml - Removed network_mode: open, added basic cachi2 lockfile config
  • images/ose-insights-runtime-extractor.yml - Removed network_mode: open, updated RPM lockfile with proper package list
  • images/openstack-resource-controller.yml - Completely removed konflux section with network_mode: open

Technical Notes
This change enables build isolation for these components, improving security posture and aligning with the project's goal of converting all images to hermetic builds.

Backport from openshift-4.21 to openshift-4.20.

Remove network_mode: open configuration from konflux section to allow
default hermetic mode for openshift-enterprise-hyperkube,
ose-insights-runtime-extractor, and openstack-resource-controller.

This change enables build isolation and improves security by preventing
network access during container builds for these components.

Backport from openshift-4.21 to openshift-4.20.
@lgarciaaco
Copy link
Contributor Author

@lgarciaaco
Copy link
Contributor Author

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lgarciaaco

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 25, 2025
@lgarciaaco
Copy link
Contributor Author

/hold waiting for a good moment after RC to merge

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 25, 2025
@joepvd
Copy link
Contributor

joepvd commented Oct 6, 2025

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 6, 2025
@joepvd
Copy link
Contributor

joepvd commented Oct 6, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 6, 2025
@joepvd
Copy link
Contributor

joepvd commented Oct 6, 2025

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit 91b8180 into openshift-eng:openshift-4.20 Oct 6, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants