Conversation
|
/test all |
|
Weren't these so users can use pre-made roles to edit operator resources? |
|
I think this is a leftover from the old generation pattern. We have role already. these are not updated anymore |
|
That is the role for the operator service account; I think those were meant for end users. But tbh it doesn't really matter, end users can just make their own roles with access to the operator APIs if they need it. |
|
Just to be safe add a release note. Don't think anyone used those manifests but in case someone did they'll have an easier time finding what happened to them. |
|
/release-note-edit |
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: 8b8f8c7985f29abe3e02d0a89c3129092a3231b1 |
|
I think this was a concept mostly carried over from Kubermatic side, so yeah, I can see us removing it. /approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ntnn, xrstf The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary
I dont think we use these anymore?
What Type of PR Is This?
/kind cleanup
Related Issue(s)
Fixes #
Release Notes