I don't understand how knocking in if itself is bad. It's just a technique to add a layer of protection. In my case, all internal services in a kubernetes clus

I don't understand how knocking in if itself is bad. It's just a technique to add a layer of protection. In my case, all internal services in a kubernetes cluster have no path that allow it to be accessed from the outside. Occasionally, developers might want to do so, say to access a database or prometheus server. The way to properly do this, imo, is to use a hardened service that functions as a networking proxy. Use proper encryption keys for access, and it should be quite hard to bust open. Where does port knocking come in? That service should need to be exposed at all times. So, use port knocking to configure the infrastructure to temporarily allow access from your IP, to that proxy servers IP, on that particular port. I'm more inclined to not take it serious, if such a simple mechanism isn't in place to protect infrastructure.