Epic Goal

• Extend installation of PAC via operator on kubernetes/kind cluster

Why is this important?

• Currently, the Operator supports PAC installation only on OpenShift. To support upstream adoption and broader usage, this capability needs to be extended to Kubernetes/Kind clusters.

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• Rename the CRD and associated code from openshiftpipelinesascodes.operator.tekton.dev to pipelinesascodes.operator.tekton.dev.

• Refactor the codebase to separate Kubernetes-specific logic (e.g., transformers) into a dedicated kubernetes directory, and provide an OpenShift extension following the existing pattern used for other components.

• Provide a clear upgrade path for existing users by supporting both CRDs (openshiftpipelinesascodes.operator.tekton.dev and pipelinesascodes.operator.tekton.dev) during the transition period, with plans to deprecate the former in a future release.

• Update TektonConfig to remove the explicit mention of platform as openshift for PAC, aligning it with the configuration pattern used by other components such as Pipelines, which are platform-agnostic.

• Comprehensive regression testing is required on both Kubernetes and OpenShift platforms, as the effort involves refactoring existing code, not just extending support to Kubernetes.

Dependencies (internal and external)

1. If PAC were to go upstream, changing the crd out of openshiftpipelinesascodes.operator.tekton.dev is paramount.

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment