-
Notifications
You must be signed in to change notification settings - Fork 16
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
test: check migration to v3 controller #585
base: main
Are you sure you want to change the base?
Conversation
@salasberryfin can we rebase this PR? |
0d0630e
to
6de42e7
Compare
@salasberryfin Can you please rebase this PR? |
19c32e2
to
a5dc55d
Compare
Does this need a rebase again? |
This was rebased today but it is still failing when trying to connect to the downstream cluster after migration using kubeconfig. Still figuring out the reason behind this. |
Signed-off-by: Alexandr Demicev <alexandr.demicev@suse.com> Signed-off-by: Carlos Salas <carlos.salas@suse.com>
a5dc55d
to
6fbc69e
Compare
@salasberryfin The problem you are facing might be fixed by 7653a81#diff-7be87c7e06c4b33e0c43cce272e500934fca8631072faf36237af336d4c1c562R185-R190 |
Signed-off-by: Carlos Salas <carlos.salas@suse.com>
6fbc69e
to
5f93e2e
Compare
What this PR does / why we need it:
We decided to split into a separate PR the E2E tests added to validate v1 to v3 controller migration. The changes to the controller can be found in #575. This PR only affects E2E scenarios.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist: