### Test report for 4081.3.12 / arm64

**Platforms tested** : aws 

🟢 ok **cl.cloudinit.basic**; Succeeded: aws (5); Failed: aws (1, 2, 3, 4)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: ad32d0e7-121a-43fa-85f2-71dd7f049eec_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 9f52b04a-56ca-48ec-8602-d41177037bea_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 5b844a15-f1ca-424f-9b7b-e75d12416248_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 20c9996e-793e-4c69-a28b-a38747584165_"
      L3: " "
  ```


</details>


❌ not ok **cl.etcd-member.discovery**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: b29a7b47-0f82-434c-ba54-407043dd96e4_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: c55b3905-26af-4219-b528-7cc894206162_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 0b894d89-f452-45d2-ada0-bddabe9e2aee_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 1c412384-ad00-4a08-8eae-c0783ec8cbf3_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 95c7da76-e72e-421a-a11e-2f32c3168301_"
      L3: " "
  ```


</details>


❌ not ok **cl.flannel.vxlan**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 0dae7ac8-371d-4d28-9a8a-5d9f79997fb4_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 99e30e93-7275-430f-96b6-65a42fad45e5_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 8dbc30bb-b245-4de2-97e2-8d329f81292e_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 5ea492a4-9194-4da6-a16b-cbeed24d4b27_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: fca2f544-8bb0-4279-9049-57ea9dece5fb_"
      L3: " "
  ```


</details>


❌ not ok **cl.ignition.kargs**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 656b208d-4dd2-4f14-8f58-8e97eeff4d99_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: e9a27280-197d-4f41-9230-36c0131fc2f0_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 1c99001f-81be-4f74-81f1-91dbb10486da_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: e545a872-c5b1-4137-bb9d-a21ad38f48bb_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 1c419941-ecd1-4a5d-bf3b-9846c9c203fc_"
      L3: " "
  ```


</details>


🟢 ok **cl.install.cloudinit**; Succeeded: aws (1)

❌ not ok **coreos.ignition.resource.remote**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: f8cb666a-f9f3-40e7-ad52-9e32bc383f53_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: d6480daa-d1f9-4aa6-a19c-8eb2560dddc5_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: c78bc0bc-078c-4d52-a42f-6dcdc55911a5_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: fb368997-8dd8-4b01-ba70-f55eb01b6fd3_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 2138dc45-e758-4954-a935-d8bf94b1570f_"
      L3: " "
  ```


</details>


❌ not ok **coreos.ignition.security.tls**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: RequestLimitExceeded: Request limit exceeded. Account 075585003325 has been throttled on ec2:RunInstances because it ?exceeded its request rate limit."
      L2: "status code: 503, request id: 0f0e332a-a9f1-49c1-b87b-52e8d978df24_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 809e3f9f-6365-4719-b9eb-122f4cdfe14d_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _security.go:132: starting client: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry ?your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 6f1e5c0e-4949-4e9e-8c2e-55aa05c97e81_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: dbe6843a-bfab-4ffc-8b66-fe183145350a_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _harness.go:651: Cluster failed starting machines: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a?). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: d335e5ac-c603-4685-94d1-7b3de85841e6_"
      L3: " "
  ```


</details>


❌ not ok **kubeadm.v1.35.1.calico.base**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: e4daa4f7-0905-4d2b-b0a2-30157af8f2ea_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 16908c04-c759-4ae4-9754-e1c69db31ee5_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 5e5a5979-5249-46d2-9a6e-04c11ba82df0_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabi?lity Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 87d61b29-b60d-42ed-a735-107d50b5741a_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: d70e1003-aaa2-461b-aa96-76e9510dbe24_"
      L3: " "
  ```


</details>


❌ not ok **kubeadm.v1.35.1.calico.cgroupv1.base**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 54be17ba-8a0d-4731-912c-0435d5418b75_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: f67fdb40-6141-4951-ada4-993ec3d49241_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 8c925c40-ad99-4115-94ad-79a93c113a4d_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 1cc88590-ee1b-4cf5-96ad-5e970d2dbd85_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 426b4b85-a954-4d07-883f-2b465ecd78c7_"
      L3: " "
  ```


</details>


❌ not ok **kubeadm.v1.35.1.cilium.cgroupv1.base**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: RequestLimitExceeded: Request limit exceeded. Account 075585003325 has been throttled on ec2:RunIn?stances because it exceeded its request rate limit."
      L2: "status code: 503, request id: 1be1822c-ae3f-4586-8e43-af30a8d9cac2_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: afe30dc8-43f8-4fa1-86c1-c330010d542f_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: f482df95-eba8-426c-a831-717971f94f02_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: e7c2c951-bf39-489a-8207-fa4bb725e968_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 4b1b4e35-7b7d-4331-89bf-c607bab7af1f_"
      L3: " "
  ```


</details>


❌ not ok **kubeadm.v1.36.1.flannel.base**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: cadd1cdc-6c4a-46b0-8bb6-6bb2be8eb615_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 593f0131-7593-4d5d-a4c9-6d8f03a3d077_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: bc17fe73-c812-4264-b82e-a132a4e6eeae_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabi?lity Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 9aa2719f-ed99-4da2-855c-ed30e112e82d_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 7f0aac15-d52f-4083-83d8-2807613699bf_"
      L3: " "
  ```


</details>


❌ not ok **kubeadm.v1.37.0.calico.base**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 5f63e228-db44-40fc-a47c-2b51ea8ab71f_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabi?lity Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 4f8af0fd-3c53-42d1-aa31-1934103ba8fe_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create master node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabi?lity Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 49934327-3710-452a-9f9b-598e828deae1_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 8c9eef68-e40a-4b49-bc2d-94935f335e29_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.37.1"
      L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.37.1"
      L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.37.1"
      L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.37.1"
      L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.6"
      L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
      L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.7.0-0"
      L8: "cluster.go:125: [init] Using Kubernetes version: v1.37.1"
      L9: "cluster.go:125: [preflight] Running pre-flight checks"
      L10: "cluster.go:125: E1027 13:57:12.029520    2719 remote_runtime.go:1359] __RuntimeConfig from runtime service failed__ err=__rpc error: code = Unimplemented desc = unknown method RuntimeConfig for servic?e runtime.v1.RuntimeService__"
      L11: "cluster.go:125:  [WARNING ContainerRuntimeVersion]: You must update your container runtime to a version that supports the CRI method RuntimeConfig. Falling back to using cgroupDriver from kubelet conf?ig will be removed in 1.38. For more information, see https://git.k8s.io/enhancements/keps/sig-node/4033-group-driver-detection-over-cri"
      L12: "cluster.go:125:  [WARNING Service-kubelet]: kubelet service is not enabled, please run _systemctl enable kubelet.service_"
      L13: "cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster"
      L14: "cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection"
      L15: "cluster.go:125: [preflight] You can also perform this action beforehand using _kubeadm config images pull_"
      L16: "cluster.go:125: W1027 13:57:12.207639    2719 checks.go:920] detected that the sandbox image __registry.k8s.io/pause:3.8__ of the container runtime is inconsistent with that used by kubeadm. It is rec?ommended to use __registry.k8s.io/pause:3.10.2__ as the CRI sandbox image."
      L17: "cluster.go:125: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
      L18: "cluster.go:125: [certs] Generating __ca__ certificate and key"
      L19: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
      L20: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ip-172-31-21-69 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 17?2.31.21.69]"
      L21: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
      L22: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
      L23: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
      L24: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
      L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
      L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
      L27: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
      L28: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
      L29: "cluster.go:125: [certs] Generating __sa__ key and public key"
      L30: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
      L31: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
      L32: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
      L33: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
      L34: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
      L35: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
      L36: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
      L37: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
      L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
      L39: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
      L40: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
      L41: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
      L42: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
      L43: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
      L44: "cluster.go:125: [kubelet-start] Starting the kubelet"
      L45: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
      L46: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
      L47: "cluster.go:125: [kubelet-check] The kubelet is healthy after 1.639527ms"
      L48: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
      L49: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.31.21.69:6443/livez"
      L50: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
      L51: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
      L52: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 23.749225ms"
      L53: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 28.065129ms"
      L54: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.502366069s"
      L55: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
      L56: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
      L57: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
      L58: "cluster.go:125: [mark-control-plane] Marking the node ip-172-31-21-69 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balanc?ers]"
      L59: "cluster.go:125: [mark-control-plane] Marking the node ip-172-31-21-69 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
      L60: "cluster.go:125: [bootstrap-token] Using token: k74a7h.fje3f3wi1nvtnwnn"
      L61: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
      L62: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
      L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials"
      L64: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
      L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
      L66: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API"
      L67: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
      L68: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
      L69: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
      L70: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
      L71: "cluster.go:125: "
      L72: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
      L73: "cluster.go:125: "
      L74: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
      L75: "cluster.go:125: "
      L76: "cluster.go:125:   mkdir -p $HOME/.kube"
      L77: "cluster.go:125:   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
      L78: "cluster.go:125:   sudo chown $(id -u):$(id -g) $HOME/.kube/config"
      L79: "cluster.go:125: "
      L80: "cluster.go:125: Alternatively, if you are the root user, you can run:"
      L81: "cluster.go:125: "
      L82: "cluster.go:125:   export KUBECONFIG=/etc/kubernetes/admin.conf"
      L83: "cluster.go:125: "
      L84: "cluster.go:125: You should now deploy a pod network to the cluster."
      L85: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
      L86: "cluster.go:125:   https://kubernetes.io/docs/concepts/cluster-administration/addons/"
      L87: "cluster.go:125: "
      L88: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
      L89: "cluster.go:125: "
      L90: "cluster.go:125: kubeadm join 172.31.21.69:6443 --token k74a7h.fje3f3wi1nvtnwnn _"
      L91: "cluster.go:125:  --discovery-token-ca-cert-hash sha256:59206a8a7c309a7a4a41ce30aedda7eb8f3e5fd8095211436adb5b32fbba5b66 "
      L92: "cluster.go:125: namespace/tigera-operator created"
      L93: "cluster.go:125: serviceaccount/tigera-operator created"
      L94: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created"
      L95: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created"
      L96: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created"
      L97: "cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created"
      L98: "cluster.go:125: deployment.apps/tigera-operator created"
      L99: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
      L100: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met"
      L101: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
      L102: "cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met"
      L103: "cluster.go:125: installation.operator.tigera.io/default created"
      L104: "cluster.go:125: apiserver.operator.tigera.io/default created"
      L105: "cluster.go:125: goldmane.operator.tigera.io/default created"
      L106: "cluster.go:125: whisker.operator.tigera.io/default created"
      L107: "kubeadm.go:197: unable to setup cluster: unable to create worker node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zon?e (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L108: "status code: 400, request id: 5bbad489-ba96-4ce4-967e-3198628b7b15_"
      L109: " "
  ```


</details>


❌ not ok **kubeadm.v1.37.0.flannel.base**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 63f3f887-16f8-4177-9544-88fdcb20e476_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 1744f91c-cd7b-42f7-8f84-fc9089949bb6_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: e7d889bc-dd2c-41d0-84e5-6b4d029e153b_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: e450a5d5-7f50-4e4d-9e09-e2c244102570_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _kubeadm.go:197: unable to setup cluster: unable to create etcd node: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availabili?ty Zone (us-west-2a). Please retry your request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: b0c47724-9044-49cc-ba3e-099403117025_"
      L3: " "
  ```


</details>


❌ not ok **linux.nfs.v3**; Failed: aws (1, 2, 3, 4, 5)

<details>

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 5</summary>

  ```
      L1: " Error: _nfs.go:80: NFS server booted."
      L2: "nfs.go:85: Test file __/tmp/tmp.79zeQuCPnU__ created on server."
      L3: "nfs.go:122: Cluster.NewMachine: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry your reque?st by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L4: "status code: 400, request id: d392fc3b-caa7-4d87-aee2-6c052fb6ca92_"
      L5: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 4</summary>

  ```
      L1: " Error: _nfs.go:80: NFS server booted."
      L2: "nfs.go:85: Test file __/tmp/tmp.aCFJMWmU75__ created on server."
      L3: "nfs.go:122: Cluster.NewMachine: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry your reque?st by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L4: "status code: 400, request id: 95eb07f3-f232-464e-b0e7-dcc10465d4ae_"
      L5: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 3</summary>

  ```
      L1: " Error: _nfs.go:77: Cluster.NewMachine: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry you?r request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: 65dd8ccd-56e9-453e-a4fa-daf0fdbcc36a_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 2</summary>

  ```
      L1: " Error: _nfs.go:77: Cluster.NewMachine: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry you?r request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: d3b77e79-b87b-4b5c-9963-9ca779e4cd11_"
      L3: " "
  ```

<summary>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Diagnostic output for aws, run 1</summary>

  ```
      L1: " Error: _nfs.go:77: Cluster.NewMachine: error running instances: Unsupported: Your requested instance type (a1.large) is not supported in your requested Availability Zone (us-west-2a). Please retry you?r request by not specifying an Availability Zone or choosing us-west-2b, us-west-2c."
      L2: "status code: 400, request id: ac3cb35c-76a0-47ff-9728-6666f6ceb3d9_"
      L3: " "
  ```


</details>