podman play kube seccomp annotations don't function like k8s

[haircommander]

follow up issue to track

k8s yaml format parses a profile path like
localhost/ with a global value <seccomp_root> filled, whereas now this PR does localhost:<seccomp_root>/

We can either hardcode the configuration path, add a flag to play kube to customize the path, or add a config value. I don't think it matters very much which we do, but I can imagine future users needing some sort of consistency with k8s here.

[rhatdan]

@baude @mheon WDYT?

[vrothberg]

I think we should be as close to K8s behavior as possible.

[rhatdan]

@haircommander can you open a PR to fix this?

[github-actions]

This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days.

[rhatdan]

@haircommander Any chance to work on this?