-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Hook up etcd to kubernetes' prow infrastructure to run CI jobs #16653
Comments
cc @chaochn47 |
Hi thanks dim for the feature request. I think it is related to #16467 and please check #16467 (comment) summarized the conversation with sig-scalability. /cc @mehvaibh since you are interested based on #16510 (comment).
Those are already run regularly in upstream, once a day nightly. The more important problem is we don't have public SLO/SLAs that can be a baseline to compare with. No visualization of the trend. I am keen to close this issue and please register to #16467 for updates. WDYT? |
Looks like step 1 is https://docs.prow.k8s.io/docs/getting-started-deploy/#install-prow-for-a-github-organization-or-repo will poke github admins |
Hi @dims - Many thanks for raising this. I think this directly relates to our overall I would be happy for #16467 to be an early candidate for prow workloads for etcd. Perhaps in an iterative manner as each individual SLI is agreed and put together. Thanks for getting the ball rolling with github admins, I am happy for this issue to stay open to track the actual mechanics of getting kubernetes prow infra setup / enabled for the etcd-io github org. Once enabled we can use other issues to track adding specific jobs etc. Note - Adopting prow bot is an enabler for: Edit: Link to slack discussion raised by @dims with github admins is here: https://kubernetes.slack.com/archives/C01672LSZL0/p1695752626527319 |
Closing - Prow is now hooked up for etcd-io/etcd, refer dashboard https://prow.k8s.io/?repo=etcd-io%2Fetcd. There is further work in progress being discussed under kubernetes/k8s.io#6102. |
To be able to run for example the robustness suite regularly?
The text was updated successfully, but these errors were encountered: