Skip to content

Conversation

@quoctruong
Copy link
Collaborator

Each headless service will target a runner workflow (the service will be cleaned up after the job is done).
The hook will use the headless service to reach the pod instead of through the pod's IP.

Copy link

@MichaelHudgins MichaelHudgins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall change looks fine, what does the full service name end up looking like? Can you give me an example?

@quoctruong
Copy link
Collaborator Author

quoctruong commented Jul 18, 2025

Overall change looks fine, what does the full service name end up looking like? Can you give me an example?

For example, if the workflow is linux-arm64-c4a-16-v4qqc-runner-9gj29-workflow then the service name will be linux-arm64-c4a-16-v4qqc-runner-9gj29-service

@quoctruong quoctruong merged commit ae46885 into google-main Jul 18, 2025
2 checks passed
@quoctruong quoctruong deleted the quoct/use_pod_service branch July 18, 2025 18:13
@quoctruong quoctruong restored the quoct/use_pod_service branch July 24, 2025 04:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants