[pull] master from kubernetes:master #838
Open
+682,020
−554,060
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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Add a static NodePort allocator for e2e tests
kubeadm: remove preflight check for nsenter on Linux nodes Signed-off-by: carlory <[email protected]>
This change makes us use the generic btree available in newer versions of github.com/google/btree. This avoids a bunch of type assertions and makes the code easier to read.
Use generic btree in watchcache
Add crd from external snapshotter
…icate optional Secret/ConfigMap (#129457) * kubectl: enhance output for projected volume sources to indicate optional secrets * .
…lue (#129017) * Add validation for revisionHistoryLimit in sts to prevent negative value * Add unit tests to verify warning messages
Bump x/net to v0.33.0
[go1.24] webhook: alter regex to account for x509sha1 GODEBUG removal
…bhookConfigurations-retry [e2e][webhook] Retry update ValidatingWebhookConfigurations
kubeadm: should not warn on non-detect sandbox image
…ation-testing Job: Remove JobTrackingFinalizer annotation specific testings
Remove general available feature-gate PDBUnhealthyPodEvictionPolicy
…date updated bootstrap-discovery link
…ponse Extract list response struct to manage all the response fields
refactor: simplify boolean expressions in CRD handler
Signed-off-by: Davanum Srinivas <[email protected]>
Signed-off-by: bzsuni <[email protected]>
test: fix pv deletion timeout
e2e: deflake volume tests
By passing the context, if available, down into the actual wait loop it becomes possible to use contextual logging when handling a crash. That then logs more information about which component encountered the problem (WithName e.g. in kube-controller-manager) and what it was doing at the time (WithValues e.g. in kube-scheduler).
Only the v1 API should be in use. The v1beta1 API therefore doesn't get updated and doesn't need the context.TODO anymore.
This was previously used by some autoscaling tests that have since been removed. It is somewhat sketchy (and inherently [Disruptive]), and depends on iptables (so would need to be updated to use nftables at some point if we were keeping it). Given that it's now unused, just remove it (as well as some helper functions that are no longer used by anyone else as well).
kube-proxy does not look at Endpoints ever, so it is incorrect for a test to assume that there is any correlation between whether Endpoints exist and whether a Service is working. Tests should only be using the v1.Endpoints API if they are explicitly testing the behavior of v1.Endpoints, the Endpoints controller, or the EndpointSlice mirroring controller. There is no reason for any non SIG Network tests to be testing any of those things, so there should be no references to v1.Endpoints in test/e2e outside of test/e2e/network. Also, simplify some pointlessly complicated e2eservice code.
Remove all references to v1.Endpoints from non-network e2e tests
…_when_adding_pod_to_nodeinfo Use cached calculateResource result when removing pod from NodeInfo in preemption
Signed-off-by: Davanum Srinivas <[email protected]>
Signed-off-by: carlory <[email protected]>
Move some exec helper functions from framework/volume to framework/pod
Self-nominating ffromani as approver for sig-node container and resource managers
testing: Fix pod delete timeout failures after InPlacePodVerticalScaling Graduate to Beta commit
Kubelet server handler cleanup
Nominate macsko to SIG Scheduling approvers
The default handler now uses contextual logging. Instead of
warnings.go:106] warning 1
it now logs the caller of client-go and uses structured, contextual
logging
main.go:100] "Warning" message="warning 1"
Users of client-go have the choice whether the handler that they provide uses
the traditional API (no API break!) or contextual logging.
The BackoffManager interface sleeps without considering the caller's context, i.e. cancellation is not supported. This alone is reason enough to deprecate it and to replace it with an interface that supports a context parameter. The other reason is that contextual logging needs that parameter.
The remaining calls can be converted without API changes.
Storing a context and making sure that it never gets canceled also has overhead. We might as well just do the klog.FromContext when constructing the Result and store the logger for later use.
…#129658) * adding support for providing version for functions in kube_codegen.sh * addressed review comments * addressed review comments
kubeadm: fix a wrong log message
Fix dual stack tests after moving the e2e test to use Endpoint Slices
tests: include stdout of failed commands in JUnit
client-go/rest: finish context support
KEP-1880 Multiple Service CIDRs: Graduate to GA
Signed-off-by: Davanum Srinivas <[email protected]>
…jose/go-jose.v2 Switch to gopkg.in/go-jose/go-jose.v2 @ v2.6.3 and github.com/coreos/go-oidc @ v2.3.0
Revert "tests: include stdout of failed commands in JUnit"
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )