Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Upgrade E2E tests #7663

Open
jakubdyszkiewicz opened this issue Sep 6, 2023 · 5 comments
Open

Upgrade E2E tests #7663

jakubdyszkiewicz opened this issue Sep 6, 2023 · 5 comments
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@jakubdyszkiewicz
Copy link
Contributor

Description

We have a basic suite of CP upgrades, but we need to do a better job of keeping CP-DP compatibility.

One idea we could adopt is to run a full E2E suite test of Kubernetes with DP version hardcoded to a minimum version that CP supports.

Of course, as we develop, some E2E tests cannot be run with old DP. In this case, we can mark those tests with a label require-upstream-dp just like we do arm-not-supported.

Those tests should be run at first only on master branch and we can figure out if we need to also run this on the branch (in case we see a lot of failures on master).

Ideally, we should also run universal and multizone tests in the same way, but we should at least start with Kube tests.
@jakubdyszkiewicz jakubdyszkiewicz added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Sep 6, 2023
@jakubdyszkiewicz jakubdyszkiewicz mentioned this issue Sep 6, 2023
Merged
6 tasks
@lahabana
Copy link
Contributor

triage: How we'd do dp version is by setting the sidecar injection image version in the help chart

@lahabana lahabana added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Sep 11, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 11, 2023
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Dec 11, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Mar 11, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label Mar 12, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jun 11, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Jun 17, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Sep 16, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lahabana @slonka @jakubdyszkiewicz @lobkovilya