Red Hat Bugzilla – Bug 1472251
project admin should be able to create / get / delete podpreset
Last modified: 2017-10-17 16:44:48 EDT
Description of problem:
project admin cannot create / get / delete podpreset
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. # oc create -f podpreset.yaml
Error from server (Forbidden): error when creating "podpreset.yaml": User "wmeng" cannot create podpresets.settings.k8s.io in project "wmeng"
podpreset "allow-database" created
isn't this something the installer should be setting up in this release?
and actually, https://github.com/openshift/openshift-ansible/pull/4765/files#diff-d66acb2fb119175c74e61c714e6bf52eR15 should have resolved it
(In reply to Jordan Liggitt from comment #2)
> and actually,
> d66acb2fb119175c74e61c714e6bf52eR15 should have resolved it
This can take effect only when enable service-catalog, but sometime we only need podpreset. Though service-catalog use podpreset, but they should separate.
We actually do not want to enable pod preset unless the catalog is enabled at this time.
I'm moving this to 3.7.0 because it's arguable that this should be done at that time. In 3.6 you should only get PodPreset if you install the catalog.
We're actually going to be removing PodPreset entirely in openshift 3.7, so this is NOTABUG