Set specific awsClusterRoleIdentityName for CAPA test suites

[ericgraf]

What this PR does

Towards: https://github.com/giantswarm/giantswarm/issues/29815

Checklist

• Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

[tinkerers-ci]

Note

As this is a draft PR no triggers from the PR body will be handled.

If you'd like to trigger them while draft please add them as a PR comment.

[tinkerers-ci]

Note

As this is a draft PR no triggers from the PR body will be handled.

If you'd like to trigger them while draft please add them as a PR comment.

[AverageMarcus]

/run cluster-test-suites

[AverageMarcus]

🤦 This is going to fail.

[AverageMarcus]

/run cluster-test-suites TARGET_SUITES=./providers/capa,./providers/eks

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-444-cluster-test-suites2pxrs
Commit SHA	859ba57
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[AverageMarcus]

/run cluster-test-suites TARGET_SUITES=./providers/capa/private,./providers/capa/cilium-eni-mode

[AverageMarcus]

/run cluster-test-suites TARGET_SUITES=./providers/capa/private

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-444-cluster-test-suitesm2ht9
Commit SHA	859ba57
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-444-cluster-test-suitesz426l
Commit SHA	859ba57
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[AverageMarcus]

COME ON!!!! 😞

/run cluster-test-suites TARGET_SUITES=./providers/capa/private

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-444-cluster-test-suitessl2xk
Commit SHA	859ba57
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[AverageMarcus]

It turns out the capa private test suite is failing due to a missing IAM permission on the role in the new AWS account. Team Phoenix is assisting with getting it resolved and then I'll re-run the tests to confirm.

[AverageMarcus]

/run cluster-test-suites TARGET_SUITES=./providers/capa/private

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-444-cluster-test-suitesdhslb
Commit SHA	77f9689
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[fiunchinho]

/run cluster-test-suites TARGET_SUITES=./providers/capa/private

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-444-cluster-test-suites8p5jz
Commit SHA	77f9689
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[fiunchinho]

/run cluster-test-suites TARGET_SUITES=./providers/capa/private

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-444-cluster-test-suites2n2lw
Commit SHA	77f9689
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[AverageMarcus]

It looks like the private CAPA WCs don't currently work when deployed into a different AWS account. I've opened an issue for Team Phoenix to investigate and will be removing the change for private WCs from this PR so we can at least have the others isolated.

Issue: giantswarm/roadmap#3671

[AverageMarcus]

/run cluster-test-suites TARGET_SUITES=./providers/capa,./providers/eks

[AverageMarcus]

/run cluster-test-suites TARGET_SUITES=./providers/capa/cilium-eni-mode

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-444-cluster-test-suitessps9g
Commit SHA	bde6f2f
Result	Completed ✅

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

[tinkerers-ci]

Oh No! 😱 At least one test suite has failed during the AfterSuite cleanup stage and might have left around some resources on the MC!

Be sure to check the full results in Tekton Dashboard to see which test suite has failed and then run the following on the associated MC to list all leftover resources:

PIPELINE_RUN="pr-cluster-test-suites-444-cluster-test-suitesxj5jc"

NAMES="$(kubectl api-resources --verbs list -o name | tr '\n' ,)"
kubectl get "${NAMES:0:${#NAMES}-1}" --show-kind --ignore-not-found -l cicd.giantswarm.io/pipelinerun=${PIPELINE_RUN} -A 2>/dev/null

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-444-cluster-test-suitesxj5jc
Commit SHA	bde6f2f
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.