Bug Report: Profile ‘lite’ is creating extra components
Description
When deploying Tekton Operator with spec.profile: lite, the expected components are not being correctly filtered. Unnecessary components like Tekton Results and Chains are being installed, even though they are not part of the lite profile.
Expected Behavior
With spec.profile: lite, the Operator should install only:
tekton pipelines controllers
Actual Behavior
NAME READY STATUS RESTARTS AGE tekton-chains-controller-5ccfb454f9-cf2v4 1/1 Running 0 4m42s tekton-events-controller-686ff59c66-29nzx 1/1 Running 0 6m30s tekton-operator-proxy-webhook-94f785b44-rc7qw 1/1 Running 0 6m29s tekton-pipelines-controller-d768b6f47-q2ck9 1/1 Running 0 6m30s tekton-pipelines-remote-resolvers-6fdd86bfb7-8vh7m 1/1 Running 0 6m30s tekton-pipelines-webhook-6f4784bb55-dmnx2 1/1 Running 0 6m30s tekton-results-api-6f6f858d79-jrwtc 1/1 Running 0 4m19s tekton-results-postgres-0 1/1 Running 0 4m19s tekton-results-retention-policy-agent-5865bf5fd4-9qcxr 1/1 Running 0 4m19s tekton-results-watcher-779bbf74f7-tmq47 1/1 Running 0 4m19s
Steps to Reproduce the Problem
-
Install Tekton Operator on a clean Kubernetes/Openshift cluster.
-
Create a TektonConfig with:
apiVersion: operator.tekton.dev/v1alpha1 kind: TektonConfig metadata: name: config namespace: tekton-pipelines spec: profile: lite
- Observe pods in tekton-pipelines:
oc get pods -n tekton-pipelines
- Note that Results and Chains pods are still running.
Additional Info
- Kubernetes version:
Client Version: v1.17.0-4-g38212b5 Server Version: v1.32.0
- Tekton Pipeline version: version: v1.1.0
/good-first-issue
@pramodbindal: This request has been marked as suitable for new contributors.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.
In response to this:
/good-first-issue
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.