Skip to content
This repository was archived by the owner on Jan 29, 2026. It is now read-only.

Assign default edit role to lcm to support kubernetes 1.9 and above#22

Merged
animeshsingh merged 2 commits intoIBM:masterfrom
Tomcli:lcm-rbac
Feb 22, 2018
Merged

Assign default edit role to lcm to support kubernetes 1.9 and above#22
animeshsingh merged 2 commits intoIBM:masterfrom
Tomcli:lcm-rbac

Conversation

@Tomcli
Copy link
Contributor

@Tomcli Tomcli commented Feb 21, 2018

From Kubernetes 1.9 and above, the default service account is not allow to view and consume cluster resources. Thus, we will assign the default edit role to LCM, so LCM can view and distribute resources to the corresponding learners.

This PR also fixes #21

@Tomcli Tomcli added the enhancement New feature or request label Feb 21, 2018
Copy link
Contributor

@animeshsingh animeshsingh left a comment

Choose a reason for hiding this comment

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

Have these changed been tested on prior version as well? Also how did values.yaml work before when it was using test namespace, since everything is deployed currently in default?

@Tomcli
Copy link
Contributor Author

Tomcli commented Feb 22, 2018

I use the latest RBAC API which only available for 1.8 and above, and I tested on both 1.8 and 1.9. I added a new option for users who are using 1.7 or below to disable the RBAC on LCM.

Regrading to the namespace in values.yaml, it wasn't used on the helm template before. Thus everything is deployed to default namespace.

@animeshsingh animeshsingh merged commit 8581fec into IBM:master Feb 22, 2018
@Tomcli Tomcli deleted the lcm-rbac branch March 20, 2018 19:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add new RBAC for LCM to support Kubernetes 1.9 and above

2 participants