Functional tests on drift detection for EK, eck-operator, authservice, harbor, mimir, sonarqube, anchore, argocd, cluster-auditor, gatekeeper
I'm working on these packages:
- mimir
Drift Detection working good in mimir after deployed it k3d cluster. I updated numbers of replicas from 1 to 4.
- anchore
Drift Detection working good in anchore after deployed it k3d cluster. I updated numbers of replicas from 1 to 3.
- argocd
Drift Detection working good in argocd after deployed it k3d cluster. I updated numbers of replicas from 1 to 3.
- cluster-auditor
Drift Detection working good in cluster-audoitor after deployed it k3d cluster. I updated numbers of replicas from 1 to 4.
- gatekeeper
Drift Detection working good in gatekeeper after deployed it k3d cluster. I updated numbers of replicas from 1 to 4. Also updated the resources limits cpu and memory.
- EK
- eck-operator
I deployed dev cluster (bb-development-eks) and I enabled Drift detection and I did testing and drift is working fine 
- authservice
Drift Detection working good in authservice after deployed it dev cluster. I updated numbers of replicas from 2 to 4 
- harbor
harbor Drift Detection working good in harbor after deployed it dev cluster. I updated numbers of replicas from 1 to 5
- sonarqube
Enabled Drift detection in Sonarqube I changes replicas from 1 to 4 and reconciliation works fine.
