-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Update CRI-API Capabilities to include a field that allows us to set … #104620
Conversation
/ok-to-test |
/cc @tallclair |
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.
This looks good to me, but you'll need signoff from sig-node
2f126de
to
e3128b9
Compare
/lgtm |
/assign @mrunalp |
message Capability { | ||
// List of capabilities to add. | ||
repeated string add_capabilities = 1; | ||
// List of capabilities to drop. | ||
repeated string drop_capabilities = 2; | ||
// List of ambient capabilities to add. | ||
repeated string add_ambient_capabilities = 3; |
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.
do we have to keep updating the v1alpha2
? Do we expect this to be implemented on Containerd 1.5, for example?
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 only expect this feature to be implemented in the latest version of containerd. I believe that would be 1.5.x wouldn't it? Sorry I am not very familiar with how CRI-API versions translate to containerd verisons.
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.
containerd 1.6 is about to be released. it supports CRI v1
, which means there is no need to fall back to v1alpha2
.
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.
Ack. I'll remove the v1alpha2 changes. Thanks!
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.
Done! PTAL. Thanks for all your help!
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.
@SergeyKanzhelev - looks like removing the changes from v1alpha2 causes TestV1alpha2ContainerConfig
test to fail. I think we will need to make the changes in v1 and v1alpha2. WDYT?
This raises an interesting question. On one hand, there is no reason and it confusing to update Specifically for this PR, I think keeping versions in sync is better. sorry that you need to re-revet it back. I didn't realize this when was commenting above |
…ambient capabilities.
Thanks added the v1alpha2 changes back! |
/test pull-kubernetes-unit |
/test pull-kubernetes-e2e-kind-ipv6 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mrunalp, qiutongs, vinayakankugoyal The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-kubernetes-e2e-kind-ipv6 |
/retest |
/retest-required |
…ambient capabilities.
What type of PR is this?
/kind feature
What this PR does / why we need it:
It adds a field to the Capabilities message that allows us to add ambient capabilities to a container. CRI-O and containerd will need to be updated to respect the existence of this field and configure the container accordingly.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
go files generated using
hack/update-generated-runtime.sh
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: