Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.18] selinux: per-nodegroup SCC toggle #1153

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1124

/assign ffromani

consume upstream fixes

Signed-off-by: Francesco Romani <[email protected]>
incorporate the SCC v2 as provided by deployer <= 0.21.3

Signed-off-by: Francesco Romani <[email protected]>
there are cases on which object (aka cluster) level annotations
are not good enough, so add limited per-nodegroup annotation.

This is another strong hint we should have had an object per nodegroup
rather than a single object for all nodegroups.

Signed-off-by: Francesco Romani <[email protected]>
rename internal helpers for consistency.
no intended changes in behavior.

Signed-off-by: Francesco Romani <[email protected]>
Now that we have per-nodegroup annotation,
we can enable back the custom selinux policy
per-nodegroup (vs per-cluster), allowing granular upgrades.

Signed-off-by: Francesco Romani <[email protected]>
we prefer and we intend to have per-nodegroup configuration,
so drop per-object global annotation check and honor the custom-selinux
policy per-nodegroup, enabling more granularity.

This is meant to enable blue-green or anyhow partial upgrades.

Signed-off-by: Francesco Romani <[email protected]>
Ince a nodegroup has the legacy custom selinux policy annotation,
it should keep using it, so it should keep reconciling the MachineConfig
and ensure its present.
Once the annotation is removed, the MachineConfig should be deleted.
Add a testcase to ensure this behavior.

Signed-off-by: Francesco Romani <[email protected]>
@ffromani
Copy link
Member

/approve
/lgtm

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

openshift-ci bot commented Jan 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, openshift-cherrypick-robot

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 Jan 14, 2025
@ffromani ffromani added cherry-pick-candidate Possible cherry-pick in the future cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Jan 14, 2025
@ffromani ffromani merged commit 01c0073 into openshift-kni:release-4.18 Jan 14, 2025
15 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cherry-pick-candidate Possible cherry-pick in the future 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