You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Successful deployment of all resources with everything working out of the box.
Actual Behavior
Tekton dashboard cannot fetch the configmaps that contain the versions of the tekton components. Most likely due to a role or role binding issue that happens when you customize the defaultTargetNamespace value in the helm chart.
If you don't specify a custom namespace and let the operator deploy everything in the default tekton-pipelines namespace the issue is not present!
Steps to Reproduce the Problem
Deploy Tekton Operator (tekton-operator-0.74.0) via HELM using the values.yaml values.yaml.txt
Wait for the operator to finish with deployment
Create an ingress for the Tekton Dashboard and notice the errors
Raw Error:
{"level":"error","ts":1733306990.525748,"caller":"endpoints/dashboard.go:27","msg":"Error getting the Tekton triggers info ConfigMap: configmaps \"triggers-info\" is forbidden: User \"system:serviceaccount:mmp-pipelines:tekton-dashboard\" cannot get resource \"configmaps\" in API group \"\" in the namespace \"tekton-pipelines\"","stacktrace":"github.com/tektoncd/dashboard/pkg/endpoints.getVersion\n\tgithub.com/tektoncd/dashboard/pkg/endpoints/dashboard.go:27\ngithub.com/tektoncd/dashboard/pkg/endpoints.getTriggersVersion\n\tgithub.com/tektoncd/dashboard/pkg/endpoints/dashboard.go:56\ngithub.com/tektoncd/dashboard/pkg/endpoints.IsTriggersInstalled\n\tgithub.com/tektoncd/dashboard/pkg/endpoints/dashboard.go:67\ngithub.com/tektoncd/dashboard/pkg/endpoints.Resource.GetProperties\n\tgithub.com/tektoncd/dashboard/pkg/endpoints/cluster.go:64\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2166\nnet/http.(*ServeMux).ServeHTTP\n\tnet/http/server.go:2683\ngithub.com/tektoncd/dashboard/pkg/csrf.(*csrf).ServeHTTP\n\tgithub.com/tektoncd/dashboard/pkg/csrf/csrf.go:74\nnet/http.serverHandler.ServeHTTP\n\tnet/http/server.go:3137\nnet/http.(*conn).serve\n\tnet/http/server.go:2039"}
{"level":"error","ts":1733306923.1582959,"caller":"endpoints/dashboard.go:27","msg":"Error getting the Tekton pipelines info ConfigMap: configmaps \"pipelines-info\" is forbidden: User \"system:serviceaccount:mmp-pipelines:tekton-dashboard\" cannot get resource \"configmaps\" in API group \"\" in the namespace \"tekton-pipelines\"","stacktrace":"github.com/tektoncd/dashboard/pkg/endpoints.getVersion\n\tgithub.com/tektoncd/dashboard/pkg/endpoints/dashboard.go:27\ngithub.com/tektoncd/dashboard/pkg/endpoints.getPipelineVersion\n\tgithub.com/tektoncd/dashboard/pkg/endpoints/dashboard.go:46\ngithub.com/tektoncd/dashboard/pkg/endpoints.Resource.GetProperties\n\tgithub.com/tektoncd/dashboard/pkg/endpoints/cluster.go:46\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2166\nnet/http.(*ServeMux).ServeHTTP\n\tnet/http/server.go:2683\ngithub.com/tektoncd/dashboard/pkg/csrf.(*csrf).ServeHTTP\n\tgithub.com/tektoncd/dashboard/pkg/csrf/csrf.go:74\nnet/http.serverHandler.ServeHTTP\n\tnet/http/server.go:3137\nnet/http.(*conn).serve\n\tnet/http/server.go:2039"}
Additional Info
Kubernetes version:
Output of kubectl version:
Client Version: v1.30.6
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.6
Tekton Pipeline version:
Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
v0.65.2
Plain vanilla k8s, deployed via Kubespray on Ubuntu Server 24.04.1 LTS
The text was updated successfully, but these errors were encountered:
The issue is caused by invalid configuration in the dashboard args.
When changing the helm value of defaultTargetNamespace, the operator provisioned deployment for the Tekton Dashboard is not being updated to reflect the NS change.
Expected Behavior
Successful deployment of all resources with everything working out of the box.
Actual Behavior
Tekton dashboard cannot fetch the configmaps that contain the versions of the tekton components. Most likely due to a role or role binding issue that happens when you customize the
defaultTargetNamespace
value in the helm chart.If you don't specify a custom namespace and let the operator deploy everything in the default
tekton-pipelines
namespace the issue is not present!Steps to Reproduce the Problem
Raw Error:
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
v0.65.2
Plain vanilla k8s, deployed via Kubespray on Ubuntu Server 24.04.1 LTS
The text was updated successfully, but these errors were encountered: