Re: ImageStream loses tags when exported

2016-04-01 Thread Tomas Nozicka
"ruby-hello-world" the > > tags > > survive export/import just fine: > > $ oc export is ruby-hello-world --namespace=original-project | oc > > create -f - --namespace=import > > > > $ oc describe is ruby-hello-world --namespace=import > > Nam

Re: BuildConfig+ImageStream question

2016-04-01 Thread Tomas Nozicka
On Pá, 2016-04-01 at 10:16 -0400, Ben Parees wrote: > > > On Fri, Apr 1, 2016 at 9:13 AM, Tomas Nozicka <tnozi...@redhat.com> > wrote: > > Hi, > > > > let's say we have an ImageStream with the following definition: > > spec: > >   dockerIm

Re: How to specify ImageStream as a source for container

2016-05-19 Thread Tomas Nozicka
For the record: https://github.com/openshift/origin/issues/8937 On St, 2016-05-18 at 08:13 -0400, Clayton Coleman wrote: > Please file an issue for that on github. > > > > > On May 18, 2016, at 7:58 AM, Tomas Nozicka <tnozi...@redhat.com> > > wrote: > >

Re: How to specify ImageStream as a source for container

2016-05-17 Thread Tomas Nozicka
me proper solution? On Út, 2016-05-17 at 10:04 -0400, Clayton Coleman wrote: > Set image to " " > > On Tue, May 17, 2016 at 9:54 AM, Tomas Nozicka <tnozi...@redhat.com> > wrote: > > > > I am not able to specify ImageStream as source of what my contai

How to specify ImageStream as a source for container

2016-05-17 Thread Tomas Nozicka
I am not able to specify ImageStream as source of what my container is run from in my DeploymentConfig. I can only specify image there [1] but not ImageStream. But when I setup triggers for DeploymentConfig I can specify ImageStream in form of ImageStreamTag.  So the #1 deployment is from an

Re: How to specify ImageStream as a source for container

2016-05-18 Thread Tomas Nozicka
t 10:56 -0400, Clayton Coleman wrote: > There is a work going on to ensure that you don't get a failure for > the first case. > > On Tue, May 17, 2016 at 10:16 AM, Tomas Nozicka <tnozi...@redhat.com> > wrote: > > > > This way you will end up with deployment #2 and

Re: Let's Encrypt controller for OpenShift

2017-02-20 Thread Tomas Nozicka
some more... Regards, Tomas [1] - https://github.com/tnozicka/openshift-acme#deploy [2] - https://github.com/tnozicka/openshift-acme/blob/master/docs/desig n/architecture.adoc#supported-objects On Mon, 2016-11-28 at 14:15 +0100, Tomas Nozicka wrote: > Thanks you all for the feedback

Re: Let's Encrypt controller for OpenShift

2017-02-23 Thread Tomas Nozicka
at.com[10.4.122.10] said: 550 5.1.1 <d...@redhat.com>... User unknown (in reply to RCPT TO command) === Re-sending to dev@lists.openshift.redhat.com On Fri, 2017-02-24 at 06:33 +0100, Tomas Nozicka wrote: > Hi Luke, > > thanks for your feedback. > > (see inline) > > On Thu

Re: Let's Encrypt controller for OpenShift

2016-11-28 Thread Tomas Nozicka
firewall, VPN) - Automated certificate renewal Regards, Tomas [10] - https://github.com/kelseyhightower/kube-cert-manager [11] - https://github.com/jetstack/kube-lego On Thu, 2016-11-24 at 14:35 +0100, Tomas Nozicka wrote: > I've been thinking for a long time about some kind of support for >

[Fwd: OpenCompose - A higher level abstraction to define applications for Kubernetes]

2017-03-06 Thread Tomas Nozicka
Hi all, I just wanted to let you know that we have rebooted the OpenCompose project.  The goal of OpenCompose is to make it easier for developers to on-board to Kubernetes using declarative higher level abstraction for specific Kubernetes resources. (We will support specific OpenShift

Re: when delete deployment via rest api, corresponding rs and pod not deleted

2019-01-02 Thread Tomas Nozicka
You are likely not specifying deleteOptions for the API call and thus defaulting to orphaning. You want propagationPolicy to be Foreground or Background, not the default Orphan. Note that the default propagationPolicy also depends on Deployment API version in question, I think since GA Orphan is

Re: Route frontend not being updated

2019-04-15 Thread Tomas Nozicka
First namespace claiming a particular domain wins, otherwise other tenants on the cluster could steel the traffic. On Mon, 2019-04-15 at 10:33 +0200, Iago Santos wrote: > Hi, > > I am running 3.11 okd and I got several errors during the deletion > and creation of some routes, in this case I got