Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Easily access installed version information #1919

Closed
ncskier opened this issue Jan 22, 2020 · 2 comments · Fixed by #2064
Closed

Easily access installed version information #1919

ncskier opened this issue Jan 22, 2020 · 2 comments · Fixed by #2064
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@ncskier
Copy link
Member

ncskier commented Jan 22, 2020

Expected Behavior

After installing Tekton Pipelines, I expect there to be an easy way to find the version of Tekton Pipelines that I am running.

Actual Behavior

As far as I know, there is not an easy way to find what version of Tekton Pipelines I have running.

Steps to Reproduce the Problem

  1. Install a version of Tekton Pipelines
  2. Try to verify what version of Tekton Pipelines you are running

Additional Info

According to these Istio guidelines, deployments should have an app and version label. Adding a version label to the Tekton Pipelines deployments would make it easy to verify what version of Tekton Pipelines is running.

The version label: This label indicates the version of the application corresponding to the particular deployment.

@vdemeester
Copy link
Member

/kind feature

We "kinda" have this in #1758 but I do like the idea of using something that is broadly used in the k8s community 👼

@tekton-robot tekton-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 22, 2020
@vdemeester
Copy link
Member

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants