Skip to content

Backward and forward compatibility testing #3799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
Feb 21, 2025

Conversation

thallgren
Copy link
Member

This PR enables the integration tests to run with an traffic-manager/traffic-agent pair of a different version than the binary being tested, so that compatibility tests can be added for release candidates.

@thallgren thallgren force-pushed the thallgren/compatibility-testing branch from d4e9440 to d3053e0 Compare February 17, 2025 23:03
@thallgren thallgren force-pushed the thallgren/compatibility-testing branch from d3053e0 to 9702cb5 Compare February 18, 2025 16:50
Base automatically changed from thallgren/port-forward-stability to release/v2 February 21, 2025 03:24
thallgren and others added 11 commits February 21, 2025 13:43
The `telepresence helm install` and `telepresence helm upgrade` can now
handle a `--version` flag. When given, the corresponding Helm chart will
be downloaded from the "oci://ghcr.io/telepresenceio/telepresence-oss"
registry.

Signed-off-by: Thomas Hallgren <[email protected]>
The new `telepresence replace` may use the port identifier "all" to
signify all ports of a targeted container, and this identifier is not
recognized by versions < 2.22.0 (no support for multi-port intercepts).

Signed-off-by: Thomas Hallgren <[email protected]>
This commit also enables backward compatibility testing by allowing
the traffic-manager and agent versions to be older than the version of
the tested binary.

Signed-off-by: Thomas Hallgren <[email protected]>
The call to `telepresence uninstall` would sometimes race with pod
creation from the `telepresence intercept` call.

Signed-off-by: Thomas Hallgren <[email protected]>
Co-authored-by: Jakub Rożek <[email protected]>
Signed-off-by: Thomas Hallgren <[email protected]>
Co-authored-by: Jakub Rożek <[email protected]>
Signed-off-by: Thomas Hallgren <[email protected]>
Co-authored-by: Jakub Rożek <[email protected]>
Signed-off-by: Thomas Hallgren <[email protected]>
Let `go test` run with `-count=1` to disable caching. This is now
necessary since we run the `make check integration` target multiple
times with different environment settings to achieve the backward-
and forward compatibility tests.

Signed-off-by: Thomas Hallgren <[email protected]>
@thallgren thallgren force-pushed the thallgren/compatibility-testing branch from d774f7b to b5a57fd Compare February 21, 2025 12:43
@thallgren thallgren added the ok to test Applied by maintainers when a PR is ready to have tests run on it label Feb 21, 2025
@github-actions github-actions bot removed the ok to test Applied by maintainers when a PR is ready to have tests run on it label Feb 21, 2025
@thallgren thallgren merged commit d439fdc into release/v2 Feb 21, 2025
11 checks passed
@thallgren thallgren deleted the thallgren/compatibility-testing branch February 21, 2025 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants