Skip to content

Tekton Dashboard and Webhooks Extension release v0.7.0
Compare
Choose a tag to compare
@a-roberts a-roberts released this 04 Jun 15:53
v0.7.0
eafe3ad
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This is the Triggers 0.5 supporting release that also supports Pipelines 0.11, 0.12, and 0.13. We've seen no problems with Triggers 0.4 either.

Lots of useful bug fixes and features here, such as:

  • Triggers 0.5 support in the Dashboard and Webhooks Extension
  • Update to Carbon 10.12
  • Fix character encoding of displayed Secrets username column
  • Fix the validation of PipelineResources in CreateTaskRun
  • Add more translated strings
  • Stop creation of non-existent Tasks being used in TaskRuns
  • Lots of backend changes are in that lay the foundations for future Dashboard releases that allow single-namespace only installs
  • Conditions are now available to view as a resource
  • Fix for extra characters displayed on an Import Resources tooltip
  • Removed very noisy sanitizing secret debug message

Note that with the introduction of Triggers and Pipeline namespace lookup flags, it’s now possible to have the versions of these components detected in different namespaces by the Tekton Dashboard.

To accomodate the variety of installation methods, you can change the lookup location with the following command (this assumes you already created the openshift-pipelines namespace first if it didn't exist, with oc create ns openshift-pipelines).

curl -L https://github.com/tektoncd/dashboard/releases/download/v0.7.0/openshift-tekton-dashboard-release.yaml\
| sed -e 's/--pipelines-namespace=openshift-pipelines/--pipelines-namespace=tekton-pipelines/g' \
| sed -e 's/--triggers-namespace=openshift-pipelines/--triggers-namespace=tekton-pipelines/g' \
| kubectl apply -f -

In this case, the lookup namespace will be tekton-pipelines, even on OpenShift - and this is especially useful if you’re installing using a mechanism that results in the Tekton deployments being in tekton-pipelines - which is currently where Tekton is installed into when you do not use the OpenShift Pipelines operator.

The OpenShift Pipelines operator uses the openshift-pipelines namespace and as such no changes will be required.

Look out for improvements to our install mechanism in a future release - there are plenty of ways to install Tekton and we're doing our best to accomodate them all.

Credits:

Assets 8
Loading