[pull] master from kubernetes:master #838
Open
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}
The `k8s.io/utils/ptr` should be allowed for import within ./pkg/apis/core Signed-off-by: Jian Zeng <[email protected]>
daemonset registry: add unit test for UpdateStatus
kubelet: new kubelet config option for disabling group oom kill
Add plugin and key-cache for ExternalJWTSigner integration
Reusing types from the alpha in the beta made it possible to provide and use both versions without conversion. The downside was that removal of the alpha would have been harder, if not impossible. DRA drivers could continue to use the alpha types and provided the beta interface automatically. Now the two versions are completely separate gRPC APIs, although in practice there are no differences besides the name. Support for the alpha API in kubelet is provided via automatically generated conversion and manually written interface wrappers. Those are provided as part of the v1alpha4 package. The advantage of having all of that in a central place is that it'll be easier to remove when no longer needed.
Signed-off-by: Lan Liang <[email protected]>
…einghint add integration test for volumebinding for queueinghint
Fix flake in CEL cost stability tests
Signed-off-by: bzsuni <[email protected]>
This fixes an issue in
TestSchedulerPerf/SteadyStateClusterResourceClaimTemplate:
scheduler_perf.go:1542: FATAL ERROR: op 7: delete scheduled pods: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
That occurs when the test is almost done, but hasn't observed all scheduled
pods yet. The previous attempt to address this error wasn't actually 100%
correct. It covered the case when the context has already been canceled, but
not this particular "will reach deadline soon".
node-lifecycle-controller: improve processPod test-coverage
…cies-we-track Add go-spew to unwanted dependencies we track
* Add status * Add validation to check if fields are correct (Network field, device has been allocated)) * Add feature-gate * Drop field if feature-gate not set Signed-off-by: Lionel Jouin <[email protected]>
Signed-off-by: Lionel Jouin <[email protected]>
* Test feature-gate enabled/disabled for validation * Test pkg/registry/resource/resourceclaim * Add Data and NetworkData to integration test Signed-off-by: Lionel Jouin <[email protected]>
Signed-off-by: Lionel Jouin <[email protected]>
Signed-off-by: Lionel Jouin <[email protected]>
Adapat validation and tests based on these API changes Signed-off-by: Lionel Jouin <[email protected]>
Signed-off-by: Lionel Jouin <[email protected]>
* Rename HWAddress to HardwareAddress * Fix condition validation * Remove feature gate validation * Fix drop field on disabled feature gate Signed-off-by: Lionel Jouin <[email protected]>
* Add max length for InterfaceName and HardwareAddress * Prevent duplicated Addresses Signed-off-by: Lionel Jouin <[email protected]>
Signed-off-by: Lionel Jouin <[email protected]>
Signed-off-by: Lionel Jouin <[email protected]>
Addressed review comments
Fixed failing UT TestWriteKubeletConfigFiles by removing privilege check and adding proper error handling
fix: split TestCoreResourceEnqueue to deal with the timeout issue
Update metrics docs for v1.32 release(Note this must be committed after the code freeze)
After removing a pod in port-forward test we wait for an error from POST request. Since the POST doesn't have a timeout it hangs indefinitely, so instead we're hitting a DefaultPodDeletionTimeout. To make sure the POST fails this adds a timeout to ensure we'll always get that expected error, rather than nil. Signed-off-by: Maciej Szulik <[email protected]>
Add timeout for port-forward test
The "disabled by label filter" message for benchmarks printed the pointer to the filter string, not the filter string itself. This mistake gets avoided and the code becomes simpler when not using pointers.
Because Go does not a "pass" action for benchmarks (golang/go#66825 (comment)), gotestsum reports a successful benchmark run as failed (gotestyourself/gotestsum#413 (comment)). We can work around that in each benchmark and sub-benchmark by emitting the output line that `go test` expects on stdout from the test binary for success.
Pruning of tests to the top-level test was added for jobs like pull-kubernetes-unit which run many tests. For other, more focused jobs like scheduler-perf benchmarking it would be nice to keep the more detailed information, in particular because it includes the duration per test case.
…tables Signed-off-by: cpanato <[email protected]>
Vendoring changes for new hnslib v0.0.8.
skip if cri proxy is disabled/undefined
Revert "[FG:InPlacePodVerticalScaling] Graduate to Beta"
scheduler_perf: fix and enhance reporting
Previously, ValidateNodeSelector did not check that labels are valid. Now it does for resource.k8s.io, regardless whether an object already was created with invalid labels in an earlier Kubernetes release. Theoretically this is a breaking change and could cause problems during an upgrade, but that is highly unlikely in practice. In contrast to node affinity, DRA does not ignore parse errors (= uses NewNodeSelector, not NewLazyErrorNodeSelector), so invalid labels would have been found instead of being silently ignored. Even if some object has invalid labels, this only affects an alpha -> beta upgrade which isn't guaranteed to work seamlessly.
[go] Bump images, dependencies and versions to go 1.23.3 and distroless iptables
DRA API: validate node selector labels
Wait for updated keys to be observed
``` update-rules --branch release-1.32 --rules staging/publishing/rules.yaml --o staging/publishing/rules.yaml ``` Signed-off-by: Davanum Srinivas <[email protected]>
fix: mount-utils IsLikelyNotMountPoint relative path issue
…release-1.32 staging/publishing: add release-1.32 branch
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 : )