You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
Currently, our e2e tests are pinned to K8s v1.22.3 version. That's because we only have v1.22.3 support in the installer. With #411 , we intend to make the installer more flexible. We should therefore move to testing higher K8s version.
Explore
Which K8s version needs to be tested and how frequently we have to update the tests can be tricky. For this, let's refer to CAPI and other providers' e2e tests to see what the current pattern of testing is. We can then make a call on which K8s version to pin to.
Anything else you would like to add:
This issue cannot be worked upon until #411 is completed. But in the meantime, it is good to do the exploration of identifying the K8s version in e2e tests.
The text was updated successfully, but these errors were encountered:
What steps did you take and what happened:
Currently, our e2e tests are pinned to K8s
v1.22.3
version. That's because we only havev1.22.3
support in the installer. With #411 , we intend to make the installer more flexible. We should therefore move to testing higher K8s version.Explore
Which K8s version needs to be tested and how frequently we have to update the tests can be tricky. For this, let's refer to CAPI and other providers' e2e tests to see what the current pattern of testing is. We can then make a call on which K8s version to pin to.
Anything else you would like to add:
This issue cannot be worked upon until #411 is completed. But in the meantime, it is good to do the exploration of identifying the K8s version in e2e tests.
The text was updated successfully, but these errors were encountered: