Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

wzshiming and others added 30 commits April 19, 2021 10:59
Signed-off-by: Shiming Zhang <[email protected]>
…erry-pick-of-#100762-upstream-release-1.19

Automated cherry pick of kubernetes#100762: list pod list once to avoid timeout
…pick-of-#101306-upstream-release-1.19

[1.19] Automated cherry pick of kubernetes#101306: Additional CVE-2021-3121 fix
GetNode() is called in a lot of places including a hot loop in
fastStatusUpdateOnce. Having a poll in it is delaying
the kubelet /readyz status=200 report.

If a client is available attempt to wait for the sync to happen,
before starting the list watch for pods at the apiserver.
The amount of memory required to build binaries in parallel is right now
set to 40GiB. We now make this variable to be able to build artifacts in
parallel even with a lower amount of memory.

This enables SIG Release to speed-up the build time drastically in
Google Cloud Build (GCB).

Signed-off-by: Sascha Grunert <[email protected]>
…ick-of-#101084-release-1.19

Automated cherry pick of kubernetes#101084: Updating EndpointSlice validation to match Endpoints
…ck-of-#96882-upstream-release-1.19

Automated cherry pick of kubernetes#96882: Make parallel build memory threshold configurable
…pick-of-#99336-origin-release-1.19

Automated cherry pick of kubernetes#99336: pkg/kubelet: improve the node informer sync check
…pick-of-#101093-upstream-release-1.19

Automated cherry pick of kubernetes#101093: Fix `startupProbe` behaviour changed
[release-1.19] Backport SIG Node approvers to 1.19
…ck-of-#100678-upstream-release-1.19

Automated cherry pick of kubernetes#100678: apf: exempt probes /healthz /livez /readyz
…-1.19

cherry pick of kubernetes#100913: no watch endpointslice in userpace mode
…k-of-#101347-upstream-release-1.19

Automated cherry pick of kubernetes#101347: Extend pod start timeout to 5min for storage subpath
This updates the StaleSlices() method in EndpointSliceTracker to also
ensure that the tracker does not have more slices than have been
provided.

Co-Authored-By: Swetha Repakula <[email protected]>
…pick-of-#100013-upstream-release-1.19

[1.19] add duration encoder to structured logger
…-pick-of-#101235-upstream-release-1.19

Automated cherry pick of kubernetes#101235: fix: azure file namespace issue in csi translation
…y-pick-of-#100944-upstream-release-1.19

Automated cherry pick of kubernetes#100944: Ensure service deleted when the Azure resource group has been deleted
…-pick-of-#100731-upstream-release-1.19

Automated cherry pick of kubernetes#100731: Normalize share name to not include capital letters
…-of-#101763-upstream-release-1.19

Automated cherry pick of kubernetes#101763: Updating EndpointSlice controllers to avoid duplicate
@damemi damemi force-pushed the rebease-1.19.14-3 branch from 8fd3df5 to 93f2255 Compare October 4, 2021 12:48
@openshift-ci-robot
Copy link

@damemi: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

@soltysh
Copy link

soltysh commented Oct 5, 2021

Last 2 bits:

  1. you're missing this commit c085042440e UPSTREAM: <drop>: enable TCP_USER_TIMEOUT on client connections https://github.com/openshift/kubernetes/commit/c085042440e?w=1 the drop is for the next release and not 4.6, double check that with @p0lyn0mial who originally authored it
  2. you're missing hack/update-vendor.sh to pass verify

damemi and others added 6 commits October 5, 2021 12:21
@damemi damemi force-pushed the rebease-1.19.14-3 branch from 5b5c3ea to 210c32a Compare October 5, 2021 16:21
@openshift-ci-robot
Copy link

@damemi: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

@soltysh soltysh removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Oct 6, 2021
@soltysh
Copy link

soltysh commented Oct 6, 2021

/override ci/prow/verify-commits
this will never pass on k8s bump

Copy link

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm
/hold
for api team final approval

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 6, 2021
@openshift-ci
Copy link

openshift-ci bot commented Oct 6, 2021

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify-commits

In response to this:

/override ci/prow/verify-commits
this will never pass on k8s bump

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.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 6, 2021
@openshift-ci
Copy link

openshift-ci bot commented Oct 6, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damemi, soltysh

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 6, 2021
@p0lyn0mial
Copy link

you're missing this commit c085042 UPSTREAM: : enable TCP_USER_TIMEOUT on client connections c085042440e?w=1 the drop is for the next release and not 4.6, double check that with @p0lyn0mial who originally authored it

please bring back that commit, the http.ping was added in 1.20+, which means we can drop the commit in 4.7

@ingvagabund
Copy link
Member

ingvagabund commented Oct 6, 2021

@p0lyn0mial checking https://github.com/openshift/kubernetes/pull/962/commits UPSTREAM: <drop>: enable TCP_USER_TIMEOUT on client connections is there at the very bottom (https://github.com/openshift/kubernetes/pull/962/commits#:~:text=p0lyn0mial%20authored%20and%20damemi%20committed%2016,210c32a).

@sttts
Copy link

sttts commented Oct 6, 2021

Have verified those commits with 1 and 2 in the spreadsheet. Lgtm.

@soltysh
Copy link

soltysh commented Oct 6, 2021

please bring back that commit, the http.ping was added in 1.20+, which means we can drop the commit in 4.7

As Jan pointed out, it's there, I've asked Mike yesterday to bring it back. <drop> commits although misleading are tricky, and since this is only within patch version we need to keep it.

@soltysh
Copy link

soltysh commented Oct 6, 2021

Based on previous comments and approval from api team
/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 6, 2021
@jerpeter1 jerpeter1 added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 7, 2021
@openshift-merge-robot openshift-merge-robot merged commit fcff70a into openshift:release-4.6 Oct 7, 2021
@openshift-ci
Copy link

openshift-ci bot commented Oct 7, 2021

@damemi: All pull requests linked via external trackers have merged:

Bugzilla bug 2008266 has been moved to the MODIFIED state.

In response to this:

[release-4.6] Bug 2008266: Rebase 1.19.14

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.

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. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.