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
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
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 resources
2.10] said:
550 5.1.1
... 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, 2017-02-23 at 14:55 -0500, Luk
ir client-go
ready
- probably 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 yo
or being behind 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
I've been thinking for a long time about some kind of support for Let's
Encrypt [1] in OpenShift. In the meantime Kelsey Hightower came with
his PoC for Kubernetes [2]. It's a great starting point although it
will need modifications to work with OpenShift's router. Actually I
thing that in combinat
716) 870-2408
> > > > >
> > > > > > > > > > On August 15, 2016 at 1:26:27 AM, Andrew Lee Rubinger
> > > > > > > > > > (a...@redhat.com) wrote:
> > > > > > +1 from me; it solves a user need in
t; >
>
> I don't believe that would make sense for this case; it's a true
> request/response event model, not an open channel of continuous information
> exchange.
>
> S,
> ALR
>
> >
> > -Todd
> >
> > On Fri, Au
+continuous-...@redhat.com
On Pá, 2016-08-05 at 22:23 +0200, Tomáš Nožička wrote:
> Hi,
>
> I am working on pipelines for OpenShift and Catapult, and we are trying
> to setup full CI/CD experience for users on their laptops.
>
> One thing we have encountered is the need for hooks forwarding behi
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
> > wrote:
> >
> > It's goo
-17 at 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
> wrote:
> >
> > This way you will end up with deployment #2 and failed #1 wit
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
> wrote:
> >
> > I am not able to specify ImageStream as source of what my container
> > is
> > run fr
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 image
On Pá, 2016-04-01 at 10:16 -0400, Ben Parees wrote:
>
>
> On Fri, Apr 1, 2016 at 9:13 AM, Tomas Nozicka
> wrote:
> > Hi,
> >
> > let's say we have an ImageStream with the following definition:
> > spec:
> > dockerImageRepository: centos/ruby-22-
uby-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
> > Name:ruby-hello
downloaded the image in
the first place or is it correct to get this error?
Thanks,
Tomas Nozicka
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
17 matches
Mail list logo