🌱 Add ClusterClass topology tests for ubuntu and bastion

[larainema]

What issue does this PR address?

Issue #2796

What does this PR do?

Adds two new non-PR-blocking ClusterClass test variants to the e2e test suite:

1. topology-ubuntu: Tests the ClusterClass with a standard ubuntu image without ignition/sysext configuration (injectIgnitionSysext: false)
2. topology-bastion: Tests the ClusterClass with a standard ubuntu image and bastion enabled (bastion.enabled: true)

These complement the existing [PR-Blocking] topology test (which uses flatcar + ignition/sysext) by exercising additional variable combinations of the dev-test ClusterClass.

Changes

• New kustomize overlays: topology-ubuntu/ and topology-bastion/
• New test file: clusterclass_test.go with two QuickStartSpec tests tagged [ClusterClass] only (not [PR-Blocking])
• New flavor constants: FlavorTopologyUbuntu and FlavorTopologyBastion
• Updated Makefile and e2e_conf.yaml to register the new templates

Why not PR-blocking?

As noted in the issue, these tests should run in the periodic/full suite only to avoid adding to PR verification time. They are tagged with [ClusterClass] but intentionally omit the [PR-Blocking] tag.

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

Name	Link
🔨 Latest commit	15dd111
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-openstack/deploys/69e0ca80c4975e00082a6a22
😎 Deploy Preview	https://deploy-preview-3121--kubernetes-sigs-cluster-api-openstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign neolit123 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @larainema. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[nikParasyr]

/ok-to-test

[lentzi90]

/test pull-cluster-api-provider-openstack-e2e-full-test

[k8s-ci-robot]

@larainema: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-openstack-e2e-full-test	15dd111	link	false	/test pull-cluster-api-provider-openstack-e2e-full-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.