[e2e tests] Add CNIManifestPath and namespaces as inputs to ClusterctlUpgradeSpec

[mboukhalfa]

User Story

In order to reuse ClusterctlUpgradeSpec with CAPM3 we might need the possibility to set clusters namespace and CNIManifestPath in ClusterctlUpgradeSpecInput.

Detailed Description

CAPM3 provider requires BMH CRs available in the same namespace before creating the cluster. However, since the ClusterctlUpgradeSpec creates dynamic and random namespaces without giving any option to reuse an existing namespace CAPM3 cannot set the those BMH before creating the cluster.

Would be great for the test portability if we can have the possibility to input the namespaces for both management and workload clusters, and setting CNIManifestPath.

/kind feature

[fabriziopandini]

/area testing
/milestone v1.2

[fabriziopandini]

CAPM3 provider requires BMH CRs available in the same namespace before creating the cluster. However, since the ClusterctlUpgradeSpec creates dynamic and random namespaces without giving any option to reuse an existing namespace CAPM3 cannot set the those BMH before creating the cluster.

I would prefer to keep the current behavior of the test being created in a random namespace because this helps in running different tests (including variations of the same test) in isolation.

I would suggest a different approach instead. Why not explore/extend the usage of hooks allowing you to add your custom resources? Please note that this approach is already used by other providers and we already have PreInit, PreUpgrade, PostUpgrade

... and setting CNIManifestPath.

This is already possible using the CNI variable

[fabriziopandini]

/triage accepted