Repository navigation
Version skew testing #519
Description
As we make changes to Konnectivity, it is important that the newer components remain compatible with older components so that the system continues to function during upgrades and other version skew scenarios. However, we currently have no visibility into this. We should add tests that run against skewed versions.
Specifically, we need to test version skew across client/server, and agent/server. I propose we update the tests in the tests directory to run against skewed versions.
Implementation steps:
- 1. Refactor integration tests to prepare for proxy-server & agent skew testing #520
- 2. Implement External{ProxyServer,Agent}Runner, which takes an external binary to run for the server/agent, and accesses the measurements through prometheus metrics. Expose test flags to select a binary (or the in-tree version).
- 3. Implement a version_skew_test script that handles fetching target tagged versions, compiling, and running the tests.
- 4. Set up CI jobs for skew testing
- 5. Refactor client operations to enable external client testing via the test-client binary.
- 6. Implement ExternalClient, update version_skew_test to run tests with the external client
/assign
Activity
jkh52 commentedon Jan 11, 2024
#553 (github actions using
kind) could be an approach here for how to specify the versions under test. (Similar to that, but use real container image registry + version tags).k8s-triage-robot commentedon Apr 10, 2024
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
tallclair commentedon Apr 24, 2024
/triage accepted
/remove-lifecycle stale
k8s-triage-robot commentedon Apr 24, 2025
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted(org members only)/closeFor more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
tallclair commentedon Apr 25, 2025
The foundation is in place, but we still need to wire it up. Version skew testing is still needed, and will make it much safer to make protocol changes.
/triage accepted
k8s-triage-robot commentedon Apr 25, 2026
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted(org members only)/closeFor more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
k8s-triage-robot commentedon Oct 17, 2026
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale