Open jakubdyszkiewicz opened 1 year ago
triage: How we'd do dp version is by setting the sidecar injection image version in the help chart
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.
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.
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.
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.
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 doarm-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 onmaster
).Ideally, we should also run universal and multizone tests in the same way, but we should at least start with Kube tests.