-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
5
-
False
-
False
-
OCPSTRAT-201 - Enable sharing ConfigMaps and Secrets across namespaces [GA]
-
Sprint 220, Sprint 221, Sprint 222, Sprint 223, Sprint 224, Sprint 225, Sprint 226, Sprint 227, Sprint 228, Sprint 229, Sprint 230, Build + Jenkins Sprint 231, Build + Jenkins Sprint 232
User Story
As a user of an OpenShift Cluster i should be restricted from creating Shared Secrets and ConfigMaps with the "openshift-" prefix unless my access level is cluster-admin 
or above
Acceptance Criteria
- Non-cluster admins should NOT be able to create Shared Secrets and ConfigMaps with prefix that is "openshift-"
- Cluster admins should be able to create Shared Secrets and ConfigMaps with the "openshift-" prefix.
- Integration testing to verify behavior
QE Impact
- Behavior will need to be verified
Docs Impact
- Docs will need to reflect this new behavior
PX Impact
- None
Notes
- Creating namespaces with the "openshift-" prefix is already restricted. That code could be used as a precedent for this.
- is blocked by
-
-
- Closed
-
- is documented by
-
RHDEVDOCS-4304 Docs: Reserved Name Prefix for SharedSecret/SharedConfigMaps
-
- Closed
-
- links to
(12 links to)
1.
|
QE: Reserved Name Prefix for SharedSecret/SharedConfigMap |
|
Closed | 
|
Jitendar Singh |
2.
|
Docs: Reserved Name Prefix for SharedSecret/ConfigMap |
|
Closed |
|
Unassigned |