aws-encryption-provider icon indicating copy to clipboard operation
aws-encryption-provider copied to clipboard

Release an official container

Open dominykas opened this issue 5 years ago • 14 comments

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 avatar Dec 08 '20 11:12 dominykas

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

fejta-bot avatar Mar 08 '21 12:03 fejta-bot

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

dominykas avatar Mar 23 '21 11:03 dominykas

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

fejta-bot avatar Apr 22 '21 11:04 fejta-bot

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

fejta-bot avatar May 22 '21 11:05 fejta-bot

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

k8s-ci-robot avatar May 22 '21 11:05 k8s-ci-robot

/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 avatar Mar 15 '23 15:03 micahhausler

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

rronsh avatar Apr 24 '23 16:04 rronsh

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!

dominykas avatar May 12 '23 12:05 dominykas

/assign

tarishij17 avatar Aug 24 '23 16:08 tarishij17

/assign

tarishij17 avatar Sep 10 '23 10:09 tarishij17

I can help on this @micahhausler @dims

xdu31 avatar Feb 01 '24 15:02 xdu31

go for it. thanks @xdu31

dims avatar Feb 01 '24 16:02 dims

Hi, any progress on this issue? Thanks

dezmodue avatar Sep 26 '24 20:09 dezmodue

/assign

phuhung273 avatar Oct 22 '24 11:10 phuhung273

I see this has been completed and merged, but nowhere in the docs can I find the location of the official container... can someone point me to it? Happy to open a PR to update the README, if I can only find the location...

dominykas avatar Jun 18 '25 06:06 dominykas