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

OCPBUGS-47743: Update cluster-reader ClusterRole permissions #4823

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

isabella-janssen
Copy link
Member

@isabella-janssen isabella-janssen commented Jan 30, 2025

- What I did

  • Update the cluster-reader ClusterRole to have read-only permissions (get, list, and watch).

- How to verify it
Testing permission updates:

  1. Use this PR to launch a cluster.
  2. View the cluster-reader permissions in the Openshift UI by going to User ManagementRolescluster-reader

Testing that functionality remained unchanged:

- Description for the changelog
OCPBUGS-47743: Update cluster-reader ClusterRole permissions

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 30, 2025
Copy link
Contributor

openshift-ci bot commented Jan 30, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@isabella-janssen
Copy link
Member Author

/test all

Copy link
Contributor

openshift-ci bot commented Jan 30, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found 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

@isabella-janssen isabella-janssen changed the title ocpbugs-47743 OCPBUGS-47743: Update cluster-reader ClusterRole permissions Jan 30, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jan 30, 2025
@openshift-ci-robot
Copy link
Contributor

@isabella-janssen: This pull request references Jira Issue OCPBUGS-47743, 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)

Requesting review from QA contact:
/cc @sergiordlr

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

In response to this:

- What I did

  • Update the cluster-reader ClusterRole to have read-only permissions (get, list, and watch).

- How to verify it
Testing permission updates:

  1. Use this PR to launch a cluster.
  2. View the cluster-reader permissions in the Openshift UI by going to User ManagementRolescluster-reader

Testing that functionality remained unchanged:

  • Tests pass
  • The cluster-reader permissions for the machineconfignodes resource were originally updated in OCPBUGS-24416: Sync MCN with node creation and deletion #4062, so I tested that this permission change did not re-introduce the bug fixed in that PR.
  • This updates the permissions for the machineosconfigsand machineosbuilds resouces, so general OCL functionality was tested.

- Description for the changelog
OCPBUGS-47743: Update cluster-reader ClusterRole permissions

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-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 30, 2025
@openshift-ci openshift-ci bot requested a review from sergiordlr January 30, 2025 20:45
@isabella-janssen
Copy link
Member Author

/retest-required

@sergiordlr
Copy link

sergiordlr commented Feb 3, 2025

Critical mcoqe e2e test cases execution:
https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-aws-ipi-longduration-mco-critical-f9/1886349988066234368

Checked that no "delete" "update" or "patch" verbs are used in the cluster-reader clusterrole

$ oc get clusterrole cluster-reader  -oyaml  | grep delete
$ oc get clusterrole cluster-reader  -oyaml  | grep update
    rbac.authorization.kubernetes.io/autoupdate: "true"
$ oc get clusterrole cluster-reader  -oyaml  | grep patch

@openshift-ci-robot
Copy link
Contributor

@isabella-janssen: This pull request references Jira Issue OCPBUGS-47743, 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)

Requesting review from QA contact:
/cc @sergiordlr

In response to this:

- What I did

  • Update the cluster-reader ClusterRole to have read-only permissions (get, list, and watch).

- How to verify it
Testing permission updates:

  1. Use this PR to launch a cluster.
  2. View the cluster-reader permissions in the Openshift UI by going to User ManagementRolescluster-reader

Testing that functionality remained unchanged:

- Description for the changelog
OCPBUGS-47743: Update cluster-reader ClusterRole permissions

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.

@sergiordlr
Copy link

MCO critical test cases passed and the permissions in the clusterrole were fixed.

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 4, 2025
@isabella-janssen isabella-janssen marked this pull request as ready for review February 4, 2025 16:52
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 4, 2025
Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

@isabella-janssen: 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/okd-scos-e2e-aws-ovn 88813e2 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants