[pull] master from kubernetes:master #838
Open
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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Signed-off-by: joshjms <[email protected]>
refactor: Stop using ioutil in apiserver
refactor: Use http method constants in apimachinery
Rewrite the cpumanager tests to make use of the lessons learned, more modern idioms, remove obsolete assumptions and in gneeral remove all the legacy which was accumulating over the years. The goal is to have a simpler, flatter and more maintenable code layout, de-entangle the net of dependency, making the tests more robust and easier to extend. In short, this is all about maintainability. All the testcases will be preserved, and few other can be added along the way. Comments in the code will explain the code layout decisions and tradeoff, and provide a good guide to add more tests in the future. Special care was added in order to maximize the isolation between tests, at cost, in selected cases of a controlled and planned code duplication. Signed-off-by: Francesco Romani <[email protected]>
rewrite the cpumanager e2e tests for the `strict-cpu-reservation` policy option to fit into the new layout. All testcases are preserved. Signed-off-by: Francesco Romani <[email protected]>
Rewrite the e2e cpumanager tests about CFS quota management. All testcases are preserved. Signed-off-by: Francesco Romani <[email protected]>
Rewrite the policy option compatibility tests. We start with the tests which check the compatibility between the `full-pcpus-only` and `strict-cpu-reservation` tests, because the former is the only GA option at time of writing. All testcases are preserved. Signed-off-by: Francesco Romani <[email protected]>
Complete the rewrite the policy option compatibility tests, rewriting the tests which check compatibility between the `full-pcpus-only` and `distribute-cpus-across-numa`. All testcases are preserved. Signed-off-by: Francesco Romani <[email protected]>
We have tests which cover the case on which a pod with a single container require multiple CPUs; rewrite them preserving the testcases and actually adding coverage. Add and use stricter checks along the way. Signed-off-by: Francesco Romani <[email protected]>
rewrite tests which exercise multiple container within the same pod. Preserve the existing testcases, add more. Note basic coverage for mixed pods - some containers requiring exclusive CPUs, some not, was already added with the initial batch. Signed-off-by: Francesco Romani <[email protected]>
rewrite tests which check with multiple pods. We may extend the coverage later on. Signed-off-by: Francesco Romani <[email protected]>
Let's have a single general comment instead of copypasting the same text all around the tests. Signed-off-by: Francesco Romani <[email protected]>
reuse existing building blocks at the cost of a tiny, non-nested BeforeEach (which is still OK) and some targeted duplication. Signed-off-by: Francesco Romani <[email protected]>
now that we have a minimal BeforeEach (and let's keep it this way) we can factor out the reservedCPUs setting, since it's the same code for each testcase. Signed-off-by: Francesco Romani <[email protected]>
rewrite the tests porting to the new layout and utilities. We may add more cases and better integration in the future. Signed-off-by: Francesco Romani <[email protected]>
We only need one special "DynamicResourceAllocation" feature for the optional node support of DRA (plugin registration, CDI support in the container runtime). For individual features, the automatic labeling through WithFeatureGate is sufficient. To find DRA-related tests in a label filter, instead of plain-text "DRA" a "DRA" label now gets added. This change depends on an update of the DRA jobs.
test: Pass test context to http requests
DRA: E2E test flake and failure fixes
Fix broken recursion in validation-gen
Build etcd v3.6.0-rc.5 image
Signed-off-by: Davanum Srinivas <[email protected]> Co-Authored-By: Jordan Liggitt <[email protected]> Set event level during context init Signed-off-by: Davanum Srinivas <[email protected]>
Add hpa reviewers
Move test cases from mounted_volume_resize into testsuites/volume_expand.go
…MetricReplicas-intmax HPA: Fix int overflow in GetExternalPerPodMetricReplicas
e2e: node: rewrite cpumanager tests
This PR fixes a possible panic caused by decoding a JSON document followed by a YAML document that is shorter than the first json document. This can cause a panic because the stream already consumed the JSON data. When we fallback to YAML reader, the YAML starts with a zero offset while the stream consumed data is non-zero. This could lead into consuming negative bytes because `d.yaml.InputOffset() - d.stream.Consumed()` is negative which will cause a panic. Signed-off-by: Tiago Silva <[email protected]>
- Close response body after http calls in the watch tests - Add apitesting utility methods for closing and testing errors from response body and websocket. - Validate read after close errors.
docs: avoid broken link
…ment cleanup: remove error comment of AddIndexers func
Duplicate v1beta1 AuthenticationConfiguration to v1
Recently in PR 131741 the kubeadm fixture for cluster-info in dryrun.go was updated to remove the 'preferences' struct. This means that the hardcoded JWS signature of the cluster-info fixture must also be updated. Update the signature to the expected one to fix e2e failures in dryrun-latest. https://testgrid.k8s.io/sig-cluster-lifecycle-kubeadm#kubeadm-kinder-dryrun-latest
hack/pin-dependency.sh github.com/vishvananda/netlink v1.3.1 hack/update-vendor.sh
update baseimage for agnhost
kubeadm: fix dryrun-latest e2e by updating cluster-info fixture
Bump github.com/vishvananda/netlink to v1.3.1
…alls Remove superflous expansion calls if controller finished expansion
…rs-to-v1.10.0 vendor: update system-validators to v1.10.0
e2e: add corresponding featuregate label to node features
fix(kubelet): update lease duration when config changes
renamed SIG Node google groups
Unify references to group resource in metrics
…reboot test (#131699) * Fix test flakiness caused by shadowed error in reboot test and stale pods affecting eviction test - Fixed a bug in `ExecCommandInContainerWithFullOutput` usage in `hybrid_network.go` where the `err` variable was shadowed, causing test failures to be silently ignored. - Added cleanup logic in `eviction.go` to explicitly delete pods created by the reboot node test (e.g., `img-puller`, `reboot-host-test-windows`) before starting the eviction test. - This improves reliability of the eviction test when the reboot test runs beforehand and leaves behind memory-consuming pods. * Add cleanup containers in reboot node test * Workaround for Calico HNS issue by avoiding eviction of undeletable pods Add a workaround for a known Calico issue (projectcalico/calico#6974) where pods on Windows nodes may become undeletable after a reboot. This causes the eviction manager to attempt evicting these pods but fail due to HNS namespace deletion errors. The workaround avoids scheduling critical test pods on rebooted nodes to prevent interference. TODO: Remove this workaround once the Calico issue is resolved. * Fix the lint issue. * Address comments
DRA E2E: reduce risk of flake in ResourceSlice stress test
…ctionType.None public
…ns: NodeAffinity plugin Signed-off-by: googs1025 <[email protected]>
The TODO was resolved and the "seamless update" PR merged already in 1.33. The updated guidance in NodeUnprepareResources is meant to emphasize existing practice.
chore(scheduler): add filter integration tests for missing part plugins: NodeAffinity plugin
…g_action_type Remove package protected fields from ActionType
…ss iptables Signed-off-by: Carlos Panato <[email protected]>
…rs-to-v1.10.1 vendor: update system-validators to v1.10.1
DRA kubeletplugin: some doc updates
Add metrics for compatibility version
[go] Bump dependencies, images and versions used to Go 1.24.3 and distroless iptables
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 : )