Display used seccomp profile on `kubectl describe`

[saschagrunert]

What would you like to be added:

Determining the used seccomp profile for a container is a non-trivial task in Kubernetes. The security context features a dedicated SeccompProfile field: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.22/#seccompprofile-v1-core
There are also the deprecated seccomp annotations. Both, annotations as well as the field are available per pod and per container. This also means that containers can overwrite the pod values, whereas the container values get inherited by the pod if not set.

This logic could be built into kubectl describe, making it easy for users to determine the used seccomp profile of a container.

cc @sftim

[eddiezane]

/triage accepted
/priority backlog
/good-first-issue

This work would need to done in https://github.com/kubernetes/kubernetes/blob/91ff1f9840278ec9c58089d891d6d594e5055bab/staging/src/k8s.io/kubectl/pkg/describe/describe.go#L692.

[k8s-ci-robot]

@eddiezane:
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:

/triage accepted
/priority backlog
/good-first-issue

This work would need to done in https://github.com/kubernetes/kubernetes/blob/91ff1f9840278ec9c58089d891d6d594e5055bab/staging/src/k8s.io/kubectl/pkg/describe/describe.go#L692.

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.

[eddiezane]

/assign @ncapps

[k8s-ci-robot]

@eddiezane: GitHub didn't allow me to assign the following users: ncapps.

Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @ncapps

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.

[ncapps]

/assign @ncapps