Document how to setup RBAC with Keystone Authentication

[dims]

From @dims on March 16, 2018 21:50

See note from Saverio on his blog post : https://cloudblog.switch.ch/2018/02/02/openstack-keystone-authentication-for-your-kubernetes-cluster/

I will be correctly authenticated by keystone that will verify my identity, but I will have no authorization to do anything:

Copied from original issue: dims/openstack-cloud-controller-manager#87

[dims]

cc @zioproto

[dims]

cc @Fedosin

[dims]

From @zioproto on March 19, 2018 9:17

How can I assign this to me ? I will propose a PR for the documentation.

[dims]

We need to test/try what we have in https://github.com/kubernetes/cloud-provider-openstack/tree/master/cluster/addons/rbac

[zioproto]

/assign zioproto

[zioproto]

@dims I tested https://github.com/kubernetes/cloud-provider-openstack/tree/master/cluster/addons/rbac. It works for me.

I deploy both files with my ansible playbook:
https://github.com/zioproto/k8s-on-openstack/tree/cloud-provider-openstack/roles/k8s-rbac/files

I am able to run a simple nginx deployment with a few pods.

I still have to test persistent volumes and LBaaS.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.