-
Notifications
You must be signed in to change notification settings - Fork 231
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
Expected Behavior
Performance values set in TektonConfig in chains spec should be reflected both in:
- Chains Controller pod labels and args
- corresponding ConfigMap- tekton-chains-config-leader-election should be kept in sync with current values
Actual Behavior
- Controller pod has performance labels and args correctly set as per TektonConfig.
- ConfigMap is not updated with the current TektonConfig values.
Steps to Reproduce the Problem
- Launch kind cluster
- Install Tekton operator -
kubectl apply -f https://storage.googleapis.com/tekton-releases/operator/latest/release.yaml - Edit config:
kubectl edit tektonconfig config - Set the following performance attributes
chain: artifacts.oci.format: simplesigning artifacts.oci.storage: oci artifacts.pipelinerun.format: in-toto artifacts.pipelinerun.storage: oci artifacts.taskrun.format: in-toto artifacts.taskrun.storage: oci disabled: false options: {} performance: buckets: 3 disable-ha: true kube-api-burst: 20 kube-api-qps: 10 replicas: 3 statefulset-ordinals: false threads-per-controller: 4 - Verify that the number of chains controller pods reflects the replica count set in config and the labels + args of each pod include the correct config values.
- However the configmap
tekton-chains-config-leader-electiondoes not reflect the current state of any of the performance configuratios
Additional Info
-
Kubernetes version:
Output ofkubectl version:
Client Version: v1.31.1
Kustomize Version: v5.4.2
Server Version: v1.31.0 -
Tekton Operator version:
Output of `kubectl get pods -n tekton-operator -l app=tekton-operator -o=jsonpath='{.items[0].spec.containers[0].env[?(@.name=="VERSION")].value}'
v0.77.0
StringKe
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.