Bump to k8s 1.26.2 #1494
Merged
Bump to k8s 1.26.2 #1494
Conversation
This file contains hidden or 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
sanchezl
commented
Mar 1, 2023
sanchezl
commented
- Limit request retrying to []byte request bodies
- Introducing LoadbalancerPortMapping flags for VipExternalIP
- Release commit for Kubernetes v1.26.1-rc.0
- Update CHANGELOG/CHANGELOG-1.26.md for v1.26.0
- Check the correct error in d.downloadAPIs
- Deflake a preemption test that may patch Node incorrectly
- Creating Ingress IP loadbalancer alone when all the endpoints are terminating. KEP1669
- Reduce load of Job integration test
- fix double lock and excercise its codepath in tests
- Improve error message when proxy connection fails
- Fix SPDY proxy authentication with special chars
- Fix a regression that scheduler always go through all Filter plugins
- Windows Kube-Proxy implementation for internal traffic policy.
- Resource claims should be a map type
- Add .go-version file containing build go version
- Add pod to dsw if termination is not completed during reconstruction #issues/113979
- Fix clearing rate limiter in disruption controller
- Fix issues in volumesnapshot test for ephemeral storage
- Licensing: skip modules with fewer subdirs than mods
- Update daemonSet status even if syncDaemonSet fails
- Automated cherry pick of Removed the reverted changes from Changelogv1.26.md kubernetes/kubernetes#114602: Removed the reverted changes from Changelogv1.26.md
- Cherry pick 114857 to release-1.26
- Bump konnectivity-client to v0.0.35
- expose prometheus.Registerer so that we can hook into this from external sources
- egress_selector.go: register konnectivity-client metrics.
- Adjust DisruptionTarget condition message to do not include preemptor pod metadata
- Do not leak cross namespace pod metadata in preemption events
- Improve vendor verification works for each staging repo
- Exports WarningPrinter field in DeleteOptions
- Explicitly call rand.Seed() method
- Do not include scheduler name in the preemption event message
- releng: Update images, dependencies and version to Go 1.19.5
- pkg/controller/job: re-honor exponential backoff
- PodGC should not add DisruptionTarget condition for pods which are in terminal phase
- Fixes the issue [Flaky test] Tests in vendor/k8s.io/apiserver/pkg/server/genericapiserver_graceful_termination_test.go are flaking kubernetes/kubernetes#114145
- Release commit for Kubernetes v1.26.1
- Release commit for Kubernetes v1.26.2-rc.0
- Update CHANGELOG/CHANGELOG-1.26.md for v1.26.1
- bump honnef.co/go/tools to support go1.20
- Fix shadowing lint error
- fix bug with param controllers being removed if used by more than one policy
- k8s.io/component-base/logs: fix usage through Go flag package
- k8s.io/component-base/logs: unit test for command line help output
- k8s.io/component-base/logs: relax flagset unit tests
- k8s.io/component-base/logs: match full help text in unit test
- add custom dialer optimized for probes
- use custom dialer for tcp probes
- use custom dialer for http probes
- Fix panic on ClusterIP allocation for /28 subnets
- kubectl: use v2 for hpa
- add scale test for probes
- Fix nil pointer error in nodevolumelimits csi logging
- Fix konnectivity-client metric registration.
- Avoid typechecking stdlib
- dynamic resource allocation: avoid apiserver complaint about list content
- update prev succeeded indexes for indexed jobs unconditionally
- apiserver: remove 34s from DELETECOLLECTION rest handler
- Ignore container events with nil PodSandboxStatus
- kubelet/client: collapse transport wiring onto standard approach
- hack/tools: Bump golangci-lint version
- *: Fix linter warnings
- Enforce nodeName cannot be set along with non empty schedulingGates
- Pin golang.org/x/net to v0.4.0 in 1.26
- Update golang.org/x/net to v0.7.0
- releng: Update images, dependencies and version to Go 1.19.6
- Release commit for Kubernetes v1.26.2
- Revert "UPSTREAM: 114770: Fix clearing rate limiter in disruption controller"
- UPSTREAM: : hack/update-vendor.sh, make update and update image
…d-cherry-pick-of-#114940-upstream-release-1.26 Automated cherry pick of kubernetes#114940: Fixes the issue kubernetes#114145
api/v1.AddFlags only supports a pflag.FlagSet. The assumption was that code
which wants to use flag.FlagSet can use VisitAll to copy the flags. That works,
with one caveat: the flag.FlagSet help implementation will call String for the
zero value to determine whether the flag has a non-default value. This
currently leads to additional warnings at the end of the -help output:
panic calling String method on zero v1.verbosityLevelPflag for flag v: runtime error: invalid memory address or nil pointer dereference
panic calling String method on zero v1.vmoduleConfigurationPFlag for flag vmodule: runtime error: invalid memory address or nil pointer dereference
Supporting usage of methods with the zero value is good practice anyway and
thus gets added. This then avoids these panics.
Both pflag and standard FlagSet are covered.
A full string comparison might fail when the underlying libraries change how they format the help text. A regex match is less strict, but still makes some assumptions about the implementation.
The test was meant to fail when there are unexpected additional lines like the "panic calling String method" messages. But `assert.Regexp` does a search for the regexp, not a full string match, and thus succeeded even if those lines are present. A full match needs to be requested explicitly with ^ and $.
…ck-of-#115129-upstream-release-1.26 Automated cherry pick of kubernetes#115129: bump honnef.co/go/tools to support go1.20
probe util dial set linger to 1s
Change-Id: I323b472606eaf3242b665022afe2a79ecf3b8358
The ClusterIP allocator tries to reserve on part of the ServiceCIDR to allocate static IPs to the Services. The heuristic of the allocator to obtain the offset was taking into account the whole range size, not the IPs available in the range, the subnet address and the broadcast address for IPv4 are not available. This caused that for CIDRs with 16 hosts, /28 for IPv4 and /124 for IPv6, the offset calculated was higher than the max number of available addresses on the allocator, causing this to panic. Change-Id: I6c6f527b0a600b3612be37769e405b8fb3dd33a8
Signed-off-by: Amir Alavi <[email protected]>
Change-Id: I1e49943531b569b5e02f82369750a9ca899ae726
…-of-#115322-upstream-release-1.26 Automated cherry pick of kubernetes#115322: Fix panic on ClusterIP allocation for /28 subnets
…k-of-#115056-upstream-release-1.26 Automated cherry pick of kubernetes#115056: PodGC should not add DisruptionTarget condition for pods
…herry-pick-of-#115143-upstream-release-1.26 Automated cherry pick of kubernetes#115143: add custom dialer optimized for probes
…tent This fixes the following warning (error?) in the apiserver: E0126 18:10:38.665239 16370 fieldmanager.go:210] "[SHOULD NOT HAPPEN] failed to update managedFields" err="failed to convert new object (test/claim-84; resource.k8s.io/v1alpha1, Kind=ResourceClaim) to smd typed: .status.reservedFor: element 0: associative list without keys has an element that's a map type" VersionKind="/, Kind=" namespace="test" name="claim-84" The root cause is the same as in e50e8a0: nothing in Kubernetes outright complains about a list of items where the item type is comparable in Go, but not a simple type. This nonetheless isn't supposed to be done in the API and can causes problems elsewhere. For the ReservedFor field, everything seems to work okay except for the warning. However, it's better to follow conventions and use a map. This is possible in this case because UID is guaranteed to be a unique key. Validation is now stricter than before, which is a good thing: previously, two entries with the same UID were allowed as long as some other field was different, which wasn't a situation that should have been allowed.
…ck-of-#115382-upstream-release-1.26 Automated cherry pick of kubernetes#115382: Avoid typechecking stdlib
Signed-off-by: ruiwen-zhao <[email protected]>
soltysh
approved these changes
Mar 2, 2023
|
/override ci/prow/verify-commits |
openshift-ci
bot
added
backports/validated-commits
|
/retest-required |
|
/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. |
|
@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: sanchezl, 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 |
openshift-ci
bot
added
the
approved
|
/override ci/prow/verify-commits |
|
/test e2e-aws-ovn-cgroupsv2 |
|
@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. |
|
@sanchezl: 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. |
|
/cherry-pick release-4.13 |
|
@sanchezl: #1494 failed to apply on top of branch "release-4.13": 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.