Well the attacker can be inside, or can infiltrate part of your network, then combine this attack to get control over your kubernetes deployment. Yes, if the c

Well the attacker can be inside, or can infiltrate part of your network, then combine this attack to get control over your kubernetes deployment. Yes, if the call is coming from inside the house, you're already in a bad spot, but going beyond capabilities like DDoS and network traversal (such as also gaining the ability to enumerate the secrets in your k8s) is quite a bit worse. Also, a public-facing running in the cluster itself could have a vulnerability that, combined with this bug, gives an attacker much further reach.