Skip to content
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

Remove SeccompProfilePath #117045

Closed
SergeyKanzhelev opened this issue Mar 31, 2023 · 16 comments · Fixed by #117050
Closed

Remove SeccompProfilePath #117045

SergeyKanzhelev opened this issue Mar 31, 2023 · 16 comments · Fixed by #117050
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@SergeyKanzhelev
Copy link
Member

Look for "// TODO: Deprecated, remove after we switch to Seccomp field". Fix it. See #115898 as example.

/cc @saschagrunert

/help
/good-first-issue
/sig node

add @saschagrunert as a reviewer when sending a PR.

(issue is a follow up from https://github.com/kubernetes/kubernetes/pull/117020/files#r1154025906)

@k8s-ci-robot
Copy link
Contributor

@SergeyKanzhelev:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Look for "// TODO: Deprecated, remove after we switch to Seccomp field". Fix it. See #115898 as example.

/cc @saschagrunert

/help
/good-first-issue
/sig node

add @saschagrunert as a reviewer when sending a PR.

(issue is a follow up from https://github.com/kubernetes/kubernetes/pull/117020/files#r1154025906)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 31, 2023
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@charles-chenzz
Copy link
Member

I will start to look at it and fix part of them

/assign

@vamshi1188
Copy link

/assign

@AmeyDagaria007
Copy link

/assign

@pgaijin66
Copy link

/assign

@kaminn
Copy link

kaminn commented Apr 3, 2023

/assign

@tmrpavan
Copy link

tmrpavan commented Apr 9, 2023

I would like to work on this issue. Can you assign this to me?

/assign

tmrpavan added a commit to tmrpavan/kubernetes that referenced this issue Apr 9, 2023
Why are we solving this issue?
Look for "// TODO: Deprecated, remove after we switch to Seccomp field"

To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Look for "// TODO: Deprecated, remove after we switch to Seccomp field"

Does this issue have zero to low barrier of entry?
Yes
@vibovenkat123
Copy link

/assign

@ashutosh887
Copy link

Should I work on this Issue?
/assign

@sherifhmdy
Copy link

/assign

@shivam-m-7
Copy link

Should I work on this Issue?
/assign

@sherifhmdy sherifhmdy removed their assignment Apr 17, 2023
@sherifhmdy
Copy link

@shivam-m-7 I believe there is someone working on this now, and in approving phase, so it's kinda done.

@tmrpavan tmrpavan removed their assignment Apr 17, 2023
@Abhi-y2003
Copy link

Abhi-y2003 commented Apr 19, 2023

Hey, I would like to work on this.
/assign

@Aakash-chouksey
Copy link

i got it!!
/assign

@Amshu-k
Copy link

Amshu-k commented Apr 24, 2023

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet