Add GitHub Actions for Network Scenario Tests on PRs

This PR adds a new workflow that allows developers to trigger network scenario tests on pull requests by adding the ci-network-scenario label. The workflow deploys a full Aztec network in a PR-specific Kubernetes namespace and runs scenario tests against it.

Key features:

New GitHub workflow ci3-network-scenario.yml triggered by the ci-network-scenario label
Reusable GitHub Actions for GCP authentication and network environment setup
Automatic cleanup of Kubernetes resources after tests complete
PR comments with test results and status information
Caching to prevent redundant test runs for the same code

The implementation extracts common functionality from the existing test-network-scenarios.yml workflow into reusable GitHub Actions:

setup-gcp-auth - Handles GCP service account authentication and kubectl setup
setup-network-env - Creates network environment configuration and SSH keys

This allows developers to run the same network scenario tests that are run on releases, but on their PRs before merging.

Oct 04 '25 09:10 just-mitch

#17505 👈 (View in Graphite)
next

This stack of pull requests is managed by Graphite. Learn more about stacking.

Oct 04 '25 09:10 just-mitch

✅ Network Scenario Tests PASSED

Test Status: passed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

To re-run tests, add the ci-network-scenario label again

Oct 04 '25 10:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 04 '25 11:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 04 '25 14:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 16 '25 16:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 16 '25 23:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 22 '25 23:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 23 '25 18:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 24 '25 00:10 github-actions[bot]

Flakey Tests

🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry.

Flaked tests

\033[38;2;188;109;208mFLAKED\033[0m (\033[38;2;250;217;121m]8;;http://ci.aztec-labs.com/0b4a31f25d2edcaa0b4a31f25d2edcaa]8;;\033[0m): BOX=vanilla BROWSER=* run_compose_test vanilla-all-browsers box boxes (431s) (code: 1) (\033[38;2;188;109;208mMitch\033[0m: feat: ci-network-scenario label)

Oct 25 '25 13:10 AztecBot

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 25 '25 13:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 25 '25 16:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

To re-run tests, add the ci-network-scenario label again

Oct 25 '25 19:10 github-actions[bot]

✅ Network Scenario Tests PASSED

Test Status: passed Namespace: pr-17505-scenario Cleanup Status: ✅ Cleaned up successfully Workflow Run: View logs

To re-run tests, add the ci-network-scenario label again

Oct 25 '25 19:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ⚠️ Cleanup may have failed Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

Manual Cleanup Required

If cleanup failed, you may need to manually delete the namespace:

kubectl delete namespace pr-17505-scenario

To re-run tests, add the ci-network-scenario label again

Oct 25 '25 21:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ⚠️ Cleanup may have failed Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

Manual Cleanup Required

If cleanup failed, you may need to manually delete the namespace:

kubectl delete namespace pr-17505-scenario

To re-run tests, add the ci-network-scenario label again

Oct 26 '25 14:10 github-actions[bot]

❌ Network Scenario Tests FAILED

Test Status: failed Namespace: pr-17505-scenario Cleanup Status: ⚠️ Cleanup may have failed Workflow Run: View logs

⚠️ Tests Failed

Please check the workflow logs for details.

Manual Cleanup Required

If cleanup failed, you may need to manually delete the namespace:

kubectl delete namespace pr-17505-scenario

To re-run tests, add the ci-network-scenario label again

Oct 26 '25 18:10 github-actions[bot]

✅ Network Scenario Tests PASSED

Test Status: passed Namespace: pr-17505-scenario Cleanup Status: ⚠️ Cleanup may have failed Workflow Run: View logs

Manual Cleanup Required

If cleanup failed, you may need to manually delete the namespace:

kubectl delete namespace pr-17505-scenario

To re-run tests, add the ci-network-scenario label again

Oct 26 '25 20:10 github-actions[bot]