While Upgrading operator from v1.1.2 to v1.2.0, I noticed that the pod `openshift-gitops-application-controller` does not come up. While investing this, I found a major issue.

v1.2 creates a resource quota for the namespace `openshift-gitops`. When a namespace is assigned with a resource quota, all the containers in the namespace should be created with resource requests/limits. The major issue is when you are upgrading the operator to v1.2, you already have all the pods created without resource request/limits by previous version of the operator.

After upgrading to v1.2, Resource Quota has been configured in `openshift-gitops` namespace.   However, existing Deployments do not contain Resource limit/request.   When any one of the existing pods are deleted, new pods failed to start because resource limit/requests are not defined in the Deployments.

Expected Behavior

• any pods can be restarted successfully after upgrading to v1.2
• default resource limits/requests should be add to Deployments/StatefulSets if they do not exist.