Recent runs || View in Spyglass
PR | cpanato: update ginko to v2, CAPI to 1.3.x, go to 1.19 and certmanager to v1.10.0 |
Result | SUCCESS |
Tests | 0 failed / 8 succeeded |
Started | |
Elapsed | 20m3s |
Revision | 080d015750cb79b0c75841ea53edbce7468c3fa0 |
Refs |
766 |
capg-e2e [It] Workload cluster creation Creating a highly available control-plane cluster Should create a cluster with 3 control-plane and 2 worker nodes
capg-e2e [It] Workload cluster creation Creating a single control-plane cluster Should create a cluster with 1 worker node and can be scaled
capg-e2e [SynchronizedAfterSuite]
capg-e2e [SynchronizedAfterSuite]
capg-e2e [SynchronizedAfterSuite]
capg-e2e [SynchronizedBeforeSuite]
capg-e2e [SynchronizedBeforeSuite]
capg-e2e [SynchronizedBeforeSuite]
capg-e2e [It] Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capg-e2e [It] Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capg-e2e [It] Running the Cluster API E2E tests Running the quick-start spec with ClusterClass Should create a workload cluster
capg-e2e [It] Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capg-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capg-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation