[Feature]: Add E2E testing to existing kubedoop operators

[lwpk110]

Duplicates

I have searched the existing issues

Summary 💡

We propose adding end-to-end (E2E) testing to the existing kubedoop product operators using the Chainsaw testing framework. This will help ensure that all operators within the data platform are thoroughly tested. Reference implementations and examples can be found in the Trino-Operator project.

track list

• refactor: bump operator-go 0.9.0 and remove database commons-operator#55
• chore: add test config #44 trino-operator
• [Enhancement]: Use e2e tests based on the catalog level  secret-operator#40
• test: add chainsaw e2e and passed a sample usercase listener-operator#25
• refactor(image): refactor image select, reconcoler, and add auth, log superset-operator#63
• [Feature]: Add e2e test case hdfs-operator#10
• [Feature]: Add e2e test case zookeeper-operator#20
• feat: update rbac and add default e2e test hbase-operator#49
• refactor: change container image from bitnami to be our own kafka-operator#75
• feat: add cluster operation spark-k8s-operator#52
• feat: add e2e hive-operator#56
• [FEATURE] Add e2e test dolphinscheduler-operator#64

Examples 🌈

1. Integrate E2E Tests Using Chainsaw:

   • Utilize the Chainsaw testing framework to build E2E tests.
   • Refer to the Chainsaw documentation: Chainsaw Test.

2. Example Reference:

   • Refer to the Trino-Operator project for implementation examples: Trino-Operator.

3. Track List for E2E Testing:

   • Ensure all listed operators have E2E tests added.

Motivation 🔦

Adding E2E testing to the kubedoop product operators is essential to ensure the reliability and robustness of each operator within the data platform. By using the Chainsaw testing framework, we can automate and standardize the testing process, reducing the likelihood of bugs and issues. This also aligns with industry best practices for software quality assurance.