-
Notifications
You must be signed in to change notification settings - Fork 115
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
Use default {ib-}sriov-cni
entrypoint script
#581
Use default {ib-}sriov-cni
entrypoint script
#581
Conversation
Thanks for your PR,
To skip the vendors CIs use one of:
|
Pull Request Test Coverage Report for Build 7974655862Details
💛 - Coveralls |
LGTM |
volumeMounts: | ||
- name: cnibin | ||
mountPath: /host/opt/cni/bin | ||
- name: os-release |
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.
who is using this mount ? sriov cni entrypoint does not use it AFAIK
volumeMounts: | ||
- name: cnibin | ||
mountPath: /host/opt/cni/bin | ||
- name: os-release |
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.
same Q as above :)
we could extend sriov-cni and ib-sriov-cni with a |
I like that! Going to file a PR in sriov-cni and ib-sriov-cni. Regarding the This logic is also present in other multus cni plugin: |
21fd429
to
63dedfa
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
63dedfa
to
a7012c8
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
a7012c8
to
0241f36
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
There's still a problem with |
/hold cancel related work on sriov-cni and ib-sriov-cni has been merged |
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.
nice work!
LGTM
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.
overall LGTM,
can you amend the commit msg.
i think this part is no longer true:
Move the copy logic back to the `containers:` section, as the image's
entrypoint script ends with a "sleep forever" [1].
we keep copy of cni bin in initContainer still, the cni image entrypoint now supports --no-sleep flag which allows it to function as init container.
Avoid overriding entrypoint script for sriov-cni and ib-sriov-cni. It is more robust to rely on the image logic, as the source image can change the path where the binary is stored. Mount `/etc/os-release` file to let the copy logic to make decision on which binary it should copy depending on the operating system. refs: [1] https://github.com/k8snetworkplumbingwg/sriov-cni/blob/07ecbf9b6ee867054df47423e51a800034ef4e05/images/entrypoint.sh#L63 Signed-off-by: Andrea Panattoni <[email protected]>
0241f36
to
0a74848
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
@zeeke feel free to remove the hold label and merge this one, thx for working on it ! |
Avoid overriding entrypoint script for sriov-cni and ib-sriov-cni. It is more robust to rely on the image logic, as the source image can change the path where the binary is stored.
Move the copy logic back to the
containers:
section, as the image's entrypoint script ends with a "sleep forever" [1].Mount
/etc/os-release
file to let the copy logic to make decision on which binary it should copy depending on the operating system.refs:
[1] https://github.com/k8snetworkplumbingwg/sriov-cni/blob/07ecbf9b6ee867054df47423e51a800034ef4e05/images/entrypoint.sh#L63
cc @SchSeba