We need to talk about helm and the 10-operator porting plan about acto HOT 2 CLOSED

From @kevchentw

My current thought is that we can support both deployment method (helm & yamls).
The only difference is calling deploy_operator_helm_chart() or deploy_operator(). So we can distinguish which deploy method with different command parameters.

Yes! I think it's a good idea to decouple the deployment and testing and support multiple deployment methods.

from acto.

From @kevin85421

Currently, Kuan-Yin, Yicheng, and I are planning to apply Acto to find bugs in other operators. However, there are two blocker issues for us to find bugs in other operators.

(1) The current deployment methods cannot work for most operators => Hence, Kuan-Yin and I decided to provide Helm support to address this.

(2) Currently, the input CR specifications are generated by the candidates.yaml. However, currently the input generator is hard-coded to rabbitMQ. Hence, it cannot work on other operators (for MongoDB operator, even the very simple candidates.yaml will cause Acto crash.) => Hence, Yicheng is working on fix these bugs.

After we finished (1) and (2), we will start to run the experiments to check whether Acto can detect bugs in these operators or not. Then, we hope to find some bug patterns and propose some testing methods to improve Acto.

from acto.