Remove would violate PodSecurity "restricted:latest" warnings #1
Description
Activity
- added a commit that references this issue
on Apr 18, 2024 Andrei Kvapil (@kvaps) How to reproduce this problem or how it occurs, where to look? If there is any evidence, it will be possible to investigate.
Hi, Andrei Kvapil (@kvaps). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary:
- You requested a refactor of all applications to remove PodSecurity "restricted:latest" warnings.
- The focus is on addressing host namespaces, privilege escalation, capabilities, runAsNonRoot, and seccompProfile settings.
- The goal is to ensure compliance with PodSecurity standards.
- The maintainer asked for reproduction steps or evidence to investigate further.
- No additional updates or solutions have been provided since then.
Next Steps:
- Please let me know if this issue is still relevant with the latest version of cozystack by commenting here.
- If I don’t hear back within 7 days, I will automatically close this issue.
Thank you for your understanding and contribution!
- added a commit that references this issue
on Nov 4, 2025 - added a commit that references this issue
on Apr 29, 2026 - added a commit that references this issue
on May 2, 2026 - added a commit that references this issue
on May 5, 2026 - added a commit that references this issue
on May 5, 2026 - added a commit that references this issue
on Sep 7, 2026
We have to refactor all our apps to avoid such warnings: