Tekton operator >= 0.73 raise as error: panic: runtime error: invalid memory address or nil pointer dereference #2476
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
l-qing
added a commit
to l-qing/tekton-operator
that referenced
this issue
Jan 3, 2025
l-qing
added a commit
to l-qing/tekton-operator
that referenced
this issue
Jan 3, 2025
4 tasks
l-qing
added a commit
to l-qing/tekton-operator
that referenced
this issue
Jan 6, 2025
l-qing
added a commit
to l-qing/tekton-operator
that referenced
this issue
Jan 7, 2025
l-qing
added a commit
to l-qing/tekton-operator
that referenced
this issue
Jan 8, 2025
|
I am seeing the same issue running in the latest Minikube with Kubernetes 1.31 when I upgraded from 73 to 74 (to test before deploying). 73 was working fine. When I copy over the config on the docs it seems to work. This is the error I see: If I copy the example TektonConfig and update the properties to match what I have (which is just a smaller config) and remove these properties
it worked. So, my TektonConfig looks like: apiVersion: operator.tekton.dev/v1alpha1
kind: TektonConfig
metadata:
name: config
spec:
profile: all
targetNamespace: tekton-pipelines
targetNamespaceMetadata:
labels: {}
annotations: {}
config:
tolerations: []
priorityClassName: system-cluster-critical
pipeline:
await-sidecar-readiness: true
coschedule: isolate-pipelinerun
disable-affinity-assistant: true
disable-creds-init: false
disable-inline-spec: "pipeline,pipelinerun,taskrun"
enable-api-fields: stable
enable-bundles-resolver: true
enable-cel-in-whenexpression: false
enable-cluster-resolver: true
enable-custom-tasks: false
enable-git-resolver: true
enable-hub-resolver: false
enable-param-enum: false
enable-provenance-in-status: true
enable-step-actions: false
enforce-nonfalsifiability: none
keep-pod-on-cancel: false
max-result-size: 4096
metrics.count.enable-reason: false
metrics.pipelinerun.duration-type: histogram
metrics.pipelinerun.level: pipeline
metrics.taskrun.duration-type: histogram
metrics.taskrun.level: task
require-git-ssh-secret-known-hosts: false
results-from: termination-message
running-in-environment-with-injected-sidecars: true
send-cloudevents-for-runs: false
set-security-context: false
trusted-resources-verification-no-match-policy: ignore
performance:
disable-ha: true
buckets: 1
replicas: 1
threads-per-controller: 2
kube-api-qps: 5.0
kube-api-burst: 10
options:
disabled: false
configMaps: {}
deployments: {}
webhookConfigurationOptions: {}
pruner:
disabled: false
keep: 1
schedule: "0 * * * *"
resources:
- taskrun
- pipelinerun
chain:
disabled: true
dashboard:
readonly: false
options:
disabled: false
configMaps: {}
deployments: {}
webhookConfigurationOptions: {}
hub:
params:
- name: enable-devconsole-integration
value: "true"
options:
disabled: true
configMaps: {}
deployments: {}
webhookConfigurationOptions: {} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Deployment on kubernetes of the Tekton Operator (>= 0.73) should not raise an error:
panic: runtime error: invalid memory address or nil pointer dereferencebut a more human readable.Actual Behavior
Tekton operator >= 0.73 raise as error: panic: runtime error: invalid memory address or nil pointer dereference
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}'The text was updated successfully, but these errors were encountered: