Kubernetes v1.14.2 cut planned Tuesday May 14

36 views
Skip to first unread message

Tim Pepper

unread,
May 6, 2019, 1:42:51 PM5/6/19
to kuberne...@googlegroups.com

Below is a draft of the generated changelog for v1.14.2. If you submitted a cherrypick, please make sure it's listed and has an accurate +release note.

If you have a pending cherrypick for v1.14.2, make sure it merges by end of day, Friday May 10. Please tag @kubernetes/patch-release-team on the GitHub issue/PR, email kubernetes-pat...@googlegroups.com, or reach out in #sig-release on Slack if your cherrypick appears to be blocked on something out of your control.

If you've already spoken to the patch release team about PRs that are not yet merged or listed below, don't worry, we're tracking them.

Release Note Preview - generated on Mon May 6 10:33:06 PDT 2019

Branch v1.14.1

Documentation

Changelog since v1.14.1

No notable changes for this release


PENDING PRs on the release-1.14 branch

PR Milestone User Date Commit Message
#77393 v1.14 @liggitt 2019-05-06 09:51 Automated cherry pick of #76675: Error when etcd3 watch finds delete event with nil prevKV
#77367 null @mansi-a 2019-05-02 16:25 Automated cherry pick of #76299: Short-circuit quota admission rejection on zero-delta
#77320 null @tallclair 2019-05-02 07:27 Automated cherry pick of #76665 upstream release 1.14
#77311 null @jingxu97 2019-05-06 10:27 Update the dynamic volume limit in GCE PD
#77249 null @qingling128 2019-05-02 12:50 Automated cherry pick of #77224: Upgrade Stackdriver Logging Agent addon image from 1.6.0 to
#77236 null @apelisse 2019-04-30 16:18 Automated cherry pick of #76969: Fix eviction dry-run
#77064 null @losipiuk 2019-05-06 10:03 Update Cluster Autoscaler to 1.14.2
#76980 null @jingxu97 2019-05-02 10:46 Fix race condition between actual and desired state in kublet volume manager
#76960 null @harsh-px 2019-05-06 10:17 Automated cherry pick of #76341: Fix concurrent map access in Portworx create volume call
#76199 null @mvladev 2019-04-05 09:43 Automated cherry pick of #75072: Check for required name parameter in dynamic client
#75695 null @misterikkit 2019-05-06 10:13 Automated cherry pick of #75486: Fix fake clientsets in metrics.k8s.io.

State of release-1.14 branch

NOT READY

Details

find_green_build: BEGIN main on tpepper-fedora-pet Mon May  6 10:33:08 PDT 2019

Checking for a valid github API token: OK
Checking required system packages: OK
Checking required PIP packages: OK
Checking/setting cloud tools: OK

Getting ci-kubernetes-integration-beta build results from GCS...
Getting ci-kubernetes-e2e-gce-cos-k8sbeta-ingress build results from GCS...
Getting ci-kubernetes-e2e-gce-cos-k8sbeta-slow build results from GCS...
Getting ci-kubernetes-build-beta build results from GCS...
Getting ci-kubernetes-bazel-test-1-14 build results from GCS...
Getting ci-kubernetes-e2e-gci-gce-scalability-beta build results from GCS...
Getting ci-kubernetes-e2e-gce-cos-k8sbeta-default build results from GCS...
Getting periodic-kubernetes-bazel-build-1-14 build results from GCS...
Getting ci-kubernetes-node-kubelet-beta build results from GCS...
Getting ci-kubernetes-gce-conformance-latest-1-14 build results from GCS...
Getting ci-kubernetes-e2e-gce-device-plugin-gpu-beta build results from GCS...
Getting ci-kubernetes-verify-beta build results from GCS...
Getting ci-kubernetes-e2e-gce-cos-k8sbeta-reboot build results from GCS...
Getting ci-kubernetes-e2e-gce-cos-k8sbeta-serial build results from GCS...
Getting ci-kubernetes-e2e-gce-cos-k8sbeta-alphafeatures build results from GCS...
Getting periodic-kubernetes-bazel-test-1-14 build results from GCS...
Getting ci-kubernetes-bazel-build-1-14 build results from GCS...

(*) Primary job (-) Secondary jobs

  Job #                                Run #   Build # Time/Status
= ==================================== =====   ======= ===========
* build-beta                           #1125446487468150785 #55     [05:05 05/06]
* (--buildversion=v1.14.2-beta.0.55+28bede9ce789b5)
- verify-beta                          --      --      FAILED
- integration-beta                     --      --      FAILED
- gce-conformance-latest-1-14          --      --      FAILED
- e2e-gce-cos-k8sbeta-default          #1125413015349366786 #55     PASSED
- e2e-gce-cos-k8sbeta-reboot           #1125437679312310274 #55     PASSED
- e2e-gce-cos-k8sbeta-serial           #1893   #50     PASSED
- e2e-gce-cos-k8sbeta-slow             #1125432396397678593 #55     PASSED
- e2e-gce-cos-k8sbeta-ingress          #1125404459514466305 #55     PASSED
- e2e-gce-cos-k8sbeta-alphafeatures    #1125426857336901632 #55     PASSED
- e2e-gce-device-plugin-gpu-beta       #1125430379084255233 #55     PASSED
- node-kubelet-beta                    #1125441454227853318 #55     PASSED
- e2e-gci-gce-scalability-beta         #1925   #31     PASSED
- bazel-build-1-14                     #1125371240530317317 #55     PASSED
- bazel-test-1-14                      #1125371240534511616 #55     PASSED
- periodic-kubernetes-bazel-build-1-14 #94     #50     PASSED
- periodic-kubernetes-bazel-test-1-14  #94     #50     PASSED


ATTENTION: The release-1.14 branch HEAD is ahead of the last good run by 2 commits.

If you want to use the head of the branch anyway,
--buildversion=v1.14.2-beta.0.53+28bede9ce789b5

find_green_build: DONE main on tpepper-fedora-pet Mon May  6 10:34:00 PDT 2019 in 52s

Hannes Hörl

unread,
May 15, 2019, 12:51:03 PM5/15/19
to Kubernetes developer/contributor discussion

Hello all!

As some of you already noticed, v1.14.2 is not there yet.

There are two reasons for that:

  • We decided to bring in a patch which bumps golang https://github.com/kubernetes/kubernetes/pull/77831 last minute. This patch fixes a scalability regression, which is why we decided to bring it in after all. After this we wanted the release to soak at least for a day — that would have postponed the release to today, 2019-05-15.
  • Today, when checking testgrid, we noticed that many of the tests actually run against the wrong version of kubernetes. This seems to be an issue that was introduced when the new test jobs for 1.15 where added and the ones for 1.11 were dropped.

People in #sig-testing are troubleshooting the issue. As soon as this is sorted out and as soon as we have a reliable test signal, we will cut the release. Realistically that will probably not be before tomorrow, 2019-05-16.

Sorry for that delay, we will keep you updated here.

Bye, Hannes


--
You received this message because you are subscribed to the Google Groups "kubernetes-dev-announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev-an...@googlegroups.com.
To post to this group, send email to kubernetes-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev-announce/20190506174235.GA24889%40tpepper-fedora-pet.ostc.vmware.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages