Current implementation does not allow to configure limits and requests for kube-rbac-proxy container in devworkspace-webhook-server pod. It leads to violation to security best practices, for example: container CPU and memory limits should be enforced.
Additional context
The similar issue is already solved for another container in this pod via envvars:
Description
Current implementation does not allow to configure limits and requests for kube-rbac-proxy container in devworkspace-webhook-server pod. It leads to violation to security best practices, for example: container CPU and memory limits should be enforced.
Additional context
The similar issue is already solved for another container in this pod via envvars:
Is it possible to have something like above but for kube-rbac-proxy container?