-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APP.4.4.A6 #32
Comments
rules:
- no init scripts for permanently running containers
- init containers where initialisation is needed
- init containers are completed there doesn't seem to be anything existing in rules, we have to write them |
For me, this feels like a mix of Kubernetes built-in functionality (init containers) and organizational requirements.
Organizational requirement for app developer / manifest owner: Do not put init scripts into the main container but in an init container
I do not understand this requirement in the container context. In the context of a deployment / multiple pods, initialization might also be performed when other pods of the application are still running (e.g. init version 6 during rolling upgrade, while version 5 is still running). In the context of a single Pod, init containers are inherently run at first by Kubernetes.
This is a standard Kubernetes behaviour, isn't it? |
Feedback is required @sluetze @ermeratos: For me this is an org-only requirement, or at maximum a manual rule. What's your opionion? |
I agree, its a mixture of inherently met and organizational rule. |
Upstream PR merged |
No description provided.
The text was updated successfully, but these errors were encountered: