Operator-sdk: Official docker image for cli
Feature Request
Is your feature request related to a problem? Please describe.
Provide a versioned docker container for using the operator-sdk CLI
Describe the solution you'd like
Same as above, docker container with the binary in it. Lots of people have created these https://hub.docker.com/search?q=operator-sdk&type=image
drewwells
All 12 comments
/assign @bharathi-tenneti
bharathi-tenneti
on 5 Nov 2019
@drewwells Can you present your usecase, for this Docker image request. Depending on the usecases, we will consider creating/maintaining officialdocker image for SDK.
bharathi-tenneti
on 4 Dec 2019
A use case I have for this to use the SDK CLI in a CI pipeline to build an operator image. We use docker on CI nodes to run build tools, rather than install the tools directly.
We use a third party image now, but would certainly prefer an officially maintained image.
micahlee
on 30 Dec 2019
@joelanford is point of contact for this issue.
bharathi-tenneti
on 19 Mar 2020
since operator-sdk build relies on docker it can become a bit tricky.
davidkarlsen
on 26 Apr 2020
just to register +1 shows be looking for it in https://github.com/operator-framework/operator-sdk/issues/2978
camilamacedo86
on 6 May 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
openshift-bot
on 4 Aug 2020
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
openshift-bot
on 3 Sep 2020
/lifecycle frozen
joelanford
on 4 Sep 2020
docker in docker has been around for a long time, it is not challenging to support https://www.docker.com/blog/docker-can-now-run-within-docker/
Even if the docker calls failed, it would be a major improvement to support specific versions of operator-sdk from docker cli. As mentioned above, we need to be able to build CICD pipelines on stable versions of applications. Having an operator-sdk docker image will be very useful to us.
Please reopen, this is still needed.
drewwells
on 21 Oct 2020
Re-opened add move to 1.2.0 since the 1.1.0 is released already 馃憤
c/c @asmacdo
camilamacedo86
on 21 Oct 2020
This was completed in 1.1 and the operator-SDK image is now available at quay.io/operator-framework/operator-sdk:v1.1.0
joelanford
on 22 Oct 2020
Related issues
danielsig727
路
4Comments
camilamacedo86
路
4Comments
kristiandrucker
路
5Comments
ffoysal
路
3Comments
flickerfly
路
5Comments
Most helpful comment
A use case I have for this to use the SDK CLI in a CI pipeline to build an operator image. We use docker on CI nodes to run build tools, rather than install the tools directly.
We use a third party image now, but would certainly prefer an officially maintained image.