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

Release an official container #71

Open
dominykas opened this issue Dec 8, 2020 · 12 comments
Open

Release an official container #71

dominykas opened this issue Dec 8, 2020 · 12 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@dominykas
Copy link

dominykas commented Dec 8, 2020 •
edited

What would you like to be added:

I'd like to use a pre-built container of this provider. I know this was requested before, twice... But maybe things have changed since? I'm also happy to contribute this.

Why is this needed:

Lower barrier for usage, if you can just use an existing one.

Happy to PR a GH workflow which would publish a latest on every push to master into the GH registry on this repo?

Also happy to PR whatever is needed to publish tagged releases, if there's someone willing to walk through the preferred workflow/requirements.
@dominykas dominykas added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 8, 2020
@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 Mar 8, 2021
@dominykas
Copy link
Author

I can see a relevant PR #72 got merged - is there anything I can do to help move this forward?

@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 Apr 22, 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.

@micahhausler
Copy link
Member

/reopen
/remove-lifecycle rotten

For anyone willing to help out, we'd appreciate community contribution here. The work involved requires following the guide in kubernetes/k8s.io and starts out by making a PR to that repo similar to kubernetes/k8s.io#2274 (owner references would be the folks listed in this repos OWNERS_ALIASES)

@micahhausler micahhausler reopened this Mar 15, 2023
@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 Mar 15, 2023
@micahhausler micahhausler added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Mar 15, 2023
@rronsh
Copy link

rronsh commented Apr 24, 2023

@dominykas are you working on this issue? If not I can try to give this a go.

@dominykas
Copy link
Author

dominykas commented May 12, 2023 •
edited

I'm not working on this, no - I missed the response, but I'm also not able to take this right now, so please do!

@tarishij17
Copy link

/assign

@tarishij17 tarishij17 removed their assignment Sep 9, 2023
@tarishij17
Copy link

/assign

@tarishij17 tarishij17 mentioned this issue Sep 10, 2023
Closed
@xdu31
Copy link
Contributor

xdu31 commented Feb 1, 2024

I can help on this @micahhausler @dims

@tarishij17 tarishij17 removed their assignment Feb 1, 2024
@dims
Copy link
Member

dims commented Feb 1, 2024

go for it. thanks @xdu31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@dims @dominykas @micahhausler @k8s-ci-robot @rronsh @fejta-bot @xdu31 @tarishij17