Retirement of Kubernetes integration jobs for unsupported Kubernetes versions

Istio is narrowing the scope of its continuous integration (CI) testing to align strictly with the supported range of Kubernetes versions. Previously, the project maintained tests for older, unsupported versions (currently 1.23 through 1.36) to ensure broader compatibility. Starting with Istio version 1.32, these legacy tests will be removed from the master branch to optimize CI infrastructure and reduce the time spent maintaining end-of-life (EOL) node images.
This shift reflects the standard 14-month support lifecycle of upstream Kubernetes releases. While the project will no longer provide automated CI validation for EOL versions, the tools used for these tests remain available to the public. Users who must maintain older environments can execute the integration suite locally using the kind tool and specific configurations retrieved from the project's commit history.

* Istio Test and Release Working Group is retiring CI integration tests for unsupported Kubernetes versions.
* The change affects Istio versions 1.32 and newer.
* The change is being implemented via test-infra PR 6048 on the master branch.
* Testing was previously conducted on Kubernetes versions 1.23 through 1.36.
* Testing will now be limited strictly to the supported Kubernetes range.
* Kubernetes minor releases are supported by upstream for approximately 14 months.
* Users requiring tests on older versions can use the integ-suite-kind.sh script locally via kind.
* Local testing requires specific node-image and kind-config values from the test-infra commit history.
* Current tested versions are listed in the Istio support status table.
* Questions are directed to the Istio Test and Release Working Group on Slack.

The strongest version of this narrative is a pragmatic resource allocation decision: removing redundant tests for dead software allows a lean engineering team to focus on the versions the vast majority of users actually employ. It is a standard "lifecycle management" move common in high-velocity open-source projects.
The paradigm here is the "Upstream Gravity" model, where the health of a downstream project (Istio) is inextricably tied to the release cadence of the upstream platform (Kubernetes). There is an unstated assumption that users can and will migrate their infrastructure at the pace of upstream support. While this is the ideal, the reality of enterprise "technical debt" often leaves users stranded on EOL versions. The cost of this transition is shifted from the maintainers to the end-users, who must now provide their own compute and labor to verify stability via local scripts.
Patterns detected: none
This echoes the broader trend of "aggressive deprecation" in the cloud-native ecosystem, which accelerates innovation but increases the operational burden on conservative organizations. The benefit is a faster, more stable CI pipeline; the cost is a loss of "safety net" validation for legacy environments.
Bridge Questions:
1. What percentage of the active user base is actually running these EOL versions?
2. If a critical vulnerability emerges that affects only EOL versions, will the lack of CI testing hinder the patching process?
3. Does this move incentivize a healthier upgrade culture, or does it simply alienate users in highly regulated industries with slow update cycles?
Counterstrike Scan: A coordinated campaign to push this narrative would frame the removal of tests as a "community-driven optimization" to mask a reduction in quality assurance or a lack of resources. The actual content does not match this; it is a transparent technical announcement providing a clear path for users to replicate the tests themselves.