Title: [Workload] Microservices test: specialized_init_system
Description of problem
There are proper init systems and sophisticated supervisors that can be run inside of a container. Both of these systems properly reap and pass signals. Sophisticated supervisors are considered overkill because they take up too many resources and are sometimes too complicated. Some examples of sophisticated supervisors are: supervisord, monit, and runit. Proper init systems are smaller than sophisticated supervisors and therefore suitable for containers. Some of the proper container init systems are tini, dumb-init, and s6-overlay.
Description of solution
The test should fails if PID 1 is supervisord, monit, or runit, and passes if PID 1 is tini, dumb-init, or s6-overlay
The test should fail if PID 1 is anything else.
https://cloud.google.com/architecture/best-practices-for-building-containers
Acceptance Criteria:
Microservice Test: Microservices test: specialized_init_system
EPIC: CNF Conformance Test Suite
Release: vN.N.N
Test Category: Configuration
Type of test (static or runtime) = ?
Environment set up tasks:
Upstream tool set up tasks: (conformance suite + upstream tools)
CNF setup Tasks
Sample CNF tasks:
Code implementation tasks:
Documentation tasks:
QA tasks
Dev Review:
Peer review:
Reference:
Tools: