-
Notifications
You must be signed in to change notification settings - Fork 827
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
Setup a k8s-infra prow instance #1394
Comments
/wg k8s-infra |
Triage-Party sometimes hit the Github API Limit. ``` message: "oh snap! I reached the GitHub search API limit: GET https://api.github.com/repos/kubernetes/release/issues?per_page=100&since=2021-02-23T15%3A13%3A29Z&state=closed: 403 API rate limit of 5000 still exceeded until 2021-03-25 15:17:12 +0000 UTC, not making remote request. [rate reset in 3m42s]" ``` GH Proxy can be used to cache TP API calls. Ultimately, ghproxy needs to be deploy as part of kubernetes#1394. Signed-off-by: Arnaud Meukam <[email protected]>
Triage-Party sometimes hit the Github API Limit. ``` message: "oh snap! I reached the GitHub search API limit: GET https://api.github.com/repos/kubernetes/release/issues?per_page=100&since=2021-02-23T15%3A13%3A29Z&state=closed: 403 API rate limit of 5000 still exceeded until 2021-03-25 15:17:12 +0000 UTC, not making remote request. [rate reset in 3m42s]" ``` GH Proxy can be used to cache TP API calls. Ultimately, ghproxy needs to be deploy as part of kubernetes#1394. Signed-off-by: Arnaud Meukam <[email protected]>
Triage-Party sometimes hit the Github API Limit. ``` message: "oh snap! I reached the GitHub search API limit: GET https://api.github.com/repos/kubernetes/release/issues?per_page=100&since=2021-02-23T15%3A13%3A29Z&state=closed: 403 API rate limit of 5000 still exceeded until 2021-03-25 15:17:12 +0000 UTC, not making remote request. [rate reset in 3m42s]" ``` GH Proxy can be used to cache TP API calls. Ultimately, ghproxy needs to be deploy as part of kubernetes#1394. Signed-off-by: Arnaud Meukam <[email protected]>
As discussed during WG K8s infra meeting of March 31 2021, we agreed to call |
For kubernetes#1394, we will need a new github account acting as a new bot [k8s-staging-ci-robot](https://github.com/k8s-staging-ci-robot). Adding a new mailing list that list be use for administration of this robot. Signed-off-by: Arnaud Meukam <[email protected]>
/retitle |
For kubernetes#1394, we will need a new github account acting as a new bot [k8s-staging-ci-robot](https://github.com/k8s-staging-ci-robot). Adding a new mailing list that list be use for administration of this robot. Signed-off-by: Arnaud Meukam <[email protected]>
/milestone v1.22 |
I'm not entirely clear on why this is in Blocked other than I think we need to get a plan of agreed-upon next steps The latest outstanding PR I see related to this is #1909 but it's in need of a rebase and I'm not sure whether my review comments were addressed |
(from slack) We need to sign the CLA for https://github.com/k8s-infra-ci-robot and make it an owner of the appropriate kubernetes orgs |
https://k8s-infra-prow.k8s.io/pr is functional |
/remove-priority important-longterm |
AIUI an incorrect kubeconfig was preventing us from scheduling jobs on the k8s-infra-prow-build cluster, which has since been updated. https://k8s-infra-prow.k8s.io/ now shows a heartbeat job being regularly scheduled |
Ref: kubernetes#1394 List the job in sig-k8s-infra testgrid dashboard. Signed-off-by: Arnaud Meukam <[email protected]>
Ref: kubernetes#1394 Expose k8s-infra-prow.k8s.io using IPv6. Signed-off-by: Arnaud Meukam <[email protected]>
Related: - part of: kubernetes#1394 Enable GKE workloads metrics that give the capability to send metrics for a GKE cluster to cloud monitoring. See: https://cloud.google.com/stackdriver/docs/solutions/gke/managing-metrics#enable-workload-metrics Signed-off-by: Arnaud Meukam <[email protected]>
/milestone clear |
This are done with this experiment at the moment. |
@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/test-infra repository. |
Part of #752
Why it's needed :
The current prow instance https://prow.k8s.io should be moved to the community-owned infrastructure.
The prow
staginginstancek8s-infra-prow
will help identify the resources needed and define a migration plan.What's needed (not in a specific order):
k8s-infra-prow-build
andk8s-infra-prow-build-trusted
: hook up build clusters to prow staging instance #1475Other considerations:
[ ] investigate usage of k8s-gsm-toolsThe text was updated successfully, but these errors were encountered: