[DSPv2] Add/manage missing empty tekton config CMs/Secrets

[gmfrasca]

In the DSPv2 PoC, there are some CMs and Secrets that need to simply be created in order for the v2 backend component to populate data with. To be specific, these are:

Config Maps

• config-artifact-bucket
• config-artifact-pvc
• config-defaults
• config-observability
• config-spire
• config-trusted-resources
• feature-flags

Secrets

• kfp-exithandler-webhook-certs
• kfptask-webhook-certs
• tekton-pipelineloop-webhook-certs

Add these to the V2 Manifests, or alternatively, figure out why the OpenShift Pipelines Operator (v1.12.0+) is no longer supply them.

[amadhusu]

Testing @gmfrasca's branch of dspv2 with Openshift Pipelines Operator v1.11.1 to test if the creation of these Config Maps and Secrets works as its supposed to.

[amadhusu]

So this isn't related to Openshift Pipelines Operator not providing these respective Config Maps & Secrets as I can see in both Openshift Pipelines Operator v1.11.1 and v1.12.0, there is an instance "pipeline-main-static-x" of CRD TektonInstallerSets which successfully creates this in the openshift-pipelines namespace. Also only the webhook pods are failing to access/leverage these config maps and secrets.

Currently Investigating the code under v2 and checking if there is something related to how the respective roles are missing some get/list permissions for these respective failures.

[amadhusu]

Pulled in all the latest commits on the dspv2 branch to catch up on backlog, the issue persists. So I am going ahead with manual creation of these secrets & configs and will update codebase if that works.

[rimolive]

Looks like #443 is merged so closing this issue.