gt; >
>> > > > We want to be able to export any arbitrary application
>> > that we know
>> > > > nothing about :(
>> > > > Now we need to figure out which object were generated
>> > by OpenShift
>>
e to export any arbitrary application
> > that we know
> > > > nothing about :(
> > > > Now we need to figure out which object were generated
> > by OpenShift
> > > > internally and wh
uxOptions.level on ruby-hello-world does not
match required level. Found s0:c7,c4, wanted s0:c6,c0]
I'm doing it like this:
export:
$ oc new-project ruby-example
$ oc new-app
centos/ruby-22-centos7~https://github.com/openshift/ruby-hello-world.git
# after build finished
$ oc export all -l app=r
ted by developer.
> > > >
> > > >
> > > > You're introducing an additional requirement. :) Can you
> > confirm the
> > > > initial problem is resolved?
> > > >
> > >
> &
hich one were created by developer.
>> > >
>> > >
>> > > You're introducing an additional requirement. :) Can you
>> confirm the
>> > > initial problem is resolved?
>> > >
>> >
were generated
> by OpenShift
> > > internally and which one were created by developer.
> > >
> > >
> > > You're introducing an additional requirement. :) Can you
> confirm the
> > > initial prob
nd which one were created by developer.
> > >
> > >
> > > You're introducing an additional requirement. :) Can you confirm
> the
> > > initial problem is resolved?
> > >
> >
> > Not really, because I don't
rm the
> > initial problem is resolved?
> >
>
> Not really, because I don't know how application was deployed.
> My initial assumption that `oc export all` will somehow magically solve
> this for every application was wrong :(
> If I'm the
t; >
> > You're introducing an additional requirement. :) Can you confirm the
> > initial problem is resolved?
> >
>
> Not really, because I don't know how application was deployed.
> My initial assumption that `oc export all` will somehow magically solve
> th
resolved?
>
Not really, because I don't know how application was deployed.
My initial assumption that `oc export all` will somehow magically solve
this for every application was wrong :(
If I'm the one who deployed application than yes, I know what objects to
export. But if someone else cre
#x27;kubernetes.io/created-by: ...'
>>
>> Can we rely on those annotations to decide what to export and what to
>> leave behind? Is this documented somewhere?
>>
>>
>>
>>
>> On 03/14/2016 04:48 PM, Clayton Coleman wrote:
>> > Export is a
to export and what to
> leave behind? Is this documented somewhere?
>
>
>
>
> On 03/14/2016 04:48 PM, Clayton Coleman wrote:
> > Export is a lower level tool that does not *exactly* export an entire
> > application, but rather tries to give you the tools to bu
d it.
>
> I would suggest instead of running "oc export all", you try "oc export
> dc,svc,route,is". "all" includes pods, replication controllers,
> build configs, and builds, some of which you do not need. We expect
> at some point in the future to h
Hi,
Thanks for the reply,
- Original Message -
> From: "Aaron Weitekamp"
> To: "Tomas Kral"
> Cc: "dev" , "Suraj Deshmukh"
>
> Sent: Monday, March 14, 2016 9:16:17 PM
> Subject: Re: oc export
>
> On Mon, Mar 14, 2016 a
Export is a lower level tool that does not *exactly* export an entire
application, but rather tries to give you the tools to build it.
I would suggest instead of running "oc export all", you try "oc export
dc,svc,route,is". "all" includes pods, replication controll
On Mon, Mar 14, 2016 at 11:13 AM, Tomas Kral wrote:
> Hi all,
> I'm working on project where we are basically using `oc export` for
> exporting project and importing it to another OpenShift instance.
>
> But it is not working as I would expect.
>
> My understanding of
Hi all,
I'm working on project where we are basically using `oc export` for
exporting project and importing it to another OpenShift instance.
But it is not working as I would expect.
My understanding of export feature is that it can be used to move
objects between clusters or projects and
17 matches
Mail list logo
