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

remove over privileged rbac from cnao manifest #413

Merged
merged 1 commit into from Jun 2, 2020

Conversation

RamLavi
Copy link
Collaborator

@RamLavi RamLavi commented Jun 2, 2020

Signed-off-by: Ram Lavi ralavi@redhat.com

What this PR does / why we need it:
Currently the cnao rbac Policy has a segment that elevates the container privileges to all resources, and all verbs.
This is too much for the cnao's needs, and also in turn changes scc to anyuid in cnv/okd clusters.
Hence, the rbac segment is removed in this commit.

Special notes for your reviewer:

Release note:

NONE

@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/S labels Jun 2, 2020
@RamLavi RamLavi force-pushed the remove_over_previliged_rbac branch from e06522a to 010ea01 Compare June 2, 2020 08:56
@RamLavi
Copy link
Collaborator Author

RamLavi commented Jun 2, 2020

/retest

prow hiccup

@RamLavi
Copy link
Collaborator Author

RamLavi commented Jun 2, 2020

/retest

Copy link
Member

@phoracek phoracek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems legit. Thanks.

Please add proper commit message.

Currently the cnao rbac Policy has a segment that elevates the container privileges to all resources, and all verbs.
This is too much for the cnao's needs, and also in turn changes scc to anyuid in cnv/okd clusters.
Hence, the rbac segment is removed in this commit.

Signed-off-by: Ram Lavi <ralavi@redhat.com>
@RamLavi RamLavi force-pushed the remove_over_previliged_rbac branch from 010ea01 to 19291e6 Compare June 2, 2020 12:20
@RamLavi RamLavi changed the title WIP remove over privileged rbac from cnao manifest remove over privileged rbac from cnao manifest Jun 2, 2020
@kubevirt-bot kubevirt-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 2, 2020
Copy link
Member

@phoracek phoracek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2020
@kubevirt-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: phoracek

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 2, 2020
@kubevirt-bot kubevirt-bot merged commit 1ce8c55 into kubevirt:master Jun 2, 2020
@phoracek
Copy link
Member

phoracek commented Jun 4, 2020

This change prevents us from deploying anything on OpenShift. Reverting.

phoracek added a commit that referenced this pull request Jun 4, 2020
phoracek added a commit that referenced this pull request Jun 4, 2020
This reverts commit 1ce8c55.

We have to rework this and allow CNAO to edit more resources. By
dropping of the global role, we blocked us from creating anything on
OpenShift.

Signed-off-by: Petr Horacek <phoracek@redhat.com>
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants