OCPBUGS-15246: Bump to k8s 1.26.6 #1610
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumping version to include changes that better handle TLS errors. Bump nescessary to prepare for when the version of Go is bumped to 1.20 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Modify unwrap error utility to make it work with go1.20 This version of Go introduces a new layer of wrapping via a new error type. The commit accounts for that while being compatible with go1.19 Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com>
If the etcd member is not found, then it has already been removed, and kubeadm reset should immediately complete the 'remove-etcd-member' phase. Previously, the phase would complete only once the exponential-backoff retry expired, up to 3 minutes duration. This commit also fixes a semantic error in etcd.GetMemberID. Previously, the function returned 0 if no member was found, but 0 is not a valid member ID.
…consistent with kubelet
…ck-of-#118104-upstream-release-1.26 Automated cherry pick of kubernetes#118104: Fix waiting for CRD sync at server start
…ck-of-#118069-upstream-release-1.26 Automated cherry pick of kubernetes#118069: kubeadm: fix a bug where the static pod changes detection
[1.26] Cherry Pick of kubernetes#114766: [Prepare for go1.20] *: Bump versions and fix tests
…-pick-of-#118156-upstream-release-1.26 Automated cherry pick of kubernetes#118156: update webhook test to go 1.21
Manually modified the commit to expect Failed phase instead of Succeeded. This is expected in 1.26 as the code in preemption.go sets it to Failed. In 1.27 the phase is determined by `getPhase` kubelet_pods.go based on the completed containers.
…k-of-#117586-upstream-release-1.26 Automated cherry pick of kubernetes#117586: Add DisruptionTarget condition when preempting for critical
Signed-off-by: Rita Zhang <rita.z.zhang@gmail.com>
…y-pick-of-#117792-kubernetes#117724-upstream-release-1.26 Automated cherry pick of kubernetes#117792: kubeadm: Use internal etcd client through an interface kubernetes#117724: kubeadm: Make etcd member removal idempotent
Since kube-proxy in LocalModeNodeCIDR needs to obtain the PodCIDR assigned to the node it watches for the Node object. However, kube-proxy startup process requires to have these watches in different places, that opens the possibility of having a race condition if the same node is recreated and a different PodCIDR is assigned. Initializing the second watch with the value obtained in the first one allows us to detect this situation. Change-Id: I6adeedb6914ad2afd3e0694dcab619c2a66135f8 Signed-off-by: Antonio Ojea <aojea@google.com>
…k-of-#118356-upstream-release-1.26 Automated cherry pick of kubernetes#118356: Add ephemeralcontainer to imagepolicy securityaccount
…-of-#118515-upstream-release-1.26 Automated cherry pick of kubernetes#118515: kube-proxy avoid race condition using LocalModeNodeCIDR
…Go 1.19.10 Bump release-1.26 to go 1.19.10 Signed-off-by: Adolfo García Veytia (Puerco) <adolfo.garcia@uservers.net>
Run of ./hack/update-vendor.sh Signed-off-by: Adolfo García Veytia (Puerco) <adolfo.garcia@uservers.net>
[release-1.26] releng/go: Update images, deps and version to go 1.19.10
openshift-ci-robot
added
the
backports/unvalidated-commits
|
@soltysh: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
|
@soltysh: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
|
/remove-label backports/unvalidated-commits Since #1609 merge this is good to go /label backport-risk-assessed |
openshift-ci
bot
added
backports/validated-commits
openshift-ci
bot
assigned duanwei33, gangwgr, kasturinarra, sunilcio, wangke19, xingxingxia and zhouying7780
openshift-ci
bot
removed
the
jira/invalid-bug
|
@soltysh: Those labels are not set on the issue: In response to this:
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. |
|
/label cherry-pick-approved |
openshift-ci
bot
added
the
cherry-pick-approved
|
/override ci/prow/verify-commits |
|
@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify-commits In response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bertinatto, soltysh, stlaz 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 |
|
/test e2e-aws-ovn-serial |
|
@soltysh: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
/label jira/valid-bug |
openshift-ci
bot
added
the
jira/valid-bug
openshift-merge-robot
merged commit a7ee68b
into
openshift:release-4.13
22 checks passed
|
@soltysh: Jira Issue OCPBUGS-15246: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-15246 has been moved to the MODIFIED state. In response to this: 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.