Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CNI plugins (kubernetes-cni) build and packaging process improvements #245

Open
8 of 11 tasks
rdodev opened this issue Jul 31, 2018 · 37 comments
Open
8 of 11 tasks

CNI plugins (kubernetes-cni) build and packaging process improvements #245

rdodev opened this issue Jul 31, 2018 · 37 comments
Assignees
@justaugustus @thockin @dcbw
Labels
area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
Artifact Management (SIG Release)
Milestone
v1.24

Comments

@rdodev
Copy link

rdodev commented Jul 31, 2018 •
edited by LappleApple

Originally opened by @rdodev:

Presently both bazel builds and release-related scripts build debs and rpms via a tarball downloaded from google object store. I've not seen or found any documentation or code that explains how this tarball is built. Would like if not the script(s) used to build and create the tarball at least a detailed description how to go about manually building it.

Action items

Release Engineering

CNI plugins maintainers (containernetworking/plugins#446)
@justaugustus
Copy link
Member

Can someone pick this up?
/help
ping @kubernetes/sig-release-feature-requests

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. kind/feature Categorizes issue or PR as related to a new feature. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Aug 17, 2018
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 15, 2018
@idealhack
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 15, 2018
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 13, 2019
@rdodev
Copy link
Author

rdodev commented Feb 13, 2019

Given lack of engagement on this ticket, I'm going to close it.

@rdodev rdodev closed this as completed Feb 13, 2019
@justaugustus
Copy link
Member

...well this seems like something we still need to do given last cycle's kerfuffle.
/reopen
/remove-lifecycle stale
/milestone v1.15
/priority important-soon

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Reopened this issue.

In response to this:

...well this seems like something we still need to do given last cycle's kerfuffle.
/reopen
/remove-lifecycle stale
/milestone v1.15
/priority important-soon

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.

@k8s-ci-robot k8s-ci-robot reopened this Apr 24, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone Apr 24, 2019
@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 24, 2019
@justaugustus justaugustus added this to To do in SIG Release via automation Apr 24, 2019
@justaugustus justaugustus added this to To do in Release Team via automation May 1, 2019
@justaugustus justaugustus removed this from To do in SIG Release May 1, 2019
@justaugustus justaugustus mentioned this issue May 1, 2019
Closed
@justaugustus justaugustus moved this from Backlog to To do in Release Team May 6, 2019
@justaugustus justaugustus mentioned this issue Jun 6, 2019
Closed
@justaugustus
Copy link
Member

/assign
/remove-help
/milestone v1.16

@k8s-ci-robot k8s-ci-robot removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Jun 10, 2019
@k8s-ci-robot k8s-ci-robot modified the milestones: v1.15, v1.16 Jun 10, 2019
@justaugustus justaugustus mentioned this issue Jun 10, 2019
Merged
@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Feb 7, 2021
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 8, 2021
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 7, 2021
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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 justaugustus modified the milestones: v1.20, v1.23 Sep 7, 2021
@justaugustus
Copy link
Member

/remove-lifecycle rotten
/reopen

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).

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

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).

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.

@k8s-ci-robot k8s-ci-robot reopened this Sep 7, 2021
@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 7, 2021
@justaugustus justaugustus added the area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects label Sep 7, 2021
@justaugustus justaugustus added this to Backlog in Artifact Management (SIG Release) via automation Sep 7, 2021
@justaugustus justaugustus moved this from Backlog to In Progress in Artifact Management (SIG Release) Sep 7, 2021
@squeed
Copy link

squeed commented Sep 8, 2021

@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).

@justaugustus justaugustus mentioned this issue Oct 5, 2021
Merged
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 7, 2021
@justaugustus
Copy link
Member

/remove-lifecycle stale
/lifecycle frozen
/milestone v1.24

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 13, 2021
@k8s-ci-robot k8s-ci-robot modified the milestones: v1.23, v1.24 Dec 13, 2021
@caseydavenport caseydavenport removed their assignment Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justaugustus justaugustus

@thockin thockin

@dcbw dcbw

Labels
area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
No open projects
Artifact Management (SIG Release)
  
In Progress
Milestone
v1.24
Development

No branches or pull requests