🐛 Setting experimental_deploy_kai: 'false' OR kai_solution_server_enabled: 'false' in the Tackle CR does not terminate the Kai solution server pods as expected.

[sshveta]

Changing the experimental_deploy_kai flag in the Tackle Custom Resource to 'false' does not terminate or remove the Kai solution server pods as expected. The kai-api pods remain running in the openshift-mta namespace, indicating that the operator/controller did not reconcile the CR to disable the deployment.

Steps :

1. Check existing Kai pods:
       ` kubectl -n openshift-mta get pods -l app=kai-api`
2. Edit the Tackle CR to set experimental_deploy_kai: 'false'.
3. Save the CR and wait for reconciliation.
4. Observe that the kai-api pods are still running

Expected Behavior:

Setting experimental_deploy_kai: 'false' should cause the operator to remove all Kai-related pods and associated resources.

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for 60 days.
It will remain open for visibility and reporting purposes.
Please comment if this issue is still relevant.