-
Notifications
You must be signed in to change notification settings - Fork 835
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
CRI-O artifact staging #1882
Comments
/reopen |
@spiffxp: Reopened 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. |
... so actually, cri-o is not actually part of kubernetes anymore (as of kubernetes/community#3668). It's now a CNCF incubating project: https://cri-o.io/ If it's not part of kubernetes, I don't think k8s-infra is the right place to host its artifacts. #915 - we still need to document our policies on what is/not fair game for a staging project |
Thank you for the clarification, I'll check if I can request a project directly from the CNCF |
@saschagrunert: 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. |
We require a staging location for image and binary artifacts, which is modifiable by us (without a retention policy).
I'll request a staging project for that purpose.
cc @haircommander @mrunalp
The text was updated successfully, but these errors were encountered: