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

✨ grant rbac access to experimental infra api group #2959

Merged
merged 1 commit into from
Apr 27, 2020

Conversation

devigned
Copy link
Contributor

What this PR does / why we need it:
This grants CAPI access to exp.infrastructure.cluster.x-k8s.io api group. The exp.infrastructure.cluster.x-k8s.io api group corresponds to experimental features in the infrastructure provider and was patterned after exp.cluster.x-k8s.io. This will be useful for supporting MachinePool and other experimental implementations in infra providers.

Related:

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Apr 24, 2020
@devigned devigned changed the title ✨ feat: grant rbac access to experimental infrastructure api group ✨ grant rbac access to experimental infrastructure api group Apr 24, 2020
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Apr 24, 2020
@devigned devigned changed the title ✨ grant rbac access to experimental infrastructure api group feat: grant rbac access to experimental infrastructure api group Apr 24, 2020
@devigned devigned changed the title feat: grant rbac access to experimental infrastructure api group ✨ grant rbac access to experimental infrastructure api group Apr 24, 2020
@devigned devigned changed the title ✨ grant rbac access to experimental infrastructure api group ✨ grant rbac access to experimental infra api group Apr 24, 2020
@@ -28,6 +28,20 @@ rules:
- patch
- update
- watch
- apiGroups:
- bootstrap.cluster.x-k8s.io
- exp.infrastructure.cluster.x-k8s.io
Copy link
Contributor

Choose a reason for hiding this comment

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

should this be added to the apiGroups above instead?

Copy link
Member

Choose a reason for hiding this comment

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

These should be automatically generated

Copy link
Contributor

Choose a reason for hiding this comment

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

why are bootstrap.cluster.x-k8s.io and infrastructure.cluster.x-k8s.io duplicated then?

Copy link
Member

Choose a reason for hiding this comment

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

I haven't looked at the controller-tools in a while, but IIRC it's because there is two different kubebuilder directives which the code can't dedupe

Copy link
Member

Choose a reason for hiding this comment

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

not allowing all resources for the experimental group can be an extra gate when / if needed. LGTM as per the existing exp.cluster.x-k8s.io.

also this ClusterRole file seems quite messy, indeed.

Copy link
Contributor

@CecileRobertMichon CecileRobertMichon left a comment

Choose a reason for hiding this comment

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

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 24, 2020
Copy link
Member

@vincepri vincepri left a comment

Choose a reason for hiding this comment

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

/approve
/milestone v0.3.4

@k8s-ci-robot k8s-ci-robot added this to the v0.3.4 milestone Apr 27, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: devigned, vincepri

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 27, 2020
@k8s-ci-robot k8s-ci-robot merged commit c9796ac into kubernetes-sigs:master Apr 27, 2020
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants