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

Changing ASB configuration should not be a requirement #17

Open
l0rd opened this issue Jul 17, 2018 · 1 comment
Open

Changing ASB configuration should not be a requirement #17

l0rd opened this issue Jul 17, 2018 · 1 comment

Comments

@l0rd
Copy link
Collaborator

l0rd commented Jul 17, 2018

Currently a manual step at cluster scope is required in order to have Che provisioned correctly: Ansible Service Broker should be configured with openshift sandbox_role set to admin.

This makes Che installation harder and impossible in some cases.

To get rid of this manual step we could have OpenShift teams to default sandbox_role to admin. This is what this issue is about openshift/openshift-ansible#9231

If this won't work we should look at

  1. why we need a RoleBinding with role_ref_kind: ClusterRole instead of role_ref_kind: Role and
  2. if sandbox_role set to edit would be enough to create a RoleBindings with role_ref_kind: Role
@l0rd
Copy link
Collaborator Author

l0rd commented Jul 30, 2018

After the discussions on openshift/openshift-ansible#9231 we can conclude that we cannot get rid of a manual step when installing Che using the ansible service broker.

But rather than asking users to change the configuration of the ASB as indicated today in the README (that has an effect on the whole cluster) we should rather ask users to manually create the ServiceAccount and RoleBinding. That is something that can be done before or after the provisioning of the APB if we set ignore_errors: yes for the RoleBinding creation step.

Summarizing this issue subtasks are:

@l0rd l0rd changed the title Get rid of ASB configuration step Changing ASB configuration should not be a requirement anymore Jul 30, 2018
@l0rd l0rd changed the title Changing ASB configuration should not be a requirement anymore Changing ASB configuration should not be a requirement Jul 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant