huskyCI runs all its securityTests using a Docker API component. It works fine but some companies may eventually face some problems when scaling to multiple VMs running this component.
By adding a load balancer, for instance, huskyCI has no logic to understand which VM behind it should query to check if a particular securityTest has finished.
It would be great if
We add a new component to huskyCI that uses k8s to run our securityTests containers. If a company uses Rancher, this process of running containers can be used as a service, for example.
What we expect
This one can be tricky because a few refactoring in securitytest package is needed. However, we will be very happy if we have an interface in it so that companies choose which best fits their environment.
Motivation
huskyCI runs all its securityTests using a Docker API component. It works fine but some companies may eventually face some problems when scaling to multiple VMs running this component.
By adding a load balancer, for instance, huskyCI has no logic to understand which VM behind it should query to check if a particular securityTest has finished.
It would be great if
We add a new component to huskyCI that uses k8s to run our securityTests containers. If a company uses Rancher, this process of running containers can be used as a service, for example.
What we expect
This one can be tricky because a few refactoring in securitytest package is needed. However, we will be very happy if we have an interface in it so that companies choose which best fits their environment.
Tips