Having filtering Docker socket traffic by action/method and by name/label as separate services/containers sounds like a waste of resources and making things more fragile... I would suggest implementing features from the companion docker-proxy service to transform it into the most powerful tool for the job.
Having filtering Docker socket traffic by action/method and by name/label as separate services/containers sounds like a waste of resources and making things more fragile... I would suggest implementing features from the companion docker-proxy service to transform it into the most powerful tool for the job.