[DOCS-13693] [MEKO] MANAGED_SECURITY_CONTEXT is not documented Created: 09/Jun/20  Updated: 29/Oct/23  Resolved: 25/Jun/20

Status: Closed
Project: Documentation
Component/s: Kubernetes Operator, MEKO
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Juan Crossley Assignee: John Williams
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCS-13732 Backport DOCS-13693 to v1.5 Backport Sub-Task Closed John Williams  
DOCS-13733 Backport DOCS-13693 to v1.4 Backport Sub-Task Closed John Williams  
Participants:
Days since reply: 3 years, 32 weeks, 6 days ago
Epic Link: DOCSP-3291
Story Points: 3

 Description   

Description

Hello,

Based on a recommendation from support we had to include the MANAGED_SECURITY_CONTEXT flag in our operator yaml to avoid issues with the restrictive environment of my customer, this flag allows to inherits the permission of the namespace defined in the security policies instead of creating its own definition, for some reason this is not documented in the last few versions, please consider including it in the section related to how to install the operator in openshift in case the policies does not allow specific users to run containers (like runAsUser: 2000 or fsGroup: 2000).

Thanks

Thanks,

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by John Williams [ 25/Jun/20 ]

Hi juan.crossley this issue has been fixed in the docs for 1.5 and 1.4. It might take an hour to two for the changes to be pushed out to the CDN. Please reach out if you require further updates.

Generated at Thu Feb 08 08:08:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.