There is also https://github.com/tnozicka/openshift-acme
Regards,
Tomas
On Fri, 2017-07-07 at 09:13 +0200, Aleksandar Lazic wrote:
> Hi Hetz Ben Hamo.
>
> on Freitag, 07. Juli 2017 at 00:48 was written:
>
>
> https://arstechnica.com/information-technology/2017/07/lets-encrypt-t
>
should work as described in our docs.
https://github.com/tnozicka/openshift-acme/blob/master/.travis.yml#L6
7-L73
>
> Thanks
> Tim
>
>
>
> On 04/09/2017 09:44, Tomas Nozicka wrote:
> > Hi Tim,
> >
> > On Mon, 2017-09-04 at 09:16 +0100, Tim Dudge
Hi Tim,
there is a controller to take care about generating and renewing Let's
Encrypt certificates for you.
https://github.com/tnozicka/openshift-acme
That said it won't generate it for masters but you can expose master
API using Route and certificate for that Route would be fully managed
by
ld work fine even for 'oc' client
unless the Router is down and you need to fix it. For that rare case,
when only the admin will need to log in to fix the router he can use
the internal cert or ssh into the cluster directly.
So this hack should cover all the use cases for users except this
special case
I need to direct Route/Service traffic from one namespace to another
which I have permissions to. (Possibly even the same namespace as
well.) Reading Kubernetes documentation[1] Services without selectors
seem to be the way to do it. It requires you to set Endpoints manually
(e.g. to Service or
on’t work.
>
> You can also grant that permission to all users if you don’t need the
> protection.
>
> > On Jan 30, 2018, at 3:18 PM, Tomas Nozicka <tnozi...@redhat.com>
> > wrote:
> >
> > I need to direct Route/Service traffic from one namespace to
> >
On Wed, 2018-02-21 at 14:43 +0200, Dan Pungă wrote:
> Hello all!
>
> Trying to build an OShift configuration for running a Java app with a
> Wildfly server.
> I've setup this with ChainBuilds where the app's artifacts are
> combined with a runtime image of Wildfly.
>
> For this particular app,
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,
I haven't tried messing with that but the reason is that console is
served from apiserver.
But depending on what you are trying to achive, you can wrap the
console (and apiserver) with a Route and get free http certificates
from Let's Encrypt like this: