-
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
Bump kubernetes to 1.16.5 and knative/pkg to release-0.12 #1894
Conversation
/hold |
9e48050
to
b7ffda9
Compare
// A function that infuses the context passed to Validate/SetDefaults with custom metadata. | ||
func(ctx context.Context) context.Context { | ||
// FIXME(vdemeester) uncomment that for auto-conversion | ||
// return v1alpha2.WithUpgradeViaDefaulting(store.ToContext(ctx)) |
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.
Conversion webhooks are imminent in knative/pkg btw cc @dprotaso
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.
👼
7b2ab24
to
e00dbf3
Compare
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@@ -101,7 +111,7 @@ func TestRecordPipelineRunDurationCount(t *testing.T) { | |||
err = metrics.DurationAndCount(test.taskRun) | |||
assertErrIsNil(err, "DurationAndCount recording recording got an error", t) | |||
metricstest.CheckDistributionData(t, "pipelinerun_duration_seconds", test.expectedTags, 1, test.expectedDuration, test.expectedDuration) | |||
metricstest.CheckCountData(t, "pipelinerun_count", test.expectedTags, test.expectedCount) | |||
metricstest.CheckCountData(t, "pipelinerun_count", test.expectedCountTags, test.expectedCount) |
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.
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 was a while ago, but I think maybe done by @anniefu?
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.
Hmm, I created the metricstest helper package a while ago, but didn't do this particular test change.
A cursory glance implies that someone added a new tag to the "pipelinerun_count" metric so it has a different set of metrics tags as the "pipelinerun_duration_seconds" metric now, which isn't a problem.
f117375
to
f416057
Compare
I think it's gonna be green 🎉 💚 |
Have a parent/teacher thing now, but will TAL after. Thanks for doing this!!! 🙏👍 |
Just double checking, but knative is also requiring 1.15 or greater now? I think the GKE default is still 1.13 but 1.15 is available 🤔 Anyway assuming that: |
/retest |
8f34f71
to
61a5a52
Compare
/hold cancel |
6d9b378
to
a365c27
Compare
This is way simpler to follow. This change the following: - Add validating and mutating webhook definition *in* yaml (so it gets registered before the webhook starts) - Rename the controller service/deployment from `tekton-pipelines-controller` to `controller` - Rename the webhook service/deployment from `tekton-pipelines-webhook` to `webhook` - Use `pipeline.tekton.dev/release` instead of `tekton.dev/release` ; mainly to let other project use their own (`trigger.tekton.dev/release`). Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
It is green 🎉 🕺 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg 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 |
/LGTM |
We should probably update some docs when we bump the k8s dependency also, e.g.: |
And the release notes too, ill add something |
In tektoncd#1894 we bumped our k8s dependencies such that a cluster must now be running at least 1.15.
In #1894 we bumped our k8s dependencies such that a cluster must now be running at least 1.15.
It is probably useful to also formulate some guidance around how these versions are bumped. We recently went through this exercise, and I'm happy to share if it's something you think it'd be worth aligning on. |
In tektoncd#1894 we bumped our k8s dependencies such that a cluster must now be running at least 1.15. This adds it to the README.md, to make sure user know it too. Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
In #1894 we bumped our k8s dependencies such that a cluster must now be running at least 1.15. This adds it to the README.md, to make sure user know it too. Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
Changes
This updates
cmd/webhook/main.go
to use latest knative/pkg code, most simplifiedThis also changes the following:
registered before the webhook starts)
Rename the controller service/deployment fromtekton-pipelines-controller
tocontroller
Rename the webhook service/deployment fromtekton-pipelines-webhook
towebhook
pipeline.tekton.dev/release
instead oftekton.dev/release
;mainly to let other project use their own (
trigger.tekton.dev/release
)./hold waiting for 0.10 to be out to get this merge
Also, this moves the min k8s server version to 1.15.x
Closes #1113
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