Expected Behavior
Tekton operator should deploy the default profile components.
Actual Behavior
Tekton operatos stucks on error due to missing CRDs in Helm Chart template.
The missing CRDs are the following:
- tektonschedulers.operator.tekton.dev
- tektonmulticlusterproxyaaes.operator.tekton.dev
Steps to Reproduce the Problem
- Install Helm Chart v0.79.0 on kind cluster
- Check logs of tekton-operator
E0504 18:33:24.645882 1 reflector.go:166] "Unhandled Error" err="k8s.io/client-go@v1.5.2/tools/cache/reflector.go:251: Failed to watch *v1alpha1.TektonMulticlusterProxyAAE: failed to list *v1alpha1.TektonMulticlusterProxyAAE: the server could not find the requested resource (get tektonmulticlusterproxyaaes.operator.tekton.dev)" logger="UnhandledError"
W0504 18:33:28.951174 1 reflector.go:569] k8s.io/client-go@v1.5.2/tools/cache/reflector.go:251: failed to list *v1alpha1.TektonScheduler: the server could not find the requested resource (get tektonschedulers.operator.tekton.dev)
E0504 18:33:28.951266 1 reflector.go:166] "Unhandled Error" err="k8s.io/client-go@v1.5.2/tools/cache/reflector.go:251: Failed to watch *v1alpha1.TektonScheduler: failed to list *v1alpha1.TektonScheduler: the server could not find the requested resource (get tektonschedulers.operator.tekton.dev)" logger="UnhandledError"
Additional Info
Expected Behavior
Tekton operator should deploy the default profile components.
Actual Behavior
Tekton operatos stucks on error due to missing CRDs in Helm Chart template.
The missing CRDs are the following:
Steps to Reproduce the Problem
Additional Info
Kubernetes version:
Output of
kubectl version:Tekton Pipeline version:
Output of
tkn versionorkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'