Skip to content

OCPBUGS-52320: [release-4.17] The openshift-operator-lifecycle-manager still use old pod-security.kubernetes.io/*-version v1.24 and v1.25 respectively#970

Closed
camilamacedo86 wants to merge 2 commits intoopenshift:release-4.17from
camilamacedo86:fix-psa-olmv0-4-17
Closed

OCPBUGS-52320: [release-4.17] The openshift-operator-lifecycle-manager still use old pod-security.kubernetes.io/*-version v1.24 and v1.25 respectively#970
camilamacedo86 wants to merge 2 commits intoopenshift:release-4.17from
camilamacedo86:fix-psa-olmv0-4-17

Conversation

@camilamacedo86
Copy link
Copy Markdown
Contributor

@camilamacedo86 camilamacedo86 commented Mar 4, 2025

No description provided.

@camilamacedo86
fix: update PSA versions to match Kubernetes API version (#3524)
813eaf7 
In this commit, a new Makefile target `update-k8s-values` was created to automatically update the
`pod-security.kubernetes.io/*-version` values (`enforceVersion`, `auditVersion`, `warnVersion`)
in the Helm chart's `values.yaml` file.

These values now align with the Kubernetes API version defined in `go.mod`, instead of using `latest`. This ensures better compatibility and avoids issues with unsupported versions in Kubernetes PSA.

Upstream-repository: operator-lifecycle-manager
Upstream-commit: efe3a9ac2e3358cdcaff03accea1e2ce96cd0d3f
@camilamacedo86
Fix OCP PSA labels for OCP manifests with k8s version
c278948
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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 Mar 4, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 4, 2025

@camilamacedo86: This pull request references Jira Issue OCPBUGS-52320, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-52319 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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:

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 requested review from dinhxuanvu and tmshort March 4, 2025 20:38
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 4, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: camilamacedo86
Once this PR has been reviewed and has the lgtm label, please assign joelanford for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details 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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 5, 2025

@camilamacedo86: 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.

@camilamacedo86 camilamacedo86 changed the title OCPBUGS-52320: [release-4.17] OLMv0 is using PSA Labels version as latest instead of version pinned OCPBUGS-52320: [release-4.17] The openshift-operator-lifecycle-manager and openshift-marketplace namespaces still use old pod-security.kubernetes.io/*-version v1.24 and v1.25 respectively Mar 5, 2025
@camilamacedo86 camilamacedo86 changed the title OCPBUGS-52320: [release-4.17] The openshift-operator-lifecycle-manager and openshift-marketplace namespaces still use old pod-security.kubernetes.io/*-version v1.24 and v1.25 respectively OCPBUGS-52320: [release-4.17] The openshift-operator-lifecycle-manager still use old pod-security.kubernetes.io/*-version v1.24 and v1.25 respectively Mar 5, 2025
@camilamacedo86
Copy link
Copy Markdown
Contributor Author

camilamacedo86 commented Mar 6, 2025

Closing since QE would like to set latest instead

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 6, 2025

@camilamacedo86: This pull request references Jira Issue OCPBUGS-52320. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In 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.

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

Reviewers

@dinhxuanvu dinhxuanvu Awaiting requested review from dinhxuanvu

@tmshort tmshort Awaiting requested review from tmshort

Assignees

No one assigned

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@camilamacedo86 @openshift-ci-robot