-
Notifications
You must be signed in to change notification settings - Fork 326
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
feat(kuma-cp): init container first by default #5857
Conversation
8213686
to
1848a4d
Compare
/golden_files |
As K8s by default doesn't guarantee anything about startup and order of containers I don't think it's useful to add an annotation to control this. I think the only place we'd add an annotation is for the 2nd part of this work (the one that adds a preStart hook) |
f35d8e5
to
142d4de
Compare
@lobkovilya or @lukidzi can we get a review/merge on this? |
Signed-off-by: Vincent Le Goff <vincent.legoff@konghq.com>
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
9c1d060
to
053f462
Compare
This reverts commit 6cf9648.
Follow up of #3121 to put the init container as first by default. I might be missing something; happy to work on this if there is other things needed.
Question is do we want to make this operation as an option? So do we create a pod annotation for this?
Checklist prior to review
syscall.Mkfifo
have equivalent implementation on the other OS --UPGRADE.md
? --> Changelog:
entry here or add aci/
label to run fewer/more tests?