chore: bump DefaultKubeBinaryVersion to 1.32, make 1.32 CEL changes, fix int tests to handle 1 version off API deprecation, and fix prerelease-lifecycle-gen for # of APIs
This leaves the old method alone, since the performance difference is so
stark.
```
$ go test ./staging/src/k8s.io/apimachinery/pkg/api/resource/ -bench=Float64
goos: linux
goarch: amd64
pkg: k8s.io/apimachinery/pkg/api/resource
cpu: Intel(R) Xeon(R) W-2135 CPU @ 3.70GHz
BenchmarkQuantityAsApproximateFloat64-6 95865672 11.44 ns/op
BenchmarkQuantityAsFloat64Slow-6 2800825 430.2 ns/op
PASS
ok k8s.io/apimachinery/pkg/api/resource 2.786s
```
* Make JobPodFailurePolicy tests for ignore resilient to random failures
* Increase parallelism and evict in parallel
* Code review fixes to the job e2e tests
The endpoints controller store the resource version of the previous
Endpoints objects to avoid issues related to stale information on the
cache.
However, there can be update operations that succeed without increasing
the resource version, causing the endpoints controller to declare stale
the existing Resource Version and stopping the Endpoints to be updated.
Co-Author-By: Quan Tian <quan.tian@broadcom.com>
Co-Author-By: Yang Yang <yyyng@amazon.com>
The LoadBalancer test "should handle updates to ExternalTrafficPolicy
field" had a bunch of problems, but the biggest is that (without doing
[Disruptive] things to the cluster or making unwarranted assumptions
about source IPs) it's very hard to *prove* that the cloud load
balancer is doing Cluster traffic policy semantics (distributing
connections to all nodes) rather than Local (distributing only to
nodes with endpoints).
So split the test into 2 new tests with more focused semantics:
- "should implement NodePort and HealthCheckNodePort correctly when
ExternalTrafficPolicy changes" (in service.go) tests that the
service proxy is correctly implementing the proxy side of
Cluster-vs-Local traffic policy for LoadBalancer Services, without
testing the cloud load balancer itself at all.
- "should target all nodes with endpoints" (in loadbalancer.go)
complements the existing "should only target nodes with
endpoints", to ensure that when a service has
`externalTrafficPolicy: Local`, and there are endpoints on
multiple nodes, that the cloud is correctly configured to target
all of those endpoints, not just one.
This improves the precision of Quantity.AsApproximateFloat64, by way of example:
decQuantity(7*1024*1024, -1, BinarySI)
Before: 734003.2000000001,
After: 734003.2
Co-Authored-By: Bo Sunesen <7479047+bosunesen@users.noreply.github.com>
Kubernetes e2e suite: [It] [sig-node] Variable Expansion should fail
substituting values in a volume subpath with absolute path [Slow]
[Conformance] test takes 37 seconds to run
