🌱 e2e: add function to create the ClusterProxy when using a secondary kind-based management cluster #10804
+12
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
When using
UseKindForManagementCluster: true
in clusterctl upgrade tests:This allows users of this test specification to define a custom function to create the ClusterProxy for the management cluster.
By that it is possible to create the default ClusterProxy, but with their own scheme and options or even create a custom ClusterProxy which has a different implementation.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
xref: kubernetes-sigs/cluster-api-provider-vsphere#3024
/area e2e-testing