I’m trying Tekton on a Kind cluster and successfully configured Tekton Dashboard to work with Ingress rules. But I don’t have a dedicated domain name, and unlikely to have one later. This Tekton instance will be exposed on a subpath on another domain through another NGINX.
But Tekton Dashboard doesn’t seem to work on subpath locations. Tekton Dashboard exposed with Ingress path: /
works well, but if I change it to path: /tekton
, it doesn’t work.
So, is it designed to work only at root path? No support for working on subpath?
P.S.
I’m going to use Kind cluster for production too as I do not have access to a Kubernetes cluster. This is small service and we don’t need scale, but just CI/CD-as-code. And nowadays it seems all of new CI/CD implementations are designed only for Kubernetes.
2
Answers
Tekton Dashboard does support being exposed on a subpath, it attempts to detect the base URL to use and adapts accordingly. For example, if you run
kubectl proxy
locally against the target cluster you can then access the Dashboard athttp://localhost:8001/api/v1/namespaces/tekton-pipelines/services/tekton-dashboard:http/proxy/
More details about the issue you’re encountering would be useful to help debug, e.g. Dashboard version? Is anything loading at all? Ingress controller and config? Any errors in the browser console / network tab, etc.
You can also use the following Ingress: