While it all falls under "security", it feels too confused in what it's trying to show.<p>I think it focuses too much on the happy path of security, typically you'll want to focus on specific areas. For example, access to the kubernetes API and what you can do, effective bypasses of RBAC by impersonation because a user has access to something else like argocd or a job system. Or another example, network paths and how they're all connected together.<p>Some boxes are weirdly disconnected, e.g. things point to the ingress but nothing flows out (hiding the potential that an ingress can be confused to route to your internal services), runtimes sit to the side when they should sit above the kernel, namespace is just a box to the side, etc.
Nice job, I'll have a deeper look at it when I'll be back at the large screen.<p>SVG link for the impatient: <a href="https://raw.githubusercontent.com/lars-solberg/kubesec-diagram/4ed560803b7eb9f0263f8ecb1895c4e946352ac9/kubesec-diagram.svg" rel="nofollow">https://raw.githubusercontent.com/lars-solberg/kubesec-diagr...</a>