chore(KFLUXVNGD-88): Add crossplane component

[hmariset]

Initial crossplane component is added in the components of the infra-deployments.

Jira-Url: https://issues.redhat.com/browse/KFLUXVNGD-88

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hmariset
Once this PR has been reviewed and has the lgtm label, please assign manish-jangra for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[avi-biton]

/retest

[amisstea]

Moved to a draft state until konflux-ci/crossplane-control-plane#1 is merged.

[avi-biton]

@hmariset
We are getting this error:
loading generator plugins: failed to load generator: plugin HelmChartInflationGenerator.builtin.[noGrp]/crossplane.[noNs] fails configuration: must specify --enable-helm

When running the kustomization file locally, we are getting the same error.
In order to overcome it when running it manually, we use the --enable-helm flag in the kustomization file.
We should check how to overcome it in our configuration

[hmariset]

@hmariset We are getting this error: loading generator plugins: failed to load generator: plugin HelmChartInflationGenerator.builtin.[noGrp]/crossplane.[noNs] fails configuration: must specify --enable-helm

When running the kustomization file locally, we are getting the same error. In order to overcome it when running it manually, we use the --enable-helm flag in the kustomization file. We should check how to overcome it in our configuration

Yes Avi, I'm working on it. I checked a documentation to add confimap to mitigate this error, will update the PR soon.

[hugares]

You need a similar change to path as this one for both production environment, here is how it should look like:

diff --git a/argo-cd-apps/overlays/konflux-public-production/kustomization.yaml b/argo-cd-apps/overlays/konflux-public-production/kustomization.yaml
index 1c614516..52245898 100644
--- a/argo-cd-apps/overlays/konflux-public-production/kustomization.yaml
+++ b/argo-cd-apps/overlays/konflux-public-production/kustomization.yaml
@@ -181,3 +181,8 @@ patches:
       kind: ApplicationSet
       version: v1alpha1
       name: proactive-scaler
+  - path: production-overlay-patch.yaml
+    target:
+      kind: ApplicationSet
+      version: v1alpha1
+      name: crossplane-control-plane
diff --git a/argo-cd-apps/overlays/production-downstream/kustomization.yaml b/argo-cd-apps/overlays/production-downstream/kustomization.yaml
index af361355..76bbde99 100644
--- a/argo-cd-apps/overlays/production-downstream/kustomization.yaml
+++ b/argo-cd-apps/overlays/production-downstream/kustomization.yaml
@@ -197,3 +197,8 @@ patches:
       kind: ApplicationSet
       version: v1alpha1
       name: proactive-scaler
+  - path: production-overlay-patch.yaml
+    target:
+      kind: ApplicationSet
+      version: v1alpha1
+      name: crossplane-control-plane

[hugares]

you need to create a folder for staging and production since the application is getting deployed to all 3 environments with this change

[amisstea]

@hmariset I took your changes, made some adjustments, and managed to successfully deploy crossplane to OCP. Please incorporate these.

I also created cluster type overlays for vanilla k8s and OCP. Please take a look at konflux-ci/crossplane-control-plane#2. If and when that gets merged the ref in the aforementioned commit should be updated so that it no longer points to my fork of crossplane-control-plane.