f2bd94a0de
1. Core Kubelet changes to implement In-place Pod Vertical Scaling. 2. E2E tests for In-place Pod Vertical Scaling. 3. Refactor kubelet code and add missing tests (Derek's kubelet review) 4. Add a new hash over container fields without Resources field to allow feature gate toggling without restarting containers not using the feature. 5. Fix corner-case where resize A->B->A gets ignored 6. Add cgroup v2 support to pod resize E2E test. KEP: /enhancements/keps/sig-node/1287-in-place-update-pod-resources Co-authored-by: Chen Wang <Chen.Wang1@ibm.com> |
||
|---|---|---|
| .. | ||
| apparmor.go | ||
| crictl.go | ||
| events.go | ||
| examples.go | ||
| framework.go | ||
| kubelet_perf.go | ||
| kubelet.go | ||
| mount_propagation.go | ||
| node_problem_detector.go | ||
| OWNERS | ||
| pod_gc.go | ||
| pod_resize.go | ||
| pods.go | ||
| pre_stop.go | ||
| README.md | ||
| runtimeclass.go | ||
| security_context.go | ||
| ssh.go | ||
| taints.go | ||
WARNING: Do not add tests in this directory
There are two types of end-to-end tests in Kubernetes:
Tests located in ${KUBE_ROOT}/test/e2e/common are shared by both Cluster
and Node E2E test jobs. Tests in ${KUBE_ROOT}/test/e2e_node are exclusively
owned by Node E2E. If you want to add a test, most likely than not, you want
to add the test to one of the two directories mentioned above. If you are
unsure, please check with the OWNER of the directory. This directory currently
contains misplaced and legacy tests; they will be cleaned up in the future.