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

Support converting OpenShift json <-> Kubernetes json/yaml #219

Closed
rothgar opened this issue Oct 19, 2016 · 16 comments
Closed

Support converting OpenShift json <-> Kubernetes json/yaml #219

rothgar opened this issue Oct 19, 2016 · 16 comments

Comments

@rothgar
Copy link
Member

rothgar commented Oct 19, 2016

As a user I'd like to use OpenShift json files or Kubernetes yaml files to convert manifests from one environment to the other. This seems like it would be easier to support than docker-compose files but currently is a manual process (as far as I've found).

Maybe I missed an existing issue or PR (I searched) but this would be a great addition for both communities.

@sebgoa
Copy link
Contributor

sebgoa commented Oct 19, 2016

just to confirm, instead of transforming from docker formats to k8s/openshift, you would like to transform from openshift to k8s ?

@rothgar
Copy link
Member Author

rothgar commented Oct 19, 2016

Correct. That is my initial goal, but I could also see a use case to switch from k8s manifests -> openshift

@kadel
Copy link
Member

kadel commented Oct 20, 2016

Hi,
regarding k8s->openshift you don't need any conversion, everything that works on k8s should work on OpenShift by default.

Other way is problematic. OpenShift is superset of k8s. For most objects it will be ok (because they are same in openshift and k8s), but there are objects in OpenShift that cannot be easily mapped to Kubernetes, for example BuildConfig.

Theoretically it can be done (to some degree), but I don't think that it is something that is in scope for Kompose.

@rothgar
Copy link
Member Author

rothgar commented Oct 20, 2016

If it's out of scope that is fine (we can close this issue) I just think it may be a use case for some people. Me being one of those people where I often translate OpenShift -> Kubernetes manifests manually. It could help broaden available applications for both OpenShift and vanilla Kubernetes

@smarterclayton
Copy link

@rothgar this has come up a few times in OpenShift as well. Even if we don't want to do it here, I'd be open to implementing it in the OpenShift CLI or another command. I agree the idea of:

deployment config -> deployment
route -> ingress

and vice versa would be very useful.

@rothgar
Copy link
Member Author

rothgar commented Oct 20, 2016

I assumed kompose would be the tool to do the conversions. It'd be nice if I didn't need oc or multiple conversion tools for each scenario.

@sebgoa
Copy link
Contributor

sebgoa commented Oct 21, 2016

@rothgar let's definitely keep this issue open. We talked about supporting other input formats (like nomad Jobs) for example, so we could add openshift -> k8s conversion.

And I agree that having only one conversion tool would be better.

@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@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 Dec 18, 2017
@cdrage
Copy link
Member

cdrage commented Dec 18, 2017

@fejta-bot @fejta How do I remove / whitelist the Kompose repo from this bot?

@fejta
Copy link

fejta commented Dec 19, 2017

Move it out of the kubernetes org

@kadel
Copy link
Member

kadel commented Dec 19, 2017

@cdrage I think that this bot will be useful

@cdrage
Copy link
Member

cdrage commented Dec 19, 2017

@fejta Okay, we'll keep it around 👍

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

@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 Jan 18, 2018
@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-testing, kubernetes/test-infra and/or fejta.
/close

@surajnarwade
Copy link
Contributor

/remove-lifecycle rotten

@surajnarwade surajnarwade reopened this Mar 6, 2018
@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 6, 2018
@cdrage
Copy link
Member

cdrage commented Mar 6, 2018

Since there's been no activity since December and this has (mainly) been used as a Docker Compose to Kubernetes / OpenShift tool, I'm going to close this (for now).

@cdrage cdrage closed this as completed Mar 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants