### Test report for 4757.2.3 / arm64

**Platforms tested** : aws 

❌ 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: e72ae414-d261-4ac0-a028-b283fef815c3_"
      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: b6b6df46-58e3-405e-9f77-30c6ef96d5f7_"
      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: 28391e0f-e208-49aa-89c9-0ae467f36ca6_"
      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: 318012de-eb6b-47e1-b699-7cc285d18f55_"
      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: e28854c9-3cd4-42fd-918a-5855601b3856_"
      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: 1309422d-60ca-4836-bb5e-fc7325e1151e_"
      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: 00b9ba4c-1e31-42dd-b732-8f3ae0c9c130_"
      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: e2954354-5c29-4dec-b994-e6bed4cd9314_"
      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: bb9a05b1-b4ff-4602-8a83-2bae70363ed2_"
      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: 2b921310-c370-457a-8618-06002939078f_"
      L3: " "
  ```


</details>


❌ not ok **cl.ignition.v1.noop**; 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: ab356e93-f016-4fbd-85fc-93d5397c452f_"
      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: 744eed48-e911-4d22-bcde-b4c1f8258ba4_"
      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: 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: a774d578-083a-4ed7-b3ec-b0c7c4688b1d_"
      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: f32344e1-d31c-42b3-90cf-9bc3ec56da45_"
      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: 3dcb4bad-ffd0-4a7c-a72b-4d0a9a5741b4_"
      L3: " "
  ```


</details>


❌ not ok **cl.metadata.aws**; 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: d6845674-a8d3-413b-939b-b60b1234c99b_"
      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: 5c427b20-93fc-4bfb-991d-d95e8d6a1795_"
      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: 46e4836f-aabd-45b0-9c3e-96c8b152c88c_"
      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: 01a4c634-5c80-46df-8b6f-2330a830c4e8_"
      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: baf15504-1a8a-4ea7-bd8e-60ef95c55472_"
      L3: " "
  ```


</details>


❌ not ok **coreos.ignition.resource.local**; 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: dc9458b7-fcbc-4023-9d17-8992ddb3519a_"
      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: 3dccc22c-f951-4e67-8243-5b64e0fa6017_"
      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: 25ab5301-010a-4be2-8b36-c01d81db337a_"
      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: _resource.go:333: 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: d7a76569-a1d1-4e47-a6ef-d22bb01456f8_"
      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: 925fd0e3-7953-4fe4-b788-b945a80c1bb2_"
      L3: " "
  ```


</details>


❌ not ok **docker.network-openbsd-nc**; 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: 3cadff84-398f-4354-bef9-f5b3d3b5edd6_"
      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: 3d06cf90-d6ae-4e27-9f9c-4eded9d36fb9_"
      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: 8e30cc38-e70e-4483-892c-f35bf5776a3d_"
      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: 15fa2c72-887f-48f2-b7a6-a97411e88b4a_"
      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: c5f7090a-39a2-4d7e-b5c3-dc3d01f2b751_"
      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: 07c8f906-78c1-467a-86cb-163887f39e99_"
      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: c5f8b913-cb45-4302-95b1-f9dbd8256389_"
      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: 6f95a3fa-c87f-48f2-b9e5-536ff6dfeda7_"
      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: 023a9c63-7210-48da-8bf3-d4b4047ccb10_"
      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: 9219231c-c886-4cd4-8717-96d1d7b3932c_"
      L3: " "
  ```


</details>


❌ not ok **kubeadm.v1.35.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: b7e62320-bf55-4617-8211-80d639429066_"
      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: 397c4359-3af2-43c3-b7bd-4cbbda2f2247_"
      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: 99b6e343-810c-4626-9ad2-359995d74634_"
      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: 9de12f3a-e244-4565-913a-950776adecc9_"
      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: 73b315ae-9051-4043-80a2-a840f0e7bac6_"
      L3: " "
  ```


</details>


❌ not ok **kubeadm.v1.36.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: 20a204ed-0860-4b42-9d76-a725a125ccc0_"
      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: b627348c-0b5a-4dc5-bc4b-1e224a7b68de_"
      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: c2d48ede-3ead-4637-ac70-5143ae3405a6_"
      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: dffbe391-ca77-44c3-8dda-c1008f467433_"
      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 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: 4ece2dbe-a61d-44f4-b7d4-ae21d327f58e_"
      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: f5f11f22-0928-4679-8f8b-44cbc950986f_"
      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: dcdd2a98-245e-4ba0-8ba8-08c794f1b570_"
      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: _cluster.go:125: I1027 14:38:12.556275    2490 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
      L2: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.5"
      L3: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.5"
      L4: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.5"
      L5: "cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.5"
      L6: "cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2"
      L7: "cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2"
      L8: "cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0"
      L9: "cluster.go:125: I1027 14:38:25.975854    2727 version.go:260] remote version is much newer: v1.37.1; falling back to: stable-1.36"
      L10: "cluster.go:125: [init] Using Kubernetes version: v1.36.5"
      L11: "cluster.go:125: [preflight] Running pre-flight checks"
      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: [certs] Using certificateDir folder __/etc/kubernetes/pki__"
      L17: "cluster.go:125: [certs] Generating __ca__ certificate and key"
      L18: "cluster.go:125: [certs] Generating __apiserver__ certificate and key"
      L19: "cluster.go:125: [certs] apiserver serving cert is signed for DNS names [ip-172-31-28-161 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 1?72.31.28.161]"
      L20: "cluster.go:125: [certs] Generating __apiserver-kubelet-client__ certificate and key"
      L21: "cluster.go:125: [certs] Generating __front-proxy-ca__ certificate and key"
      L22: "cluster.go:125: [certs] Generating __front-proxy-client__ certificate and key"
      L23: "cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation"
      L24: "cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation"
      L25: "cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation"
      L26: "cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation"
      L27: "cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation"
      L28: "cluster.go:125: [certs] Generating __sa__ key and public key"
      L29: "cluster.go:125: [kubeconfig] Using kubeconfig folder __/etc/kubernetes__"
      L30: "cluster.go:125: [kubeconfig] Writing __admin.conf__ kubeconfig file"
      L31: "cluster.go:125: [kubeconfig] Writing __super-admin.conf__ kubeconfig file"
      L32: "cluster.go:125: [kubeconfig] Writing __kubelet.conf__ kubeconfig file"
      L33: "cluster.go:125: [kubeconfig] Writing __controller-manager.conf__ kubeconfig file"
      L34: "cluster.go:125: [kubeconfig] Writing __scheduler.conf__ kubeconfig file"
      L35: "cluster.go:125: [control-plane] Using manifest folder __/etc/kubernetes/manifests__"
      L36: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-apiserver__"
      L37: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-controller-manager__"
      L38: "cluster.go:125: [control-plane] Creating static Pod manifest for __kube-scheduler__"
      L39: "cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file __/var/lib/kubelet/kubeadm-flags.env__"
      L40: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/instance-config.yaml__"
      L41: "cluster.go:125: [patches] Applied patch of type __application/strategic-merge-patch+json__ to target __kubeletconfiguration__"
      L42: "cluster.go:125: [kubelet-start] Writing kubelet configuration to file __/var/lib/kubelet/config.yaml__"
      L43: "cluster.go:125: [kubelet-start] Starting the kubelet"
      L44: "cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory __/etc/kubernetes/manifests__"
      L45: "cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s"
      L46: "cluster.go:125: [kubelet-check] The kubelet is healthy after 1.17168ms"
      L47: "cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s"
      L48: "cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.31.28.161:6443/livez"
      L49: "cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz"
      L50: "cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez"
      L51: "cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 18.567504ms"
      L52: "cluster.go:125: [control-plane-check] kube-scheduler is healthy after 23.355528ms"
      L53: "cluster.go:125: [control-plane-check] kube-apiserver is healthy after 2.003776702s"
      L54: "cluster.go:125: [upload-config] Storing the configuration used in ConfigMap __kubeadm-config__ in the __kube-system__ Namespace"
      L55: "cluster.go:125: [kubelet] Creating a ConfigMap __kubelet-config__ in namespace kube-system with the configuration for the kubelets in the cluster"
      L56: "cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs"
      L57: "cluster.go:125: [mark-control-plane] Marking the node ip-172-31-28-161 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balan?cers]"
      L58: "cluster.go:125: [mark-control-plane] Marking the node ip-172-31-28-161 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]"
      L59: "cluster.go:125: [bootstrap-token] Using token: y51lo4.dbobmyt5we230w2n"
      L60: "cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles"
      L61: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes"
      L62: "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"
      L63: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token"
      L64: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster"
      L65: "cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API"
      L66: "cluster.go:125: [bootstrap-token] Creating the __cluster-info__ ConfigMap in the __kube-public__ namespace"
      L67: "cluster.go:125: [kubelet-finalize] Updating __/etc/kubernetes/kubelet.conf__ to point to a rotatable kubelet client certificate and key"
      L68: "cluster.go:125: [addons] Applied essential addon: CoreDNS"
      L69: "cluster.go:125: [addons] Applied essential addon: kube-proxy"
      L70: "cluster.go:125: "
      L71: "cluster.go:125: Your Kubernetes control-plane has initialized successfully!"
      L72: "cluster.go:125: "
      L73: "cluster.go:125: To start using your cluster, you need to run the following as a regular user:"
      L74: "cluster.go:125: "
      L75: "cluster.go:125:   mkdir -p $HOME/.kube"
      L76: "cluster.go:125:   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config"
      L77: "cluster.go:125:   sudo chown $(id -u):$(id -g) $HOME/.kube/config"
      L78: "cluster.go:125: "
      L79: "cluster.go:125: Alternatively, if you are the root user, you can run:"
      L80: "cluster.go:125: "
      L81: "cluster.go:125:   export KUBECONFIG=/etc/kubernetes/admin.conf"
      L82: "cluster.go:125: "
      L83: "cluster.go:125: You should now deploy a pod network to the cluster."
      L84: "cluster.go:125: Run __kubectl apply -f [podnetwork].yaml__ with one of the options listed at:"
      L85: "cluster.go:125:   https://kubernetes.io/docs/concepts/cluster-administration/addons/"
      L86: "cluster.go:125: "
      L87: "cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:"
      L88: "cluster.go:125: "
      L89: "cluster.go:125: kubeadm join 172.31.28.161:6443 --token y51lo4.dbobmyt5we230w2n _"
      L90: "cluster.go:125:  --discovery-token-ca-cert-hash sha256:affc5a3b4b189b6f824d75eddb19e6430101670c6c8c19e138ce44b96fcd4822 "
      L91: "cluster.go:125: namespace/kube-flannel created"
      L92: "cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created"
      L93: "cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created"
      L94: "cluster.go:125: serviceaccount/flannel created"
      L95: "cluster.go:125: configmap/kube-flannel-cfg created"
      L96: "cluster.go:125: daemonset.apps/kube-flannel-ds created"
      L97: "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."
      L98: "status code: 400, request id: c016ee05-19ac-4f90-b2b4-6e083fb41980_"
      L99: " "
  ```

<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: 37f59d42-57b3-4c84-8b52-220074cbce43_"
      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: fb7f9cca-88b1-44a6-a8e8-f88fa64f2e5a_"
      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: 6c9fb316-88da-430d-bfad-9eb9f1d229c0_"
      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: 8e371d9f-3e8a-4201-818d-4fe338f4e7cc_"
      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: 9eedd4fe-9f00-413b-8550-782baa28b582_"
      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: 31ebff9d-9587-4b7c-99a2-467e452c29cc_"
      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: 568a9817-de0a-49a5-9d0d-162b3f2a5099_"
      L3: " "
  ```


</details>


❌ not ok **kubeadm.v1.37.0.cilium.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: 08c46da0-7929-4c4d-b409-3262cd646843_"
      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: 111a252e-d5cc-4f5b-a120-8a8898a7f8b5_"
      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: 90fb5be7-1ce0-4aab-9631-c37ed1596a0f_"
      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: 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: 458a1fbe-9818-44cf-923c-73e3ffd856e9_"
      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: ef534d2e-27d1-44d8-99f8-fbcc52f8e1de_"
      L3: " "
  ```


</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: dd252ddc-2255-4cf0-95e4-24072f7c992c_"
      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: b79b73d5-a39f-4584-8d5a-28bc93d43a3b_"
      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: b62b4628-d232-4ead-860c-453c374667b9_"
      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: 82b2214e-def3-4ed8-9c93-2010fa284c04_"
      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: 901f0b5c-5ece-4575-9f70-7487402802c2_"
      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.1We9b3FuA1__ 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: cbf658f9-f6eb-47cb-999b-9fc00c4d37ab_"
      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: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: 6042870d-e96f-4ff4-a168-d87d1cf26331_"
      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: _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: 559e743f-3744-4364-83bf-c5d51e37d523_"
      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: aa6ac446-97a7-4f52-9ea8-e67920439189_"
      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: 1c00d08b-70bc-424d-b318-f6ef7d9cd058_"
      L3: " "
  ```


</details>


❌ not ok **linux.nfs.v4**; 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: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: edf57fe0-6a1a-41ed-af6e-4649f4c8ed87_"
      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: _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: f7e8dd18-cd59-4fb1-8646-d18e94a945bb_"
      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: _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: 31a24725-c79a-4da1-9a9a-04a5424ef0db_"
      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: bb48d8aa-843b-43df-a4b3-d5d85a752b4d_"
      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:80: NFS server booted."
      L2: "nfs.go:85: Test file __/tmp/tmp.UQNzKoIUMo__ 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: 4b6fd105-cd26-4929-96c3-1b2f36cf4e64_"
      L5: " "
  ```


</details>