new behavior of `kompose up` about kompose HOT 11 CLOSED

As kompose supports more than one provider, we should have --provider flag like this:

kompose up --provider openshift

Default: Kubernetes (without --provider).

from kompose.

I've started working on adding kompose up for openshift.
I will brake it to multiple PRs and in every PR I'm going to reference this issue.

from kompose.

Also, print suggestion to use kubectl to deploy other controllers and include non-supported fields warning

from kompose.

Reopen it for further enhancement:

• add --provider flag
• handling invalid converted k8s object

from kompose.

@surajssd how can kompose read OpenShift endpoint config ?

from kompose.

@ngtuna OpenShift endpoint config as in similar to ~/.kube/config ?

from kompose.

Really? OK so I'm thinking how we can add kompose up --provider openshift. What is the process ? We need to have a ~/.kube/config pre-configured to openshift endpoint. Then let kompose does the same with kubernetes. Does it make sense ?

from kompose.

I even think that we can use same deploy function (from kubernetes) for deploying to OpenShift.
We just need to make sure that proper api all installed such as (_ "github.com/openshift/origin/pkg/deploy/api/install")
We might change that to _ "github.com/openshift/origin/pkg//api/install" to make sure that all openshift objects are included in schema

from kompose.

Ah.... I remember we discussed about preference file at #39. So, if the preference file is used, we don't need --provider anymore, right ?

from kompose.

I think this can be closed now?

from kompose.

Yes

from kompose.