OCPBUGS-52340: Ensure that PSA label use k8s version supported on the project by camilamacedo86 · Pull Request #592 · operator-framework/operator-marketplace

camilamacedo86 · 2025-02-28T17:00:26Z

Description of the change:
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.

openshift-ci-robot · 2025-02-28T17:00:32Z

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

expected the bug to target the "4.19.0" version, but no target version was set

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:

Description of the change:

Motivation for the change:

Reviewer Checklist

Implementation matches the proposed design, or proposal is updated to match implementation

Sufficient unit test coverage

Sufficient end-to-end test coverage

Docs updated or added to /docs

Commit messages sensible and descriptive

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 · 2025-02-28T17:00:37Z

[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 perdasilva 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:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

camilamacedo86 · 2025-02-28T17:27:23Z

I will need to create an OCPBUG for each version :-(
I also pushed the check: openshift/release#62239
But we can only merge that after cherry-picking it up to the OCP release 4.16.

@tmshort

openshift-ci-robot · 2025-02-28T18:11:00Z

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

Description of the change:
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.

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.

camilamacedo86 · 2025-03-01T07:04:20Z

/test e2e-gcp-operator

camilamacedo86 · 2025-03-01T07:05:22Z

/test okd-scos-e2e-aws-ovn

camilamacedo86 · 2025-03-01T17:37:19Z

/test okd-scos-e2e-aws-ovn

camilamacedo86 · 2025-03-01T19:55:25Z

/test okd-scos-e2e-aws-ovn

camilamacedo86 · 2025-03-03T15:56:04Z

/test e2e-gcp-console-olm

camilamacedo86 · 2025-03-03T17:47:34Z

/test e2e-gcp-console-olm

camilamacedo86 · 2025-03-03T19:31:35Z

/test e2e-gcp-console-olm

camilamacedo86 · 2025-03-03T23:54:46Z

/test e2e-gcp-console-olm

camilamacedo86 · 2025-03-04T01:55:29Z

/test e2e-gcp-console-olm

The error faced has no relation with the change :-(

camilamacedo86 · 2025-03-04T08:33:01Z

/test e2e-gcp-console-olm

jianzhangbjz · 2025-03-04T09:08:46Z

Test pass, details: https://issues.redhat.com/browse/OCPBUGS-42526
/label qe-approved

camilamacedo86 · 2025-03-04T18:13:19Z

/test e2e-gcp-console-olm

camilamacedo86 · 2025-03-05T08:27:51Z

/test e2e-gcp-console-olm

openshift-ci-robot · 2025-03-05T08:36:10Z

@camilamacedo86: This pull request references Jira Issue OCPBUGS-52340, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.19.0) matches configured target version for branch (4.19.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

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

Details

In response to this:

Description of the change:
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.

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 · 2025-03-05T10:14:14Z

@camilamacedo86: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-console-olm	`28c530f`	link	true	`/test e2e-gcp-console-olm`

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.

jianzhangbjz · 2025-03-06T02:06:21Z

Based on https://redhat-internal.slack.com/archives/C06KP34REFJ/p1741224828143489?thread_ts=1739880491.760029&cid=C06KP34REFJ, we should use the latest instead of the pinned version.

jianzhangbjz · 2025-03-06T02:07:33Z

/hold

jianzhangbjz · 2025-03-06T02:11:25Z

/remove-label qe-approved

openshift-ci-robot · 2025-03-06T02:11:31Z

@camilamacedo86: This pull request references Jira Issue OCPBUGS-52340, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.19.0) matches configured target version for branch (4.19.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

In response to this:

Description of the change:
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.

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.

camilamacedo86 · 2025-03-06T09:30:54Z

Closing since QE would like to set latest instead

openshift-ci-robot · 2025-03-06T09:31:02Z

@camilamacedo86: This pull request references Jira Issue OCPBUGS-52340. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

Details

In response to this:

Description of the change:
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.

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.

jianzhangbjz · 2025-03-07T01:08:43Z

This PR was replaced by #600

openshift-ci Bot requested review from kevinrizza and rashmigottipati February 28, 2025 17:00

camilamacedo86 force-pushed the fix-psa-label branch from 73ce02b to 4bc88b8 Compare February 28, 2025 17:14

camilamacedo86 force-pushed the fix-psa-label branch from 4bc88b8 to 6068e79 Compare February 28, 2025 17:28

camilamacedo86 changed the title ~~OCPBUGS-42526: (fix): Ensure that PSA label use k8s version supported on the project~~ (fix): Ensure that PSA label use k8s version supported on the project (OCPBUGS-42526) Feb 28, 2025

openshift-ci-robot removed 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. labels Feb 28, 2025

openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Feb 28, 2025

camilamacedo86 force-pushed the fix-psa-label branch from 6068e79 to dbc31f0 Compare March 3, 2025 13:34

(fix): Ensure that PSA label use k8s version supported on the project

28c530f

camilamacedo86 force-pushed the fix-psa-label branch from dbc31f0 to 28c530f Compare March 3, 2025 13:35

openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Mar 4, 2025

camilamacedo86 changed the title ~~(fix): Ensure that PSA label use k8s version supported on the project (OCPBUGS-42526)~~ OCPBUGS-52340: Ensure that PSA label use k8s version supported on the project Mar 5, 2025

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. labels Mar 5, 2025

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 5, 2025

openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 6, 2025

openshift-ci Bot removed the qe-approved Signifies that QE has signed off on this PR label Mar 6, 2025

camilamacedo86 closed this Mar 6, 2025

openshift-ci-robot mentioned this pull request Mar 14, 2025

OCPBUGS-42526: Ensure that PSA label is latest instead of pinning versions openshift/operator-framework-olm#972

Merged

Conversation

camilamacedo86 commented Feb 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Feb 28, 2025

Uh oh!

openshift-ci Bot commented Feb 28, 2025

Uh oh!

camilamacedo86 commented Feb 28, 2025

Uh oh!

openshift-ci-robot commented Feb 28, 2025

Uh oh!

camilamacedo86 commented Mar 1, 2025

Uh oh!

camilamacedo86 commented Mar 1, 2025

Uh oh!

camilamacedo86 commented Mar 1, 2025

Uh oh!

camilamacedo86 commented Mar 1, 2025

Uh oh!

camilamacedo86 commented Mar 3, 2025

Uh oh!

camilamacedo86 commented Mar 3, 2025

Uh oh!

camilamacedo86 commented Mar 3, 2025

Uh oh!

camilamacedo86 commented Mar 3, 2025

Uh oh!

camilamacedo86 commented Mar 4, 2025

Uh oh!

camilamacedo86 commented Mar 4, 2025

Uh oh!

jianzhangbjz commented Mar 4, 2025

Uh oh!

camilamacedo86 commented Mar 4, 2025

Uh oh!

camilamacedo86 commented Mar 5, 2025

Uh oh!

openshift-ci-robot commented Mar 5, 2025

Uh oh!

openshift-ci Bot commented Mar 5, 2025

Uh oh!

jianzhangbjz commented Mar 6, 2025

Uh oh!

jianzhangbjz commented Mar 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jianzhangbjz commented Mar 6, 2025

Uh oh!

openshift-ci-robot commented Mar 6, 2025

Uh oh!

camilamacedo86 commented Mar 6, 2025

Uh oh!

openshift-ci-robot commented Mar 6, 2025

Uh oh!

jianzhangbjz commented Mar 7, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

camilamacedo86 commented Feb 28, 2025 •

edited

Loading

jianzhangbjz commented Mar 6, 2025 •

edited

Loading