-
Notifications
You must be signed in to change notification settings - Fork 384
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
CNI plugins (kubernetes-cni) build and packaging process improvements #245
Comments
Can someone pick this up? |
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-testing, kubernetes/test-infra and/or fejta. |
Given lack of engagement on this ticket, I'm going to close it. |
...well this seems like something we still need to do given last cycle's kerfuffle. |
@justaugustus: 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. |
/assign |
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. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: 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. |
/remove-lifecycle rotten Working on a file promotion pattern for CRI tools in kubernetes/k8s.io#2663 and kubernetes/k8s.io#2624 (that I'll replicate for CNI). |
@justaugustus: 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. |
@justaugustus thanks for taking a look at this! I'll be on parental leave for a few months, but if you have any questions, feel free to reach out (or in #cni-dev on the CNCF slack). |
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 |
Originally opened by @rdodev:
Action items
Release Engineering
cni: Update CNI download URLs to use new GCS bucket (k8s-artifacts-cni) kubernetes#87562cni: Update CNI version to v0.8.5 kubernetes#78819) Update CNI fetch URLs in k/k to use new GCS bucket (gs://k8s-artifacts-cni
)k8s-infra-push-cni@kubernetes.io
) once CNI maintainers are updated - https://github.com/kubernetes/k8s.io/blob/c72a701bf6602560efbdaa0bb717f34c14f80a3f/groups/groups.yaml#L290-L299kubelet
deb/rpm package and deprecatekubernetes-cni
deb/rpm package - Deprecate kubernetes-cni deb/rpm packages release#885CNI plugins maintainers (containernetworking/plugins#446)
gs://k8s-artifacts-cni/release/
)The text was updated successfully, but these errors were encountered: