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.

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

Compose-on-kubernetes and kompose #1086

Open
Vad1mo opened this Issue Dec 5, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@Vad1mo
Copy link

commented Dec 5, 2018

Docker just announced to open source their compose to kubernetes tool.

https://github.com/docker/compose-on-kubernetes

my question is, how does this announcement impact this project and it future and maybe it position?

@cdrage

This comment has been minimized.

Copy link
Member

commented Dec 5, 2018

@Vad1mo

No impact on future plans, we will continue to improve and release new Kompose versions.

Due to slow-down in activity with Docker Compose, Kompose isn't as popular as it used to be during Docker Compose's hype, however, that won't impact the projects position.

Kompose has done it's job for creating an excellent tool for Docker Compose to Kubernetes conversion during the great transition to Kubernetes.

As long as Docker continues to release new Docker Compose version's and supporting it, Kompose will be there! 💯

@Vad1mo

This comment has been minimized.

Copy link
Author

commented Dec 5, 2018

Adding the information you posted to the README would be great for others to relate.

@fejta-bot

This comment has been minimized.

Copy link

commented Mar 5, 2019

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

@fejta-bot

This comment has been minimized.

Copy link

commented Apr 4, 2019

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-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.