fix: Stop reconciling if K8sGPT CR is not in the operator namespace

[yeahdongcn]

Closes #

📑 Description

I accidentally applied K8sGPT CR to the default namespace while the operator was installed in another namespace. This causes the newly created deployment can't be scaled to the minimum replicas (sa k8sgpt not found).

apiVersion: apps/v1
kind: Deployment
metadata:
  generation: 1
  name: k8sgpt-local-ai
  namespace: default
...
status:
  conditions:
  - lastTransitionTime: "2024-07-23T05:32:23Z"
    lastUpdateTime: "2024-07-23T05:32:23Z"
    message: Deployment does not have minimum availability.
    reason: MinimumReplicasUnavailable
    status: "False"
    type: Available
  - lastTransitionTime: "2024-07-23T05:32:23Z"
    lastUpdateTime: "2024-07-23T05:32:23Z"
    message: 'pods "k8sgpt-local-ai-546d874f59-" is forbidden: error looking up service
      account default/k8sgpt: serviceaccount "k8sgpt" not found'
    reason: FailedCreate
    status: "True"
    type: ReplicaFailure

So I updated the controller-manager deployment env and added an early check before creating the needed resources in the reconciling process.

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

Testing done:

[AlexsJones]

created deployment can't be scaled to the minimum replicas (sa k8sgpt not found)

so the real issue here is the Service Account is installed in the k8sgpt-operator-system namespace or not at all?

[yeahdongcn]

created deployment can't be scaled to the minimum replicas (sa k8sgpt not found)

so the real issue here is the Service Account is installed in the k8sgpt-operator-system namespace or not at all?

Yes. This PR can prevent further resource creation.