Unable to get pods when using kubectl describe node

[MaxFedotov]

Bug description

After updating from capsule-proxy v0.5.0 to v0.7.0 users lost the ability to get a list of pods on nodes when using kubectl describe node

The following error can be found when using -v 10 for this command:

I0828 13:07:53.486929   87563 request.go:1212] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"foo\" cannot list resource \"pods\" in API group \"\" at the cluster scope","reason":"Forbidden","details":{"kind":"pods"},"code":403}

This regression was introduced by this commit, which removed proxy module for pods from internal/webserver/webserver.go file:

-               pod.Get(n.reader),

How to reproduce

kubectl describe node {nodeName} -v 10

Expected behavior

Users should be able to see pods running on the node

Logs

I0828 13:07:53.486929   87563 request.go:1212] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"foo\" cannot list resource \"pods\" in API group \"\" at the cluster scope","reason":"Forbidden","details":{"kind":"pods"},"code":403}

Additional context

• Capsule-Proxy version: (capsule-proxy --version): v0.7.0
• Helm Chart version: (helm list -n capsule-system)
• Kubernetes version: (kubectl version)