-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Reflect tektoncd/pipeline release version as an annotation on pod #1758
Conversation
Hi @waveywaves. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
0d10efc
to
90b4048
Compare
90b4048
to
33471ea
Compare
pkg/pod/pod.go
Outdated
@@ -42,6 +43,9 @@ const ( | |||
|
|||
// These are effectively const, but Go doesn't have such an annotation. | |||
var ( | |||
releaseAnnotation = "tekon.dev/release" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tekon - > tekton
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This approach looks interesting! Have a couple of questions/requests:
-
Could we add tests to verify that the annotation is being set?
-
Could we add some release notes to the PR description? https://github.com/tektoncd/pipeline/blob/master/.github/pull_request_template.md#release-notes
-
Question: This seems to add the release version to all pods that are being created by the controller. Is there a way to add this annotation to the controller itself?
@dibyom Thanks for chekcing this out. I was planning on also adding it to the controller yaml file and then overriding the value there during build/release, similar to what has been done in knative/serving. |
Thanks! |
I think it would cascade to the pod. Honestly I think it's a nice to have to know which version of Tekton did create a certain resource, so I am 👍 on having the annotation on all the things — it doesn't cost too much either 👼 . /cc @bobcatfish |
33471ea
to
264bcc4
Compare
26ea656
to
97f5e07
Compare
97f5e07
to
813e54f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
/lgtm |
@waveywaves needs a rebase 👼 |
51a1d6e
to
7549c69
Compare
@chmouel @vdemeester Done ! |
/retest |
As a followup to tektoncd#1650 , the `tekton.dev/release` annotation is set on the pod to reflect the value of version.PipelineVersion Signed-off-by: Vibhav Bobade <[email protected]>
7549c69
to
c60516e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Vibhav Bobade [email protected]
Changes
Based on suggesstion in knative/pkg#948 have opened this PR as an alternative fix for reflecting the release version for tektoncd/pipline.
This solution reflects the version as value to the annotation
tekton.dev/release
on the controller pod.Followup of #1650 and tektoncd/cli#503
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes