-
Epic
-
Resolution: Done
-
High
-
None
-
None
-
No root (superuser) access to database from application container
-
Non-Functional Requirement (DEPRECATED)
-
2
-
Not yet performed
-
Reduced Scope
-
M
-
GO
-
Green
-
GO
-
Yellow
-
GO
-
Yellow
-
GO
Description of Use Case / Requirement:
ONAP application container should not access database using root account and should not ask for escalation (sudo). If application requires root access to bootstrap the database an init container or separate kubernetes job should be used.
Owners (one of these should be the Assignee - use @ notation): kopasiak sdesbure
Link to HLD/LLD (if any):
Dependency Relationships with Other Projects:
Project Impact (Test Only (TO), Code (C)): C
Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):
Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.
Integration Leads (use @ notation):
Company Engagement: Samsung, Orange
- clones
-
REQ-1
ONAP Requirement Template
-
- To Do
-
-
REQ-537
Long-term IPv4/IPv6 dual stack networking support
-
- Done
-
- relates to
-
SO-3044
No root (superuser) access to database from application container
-
- Open
-
-
OPTFRA-800 REQ-358 No root access to database from application container
-
- Closed
-
-
DCAEGEN2-2329
REQ-358 No root (superuser) access to database from application container
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-