pod.spec.securityContext.seccompProfile is not working on old version

[camilamacedo86]

We udpate the default scaffold on K8s and SDK to follow up the good practices and recommendations on the k8s api: https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted

The securityContext.seccompProfile was added in 1.19 and it seems not work on ocp < 4.11.
So, we might need to change the default scaffold and comment it before to do the releases so that users will be aware when they can or not use the option

[everettraven]

@camilamacedo86 is this regarding the files that are scaffolded with kustomize in the config/ directory?

[camilamacedo86]

We also will need to add a comment in the docs and a changelog to clarify that.

[everettraven]

Things to be done to resolve this issue:

• (upstream): Merge Kubebuilder PR: ✨ adding comment one the scaffolds to clarifies for common cases that do not require escalating privileges is recommended the Pods/containers be restrictive kubernetes-sigs/kubebuilder#2720
• (helm-operator-plugins): Bump KB to latest commit when ^ is merged (PR: (chore): bump Kubebuilder to commit 57aed3f94a441973deff4121a0538e20dda422a8 helm-operator-plugins#181)
• (operator-sdk): Bump KB and helm-operator-plugins to latest commit when both above are done (PR: (chore): bump Kubebuilder to commit 57aed3f94a441973deff4121a0538e20dda422a8 and helm-operator-plugins to commit 7329cace347fa1f4a74aa6835e5e557f0ddf165b #5869)
• (operator-sdk): Update docs to contain more information regarding the seccompProfile field -doc/samples: update pod security standards to clarifies usage #5867