Referring SPIKE. With the driftDetection enabled, for the package stated in the issue title that was deployed on the bb-development-eks cluster, test if reconciliation or correction is properly performed when drift was detected.

Packages that will be tested in this epic:

• Vault
• MinIO/Operator
• Mattermost
• Velero
• External Secrets Operator

Test Cases: Test the respective package on all objects such as Deployment, StatefulSet, Pod.

The drift that should be detected include replicas mismatch, resource mismatch or as stated in the parent epic, duplicate 'imagePullSecrets' elements.

1. Resource mismatch:

   • Manually change the values for resources.limits.cpu/memory and resources.requests.cpu/memory in the object manifests and verify the values of the running objects should reconcile back to all of it's original values.

2. Replicas Mismatch:

   • Manually change the replicas values to different values and verify the new pods spawn up and then reconciled back to it's original replicas values.

3. Modify container image:

   • Manually change the image: any different names and versions and verify the original image is restored.

4. Add extra imagePullSecrets:

     imagePullSecrets:
   
     - name: public-registry
   
     - name: private-registry

   • Add a new public-registry before the original private-registry and verify it associated objects still run without errors. Remember to remove the public-registry entry afterwards as no expected reconciliation happens here.

5. Please write a quick summary on all test results either passing or failing to reconcile. Create issues to research or fix any errors, if needed.

If any reconciliation tests failed, document any and all errors and create issues to research/fix.