Migrate seccomp annotation to API field in manifests

[benhxy]

/kind deprecation

Seccomp (secure computing mode) support for Kubernetes has graduated to General Availability (GA). This feature can be used to increase the workload security by restricting the system calls for a Pod (applies to all containers) or individual containers.

seccomp.security.alpha.kubernetes.io/pod and container.seccomp.security.alpha.kubernetes.io/… annotations are now deprecated, and will be removed in Kubernetes v1.22.0. We should identify and transition workloads using the annotations to use the API fields before v1.21.

More resources:

• https://kubernetes.io/docs/tutorials/clusters/seccomp/
• https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190717-seccomp-ga.md

The deprecated annotation is found in these files:

deploy/cloud-controller-manager.manifest
cluster/gce/manifests/glbc.manifest
cluster/gce/manifests/cluster-autoscaler.manifest
cluster/gce/manifests/kube-apiserver.manifest
cluster/gce/manifests/kube-controller-manager.manifest
cluster/gce/manifests/etcd-empty-dir-cleanup.yaml
cluster/gce/manifests/cloud-controller-manager.manifest
cluster/gce/manifests/kube-addon-manager.yaml
cluster/gce/manifests/kube-scheduler.manifest
cluster/gce/manifests/etcd.manifest
cluster/gce/manifests/konnectivity-server.yaml
cluster/addons/metrics-server/metrics-server-deployment.yaml
cluster/addons/metadata-agent/stackdriver/metadata-agent.yaml
cluster/addons/fluentd-elasticsearch/fluentd-es-ds.yaml
cluster/addons/fluentd-elasticsearch/kibana-deployment.yaml
cluster/addons/dns/kube-dns/kube-dns.yaml.in
cluster/addons/dns/kube-dns/kube-dns.yaml.base
cluster/addons/dns/kube-dns/kube-dns.yaml.sed
cluster/addons/dns/coredns/coredns.yaml.in
cluster/addons/dns/coredns/coredns.yaml.base
cluster/addons/dns/coredns/coredns.yaml.sed
cluster/addons/dashboard/dashboard-deployment.yaml
cluster/addons/dns-horizontal-autoscaler/dns-horizontal-autoscaler.yaml
cluster/addons/cluster-loadbalancing/glbc/default-svc-controller.yaml

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[benhxy]

/remove-lifecycle stale

[cici37]

/assign
I have a WIP to address it. Will raise the pr when it is ready

[cici37]

After talking with @jpbetz offline, the current issue will be included in his WIP pr within: #214

/unassign

[jpbetz]

#216 already fixes most of these. Adding the remaining fixes to it as a separate commit now.