-
Notifications
You must be signed in to change notification settings - Fork 791
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
Migrate k8s-gubernator:builds dataset to wg-k8s-infra #1307
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove lifecycle-stale |
@spiffxp With kettle currently down, we can go with
I can add a BQ dataset in kubernetes-public and data transfer job. |
/remove-priority important-longterm |
Pretty sure I've seen activity on this in PRs related to kettle: |
Next steps are :
|
/milestone v1.24 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/milestone clear |
We can close this. From: #789. All the datasets are gone. cc @BenTheElder /close |
@ameukam: 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-sigs/prow repository. |
Yeah, this should be in k8s-infra already. Thanks for closing. |
Part of migrating away from gcp-project k8s-gubernator: #1308
This dataset: https://console.cloud.google.com/bigquery?p=k8s-gubernator
It's used by:
It's publicly readable (though compute time for queries will be charged to their own GCP account), but not publicly writable
It's not quite clear to me what strategies are available to us:
Given that this is a public artifact I'm inclined to suggest we home this under the kubernetes-public gcp project. We should examine billing briefly to understand if there are associated network/compute costs we would want billed elsewhere.
The text was updated successfully, but these errors were encountered: