-
Notifications
You must be signed in to change notification settings - Fork 772
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
Docker build in kompose convert #691
Comments
@hrishin , try this |
@cdrage , but I can see |
@surajnarwade Woops, let me clarify, As to why build/push wasn't enabled by default when added to convert 👍 |
@cdrage @surajnarwade So are we going to release this feature in next release? |
@hrishin Yup! We just graduated (hence why we're in Kubernetes land now) and haven't made the announcement yet, but we will be coinciding the graduation blog post with a 1.0.0 release! |
@surajnarwade Once 1.0.0 is out the issue is solved and we can close this. |
@hrishin can you verify with the latest release that your issue is solved? |
Yes its resolved now, thanks! 👍 |
kompose convert
provides nice utility for converting docker-compose resources to kubenetes resources. However while leveraging on it if compose file hasbuild:
tag, so converting those resources to kubernates resources wont help much in our case as another system expects docker image do exists in respective registry prior bringing kubenetes deployment up and running.It would be great if we can add optional flag in
kompose convert -b
so on presence of itkompose
can build docker images, push it to respective registry and the execute conversation process as a whole.As of now I can see this functionality is available in
kompose up
command but we don't want to spin up the pods/containers.The text was updated successfully, but these errors were encountered: