Restriction on resources or functionality to avoid abuse #6
Comments
Great suggestion! Thanks for that! Based on the technology we are building off of (hyper/Kubernetes/etc.), here's what I would suggest:
|
Ok nice. What I was going for functionality is to have a way to prevent or permit outgoing requests to third party so to avoid DDos by using this. A way to go for this to have like a limit on the outgoing requests. I have made a script which can bring down web servers by attacking search input fields. |
Something like https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/ would be nice to have, there's a BIG difference if I need to specify 64 or 128 GiB RAM if I only need 70 GiB. More exact limits would lead to better utilization and probably better pricing opportunities too, instead of having something similar to the instance types on https://aws.amazon.com/en/ec2/pricing/on-demand/ containers allow you to be more specific about resources required and requested from the get-go while also allowing the host to enforce these. |
It would be best to include:
This way a host can select which manifest to accept prior of installing docker image.
The text was updated successfully, but these errors were encountered: