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.

Sign up for GitHub

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

Jump to bottom

Add seccomp page for Node Reference Information #47687

Closed
saschagrunert opened this issue Aug 26, 2024 · 9 comments · Fixed by #47967
Closed

Add seccomp page for Node Reference Information #47687

saschagrunert opened this issue Aug 26, 2024 · 9 comments · Fixed by #47967
Assignees
@saschagrunert @VinayakPaka
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/security Categorizes an issue or PR as relevant to SIG Security. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@saschagrunert
Copy link
Member

The goal is to update https://kubernetes.io/docs/reference/node to link to a dedicated seccomp page, explaining the fields from the pod and container specification.

Per kubernetes/enhancements#135 (comment)
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 26, 2024
@saschagrunert saschagrunert mentioned this issue Aug 26, 2024
Closed
22 tasks
@saschagrunert
Copy link
Member Author

/help
/good-first-issue

@k8s-ci-robot k8s-ci-robot added 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. labels Aug 26, 2024
@VinayakPaka
Copy link

I would like to work on this issue. Please assign this issue to me.

@tengqm
Copy link
Contributor

tengqm commented Aug 26, 2024

/assign @VinayakPaka

@tengqm
Copy link
Contributor

tengqm commented Aug 26, 2024

/triage accepted
/kind feature

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. kind/feature Categorizes issue or PR as related to a new feature. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 26, 2024
@sftim
Copy link
Contributor

sftim commented Aug 27, 2024

/sig security

@k8s-ci-robot k8s-ci-robot added the sig/security Categorizes an issue or PR as relevant to SIG Security. label Aug 27, 2024
@sftim
Copy link
Contributor

sftim commented Aug 27, 2024

Does this issue have a zero to low barrier to entry @sashagrunert? If not, I'd drop the good-first-issue marker.

@saschagrunert
Copy link
Member Author

I think I can take care of that in the 1.32 cycle.

/assign

@saschagrunert
Copy link
Member Author

/remove-help
/remove-good-first-issue

@k8s-ci-robot k8s-ci-robot removed help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Aug 27, 2024
@saschagrunert saschagrunert mentioned this issue Sep 17, 2024
Merged
@saschagrunert
Copy link
Member Author

Working on this as part of #47967

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@saschagrunert saschagrunert

@VinayakPaka VinayakPaka

Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/security Categorizes an issue or PR as relevant to SIG Security. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add dedicated seccomp node reference saschagrunert/website
6 participants
@saschagrunert @tengqm @k8s-ci-robot @sftim @VinayakPaka and others