Add a QuickStart e2e with cluster class

[deepakm-ntnx]

What this PR does / why we need it:

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 #

How Has This Been Tested?:

git push origin HEAD:quickstart-clusterclass

When following the Cluster API quick-start with ClusterClass Should create a workload cluster [quickstart2, capx-feature-test]
/Users/deepak.muley/go/src/github.com/kubernetes-sigs/cluster-api/test/e2e/quick_start.go:78
  STEP: Creating a namespace for hosting the "quick-start" test spec @ 01/24/24 15:15:32.709
  INFO: Creating namespace quick-start-mcxuvt
  INFO: Creating event watcher for namespace "quick-start-mcxuvt"
  STEP: Creating a workload cluster @ 01/24/24 15:15:32.76
  INFO: Creating the workload cluster with name "quick-start-q2yn0a" using the "topology" template (Kubernetes v1.27.9, 1 control-plane machines, 1 worker machines)
  INFO: Getting the cluster template yaml
  INFO: clusterctl config cluster quick-start-q2yn0a --infrastructure (default) --kubernetes-version v1.27.9 --control-plane-machine-count 1 --worker-machine-count 1 --flavor topology
  INFO: Applying the cluster template yaml to the cluster
configmap/quick-start-q2yn0a-pc-trusted-ca-bundle created
configmap/nutanix-ccm created
secret/quick-start-q2yn0a created
secret/nutanix-ccm-secret created
clusterresourceset.addons.cluster.x-k8s.io/nutanix-ccm-crs created
kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/quick-start-q2yn0a-kcfg-0 created
clusterclass.cluster.x-k8s.io/e2e created
kubeadmcontrolplanetemplate.controlplane.cluster.x-k8s.io/e2e-kcpt created
nutanixclustertemplate.infrastructure.cluster.x-k8s.io/e2e-nct created
nutanixmachinetemplate.infrastructure.cluster.x-k8s.io/e2e-cp-nmt created
nutanixmachinetemplate.infrastructure.cluster.x-k8s.io/e2e-md-nmt created
configmap/cni-quick-start-q2yn0a-crs-cni created
clusterresourceset.addons.cluster.x-k8s.io/quick-start-q2yn0a-crs-cni created
cluster.cluster.x-k8s.io/quick-start-q2yn0a created

  INFO: Waiting for the cluster infrastructure to be provisioned
  STEP: Waiting for cluster to enter the provisioned phase @ 01/24/24 15:15:36.261
  INFO: Waiting for control plane to be initialized
  INFO: Waiting for the first control plane machine managed by quick-start-mcxuvt/quick-start-q2yn0a-r9dr6 to be provisioned
  STEP: Waiting for one control plane node to exist @ 01/24/24 15:15:46.349
  INFO: Waiting for control plane to be ready
  INFO: Waiting for control plane quick-start-mcxuvt/quick-start-q2yn0a-r9dr6 to be ready (implies underlying nodes to be ready as well)
  STEP: Waiting for the control plane to be ready @ 01/24/24 15:16:46.437
  STEP: Checking all the control plane machines are in the expected failure domains @ 01/24/24 15:16:46.441
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/24/24 15:16:46.464
  STEP: Checking all the machines controlled by quick-start-q2yn0a-md-0-xdfwp are in the "" failure domain @ 01/24/24 15:17:16.515
  INFO: Waiting for the machine pools to be provisioned
  STEP: PASSED! @ 01/24/24 15:17:16.558
  STEP: Dumping logs from the "quick-start-q2yn0a" workload cluster @ 01/24/24 15:17:16.558
Failed to get logs for Machine quick-start-q2yn0a-md-0-xdfwp-mwlt7-7sr6f, Cluster quick-start-mcxuvt/quick-start-q2yn0a: error creating container exec: Error response from daemon: No such container: quick-start-q2yn0a-md-0-xdfwp-mwlt7-7sr6f
Failed to get logs for Machine quick-start-q2yn0a-r9dr6-pw74q, Cluster quick-start-mcxuvt/quick-start-q2yn0a: error creating container exec: Error response from daemon: No such container: quick-start-q2yn0a-r9dr6-pw74q
  STEP: Dumping all the Cluster API resources in the "quick-start-mcxuvt" namespace @ 01/24/24 15:17:16.722
  STEP: Deleting cluster quick-start-mcxuvt/quick-start-q2yn0a @ 01/24/24 15:17:17.181
  STEP: Deleting cluster quick-start-q2yn0a @ 01/24/24 15:17:17.215
  INFO: Waiting for the Cluster quick-start-mcxuvt/quick-start-q2yn0a to be deleted
  STEP: Waiting for cluster quick-start-q2yn0a to be deleted @ 01/24/24 15:17:17.23
  STEP: Deleting namespace used for hosting the "quick-start" test spec @ 01/24/24 15:17:47.265
  INFO: Deleting namespace quick-start-mcxuvt
• [134.581 seconds]

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration and test output

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8c8d118) 15.21% compared to head (dc8e505) 15.21%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #371   +/-   ##
=======================================
  Coverage   15.21%   15.21%           
=======================================
  Files          18       18           
  Lines        1209     1209           
=======================================
  Hits          184      184           
  Misses       1025     1025           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[thunderboltsid]

/retest

[deepakm-ntnx]

/test e2e-capx-controller-upgrade

[dkoshkin]

As long as the e2e tests are passing in CI, this LGTM!

[thunderboltsid]

/lgtm
/approve

[nutanix-cn-prow-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepakm-ntnx, dkoshkin, thunderboltsid

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [deepakm-ntnx,thunderboltsid]

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