-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decommission gke-project-pool #23778
Comments
Inspecting output of
Jobs I'm less certain about:
|
Another way of surveying which jobs are actually using the projects gcloud logging read \
--project=k8s-prow-builds \
--format=json \
--limit=100 \
--freshness=1d \
'
jsonPayload.component="boskos"
jsonPayload.msg=~"Request for a free gke-project from"
' \
| jq -r 'map(.jsonPayload.msg)[]' \
| sort \
| uniq -c
|
Jobs to decomission or replace with alternatives:
|
/close |
@spiffxp: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What should be cleaned up or changed:
We shouldn't be using gke-specific projects to run prowjobs for kubernetes. We have mostly stopped running jobs that require these, it's time to decommission the pool and identify whether jobs that still use these projects can use gce-project or should be running elsewhere.
Provide any links for context:
Related to:
/sig testing
/priority important-longterm
/area boskos
/area jobs
/milestone v1.23
The text was updated successfully, but these errors were encountered: