-
Notifications
You must be signed in to change notification settings - Fork 127
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
move install-cni.sh to an initContainer #251
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this PR improves the code base, and I agree we should be using the K8s primitives to get required stuff installed in the nodes.
... having said that, once we have this in an init container, it doesn't make sense to have that ugly bash script a long lived process. I think you should remove the SLEEP
option from it, and just make it a one-shot script.
Thanks for spotting this and for following through with a PR.
happy to add that to this PR
…On Mon, Jul 18, 2022, 04:38 Miguel Duarte Barroso ***@***.***> wrote:
***@***.**** requested changes on this pull request.
I think this PR improves the code base, and I agree we should be using the
K8s primitives to get required stuff installed in the nodes.
... having said that, once we have this in an init container, it doesn't
make sense to have that ugly bash script a long lived process. I think you
should remove the SLEEP option from it, and just make it a one-shot
script.
Thanks for spotting this and for following through with a PR.
—
Reply to this email directly, view it on GitHub
<#251 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA36GX3FXNMIJDP3LT2JJR3VUU645ANCNFSM532NIHCA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Let see what the other maintainers think of this ...
- quote all the things - remove some bits that aren't POSIX but busybox sh supports, to make shellcheck happy - make chown modes absolute
e2e CI failed, I'll look into it
https://github.com/k8snetworkplumbingwg/whereabouts/runs/7391864197?check_suite_focus=true
…--
regards,
DQ
On Mon, Jul 18, 2022, 07:46 Miguel Duarte Barroso ***@***.***> wrote:
***@***.**** approved this pull request.
Thanks.
Let see what the other maintainers think of this ...
—
Reply to this email directly, view it on GitHub
<#251 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA36GXZJ2LBMNTF3NTDSX6DVUVU4XANCNFSM532NIHCA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Where do we stand with this PR? I was about to submit something similar, but this one seems stuck |
@deekue mind rebasing this PR so we see how this behaves in regard to the e2e tests ? |
What this PR does / why we need it:
install-cni.sh
to an initContainer. separation of concernsip-control-loop
directly. daemon receives signals from k8s for graceful shutdown etc