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

Bump knative to release-0.20 #3605

Merged
merged 2 commits into from
Jan 8, 2021
Merged

Conversation

vdemeester
Copy link
Member

@vdemeester vdemeester commented Dec 7, 2020

Changes

Bump knative to 0.20.

This also fix controller flag handling 🙃 (#3663, maybe others) :

Do not call flag.Parse() as it happens in
sharedmain.ParseAndGetConfigOrDie. Move anything that needs the flag
value after that call.

This also does something with QPS and Burst flag are they are already
defined in knative/pkg but with different default.

/kind misc

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

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

Updating knative.dev/pkg to release-0.20. This bumps the minimum supported version of kuberenetes to 0.17

@tekton-robot tekton-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/misc Categorizes issue or PR as a miscellaneuous one. labels Dec 7, 2020
@tekton-robot tekton-robot requested review from dlorenc and a user December 7, 2020 10:04
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 7, 2020
@vdemeester
Copy link
Member Author

/cc @tektoncd/core-maintainers

@tekton-robot tekton-robot requested a review from a team December 7, 2020 10:04
@vdemeester vdemeester force-pushed the bump-knative branch 2 times, most recently from a5bfcb2 to e795a6a Compare December 7, 2020 10:50
@vdemeester
Copy link
Member Author

vdemeester commented Dec 7, 2020

Note that this bump the minimum required k8s to 1.17 (https://github.com/knative/pkg/blob/release-0.19/version/version.go)

/hold

@tekton-robot tekton-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 7, 2020
@vdemeester
Copy link
Member Author

Also note that the integration test fails because of this min version, because the GKE version is v1.17.14-gke.400, which is a similar problem than #3335 (comment).

/cc @mattmoor

@vdemeester vdemeester added this to the Pipelines v0.20 milestone Dec 8, 2020
@tekton-robot tekton-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 16, 2020
@tekton-robot tekton-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 7, 2021
@vdemeester vdemeester changed the title Bump knative to release-0.19 Bump knative to release-0.20 Jan 7, 2021
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester
Copy link
Member Author

This most likely fixes #3663 too 🙃

@vdemeester
Copy link
Member Author

cc @zhouhaibing089

Do not call flag.Parse() as it happens in
`sharedmain.ParseAndGetConfigOrDie`. Move anything that needs the flag
value after that call.

This also does something with QPS and Burst flag are they are already
defined in knative/pkg *but* with different default.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester
Copy link
Member Author

/hold cancel

@tekton-robot tekton-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 7, 2021
Comment on lines +80 to +89
if cfg.QPS == 0 {
cfg.QPS = 2 * rest.DefaultQPS
}
if cfg.Burst == 0 {
cfg.Burst = rest.DefaultBurst
}
// FIXME(vdemeester): this is here to not break current behavior
// multiply by 2, no of controllers being created
cfg.QPS = 2 * float32(*qps)
cfg.Burst = 2 * *burst
cfg.QPS = 2 * cfg.QPS
cfg.Burst = 2 * cfg.Burst
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tektoncd/core-maintainers This is a bit weird but it's there to keep the same behavior as of today. Because the flag default value is defined in knative/pkg, we don't have the control over it, so we detect if the default value are passed or not. The 2 * … I am not sure about why we are doing this, but I didn't want to change the behavior here.

@bobcatfish
Copy link
Collaborator

This also fix controller flag handling 🙃

@vdemeester what flag handling does this fix?

@vdemeester
Copy link
Member Author

This also fix controller flag handling upside_down_face

@vdemeester what flag handling does this fix?

I linked the issue in comments. We do call flag.Parse before calling cfg := sharedmain.ParseAndGetConfigOrDie() which also does flag.Parse. The problem with that is… any new flag defined in knative/pkg are not parsed because we already parsed the flags before, thus, as #3663, some flags defined in knative are not handled correctly.

Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this! Let's try and get this into v0.20.0
/approve

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 7, 2021
@afrittoli
Copy link
Member

/test check-pr-has-kind-label

@afrittoli
Copy link
Member

/kind check-pr-has-kind-label

@zhouhaibing089
Copy link
Contributor

@vdemeester: Thanks for fixing the flag issue. :)

@vdemeester vdemeester added kind/misc Categorizes issue or PR as a miscellaneuous one. and removed kind/misc Categorizes issue or PR as a miscellaneuous one. labels Jan 8, 2021
@@ -142,7 +142,7 @@ func getPipelineRunController(t *testing.T, d test.Data) (test.Assets, func()) {
ctx, cancel := context.WithCancel(ctx)
ensureConfigurationConfigMapsExist(&d)
c, informers := test.SeedTestData(t, ctx, d)
configMapWatcher := configmap.NewInformedWatcher(c.Kube, system.GetNamespace())
configMapWatcher := cminformer.NewInformedWatcher(c.Kube, system.GetNamespace())
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The point of this split btw was to enable you to write tests like this for your tiny containers:
https://github.com/mattmoor/mink/blob/master/cmd/extract-digest/depcheck_test.go#L27

Not necessary for this change, but we should follow up to add checks for all the containers that should be nice and tiny.

Copy link
Member

@mattmoor mattmoor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 8, 2021
@mattmoor
Copy link
Member

mattmoor commented Jan 8, 2021

Registry 503:

Error reading blob sha256:c71a6f8e13782fed125f2247931c3eb20cc0e6428a5d79edb546f1f1405f0e49: invalid status code from registry 503 (Service Unavailable)

/retest

@mattmoor
Copy link
Member

mattmoor commented Jan 8, 2021

Looks like it maybe timing related:

message: TaskRun "workspace-in-sidecar-7ssh4" failed to finish within "1m0s"

I don't see anything else obvious in the logs, but y'all don't seem to describe the pods, which is generally pretty useful.

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants