magnum/magnum
Feilong Wang d8df9d0c36 [fedora-atomic][k8s] Support default Keystone auth policy file
With the new config option `keystone_auth_default_policy`, cloud admin
can set a default keystone auth policy for k8s cluster when the
keystone auth is enabled. As a result, user can use their current
keystone user to access k8s cluster as long as they're assigned
correct roles, and they will get the pre-defined permissions
set by the cloud provider.

The default policy now is based on the v2 format recently introduced
in k8s-keystone-auth which is getting more useful now. For example,
in v1 it doesn't support a policy for user to access resources from
all namespaces but kube-system, but v2 can do that.

NOTE: Now we're using openstackmagnum dockerhub repo until CPO
team fixing their image release issue.

Task: 30069
Story: 1755770

Change-Id: I2425e957bd99edc92482b6f11ca0b1f91fe59ff6
2019-06-11 11:57:15 +12:00
..
api [k8s][fedora atomic] Rolling upgrade support 2019-06-07 14:48:08 +12:00
cmd Add framework for magnum-status upgrade check 2019-01-27 04:26:30 +00:00
common Add cluster upgrade to the API 2019-06-07 12:01:10 +12:00
conductor Add cluster upgrade to the API 2019-06-07 12:01:10 +12:00
conf [fedora-atomic][k8s] Support default Keystone auth policy file 2019-06-11 11:57:15 +12:00
db ng-4: Adapt cluster object 2019-03-29 10:31:48 +00:00
drivers [fedora-atomic][k8s] Support default Keystone auth policy file 2019-06-11 11:57:15 +12:00
hacking Fix typo in magnum/hacking/checks.py for consistency 2017-06-16 15:43:27 +08:00
objects ng-4: Adapt cluster object 2019-03-29 10:31:48 +00:00
service ng-2: Adapt existing cluster APIs and conductor 2019-03-28 10:31:01 +00:00
servicegroup Trivial code cleanups 2018-10-02 19:41:34 +00:00
tests [fedora-atomic][k8s] Support default Keystone auth policy file 2019-06-11 11:57:15 +12:00
__init__.py Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
i18n.py Remove log translations 2017-03-30 17:05:10 +08:00
version.py Remove coding:utf-8 2015-08-03 23:28:22 +08:00