rotate-kubeconfig integration tests breaks later tests #322
Labels
area/testing
Testing related
kind/bug
Bug
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
priority/3
Priority (lower number equals higher priority)
How to categorize this issue?
/area testing
/kind bug
/priority normal
What happened:
When promoting the integration test
should rotate kubeconfig for a shoot cluster
in gardener/gardener#3300 from beta to default, we missed to understand that this tests will "invalidate" the kubeconfigs used by subsequent tests.The attempt to overcome this with gardener/gardener#3326 unfortunately doesn't work, as the kubeconfigs from TestMachinery are currently not meant to be "updated" via intermediate steps, hence all tests will only get the kubeconfigs from the create-shoot step, see e.g. this generated argo task for the e2e tests:
What you expected to happen:
Maybe kubeconfigs should be allowed to be overwritten by intermediate steps.
The text was updated successfully, but these errors were encountered: