feat(core/containerd): refactor containerd interaction to v2 APIs #1906
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daemon1024
force-pushed
the
containerd-revamp
branch
from
fa43bf6 to
686a68c
Compare
rksharma95
force-pushed
the
containerd-revamp
branch
3 times, most recently
from
c588c14 to
73aefe6
Compare
|
snyk failure couldn't be handled completely, as one of the failure is due to a medium severity vulnerability is Introduced through: |
* Move from v1 to v2 APIs * Use Event Driven Approach * Watch for tasks instead of container events, this will prevent mismanagement of events and policies on KubeArmor end incase of reuse of PIDNS/MNTNS by contaienr runtime, since we delete container information as soon as the root task exits Signed-off-by: daemon1024 <[email protected]>
Signed-off-by: rksharma95 <[email protected]>
daemon1024
force-pushed
the
containerd-revamp
branch
from
73aefe6 to
3cb740c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of PR?:
Fixes #1674
Does this PR introduce a breaking change?
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>