Help regarding mounting hostPath volumes

2018-03-06 Thread Gaurav Ojha
Hi,

I would like some help from you guys if possible.

I am trying to mount a directory on my host machine to my OpenShift
instance.

As per the kubernetes document here
 , it
mentions that changing the pod spec by simply adding the hostPath volume
should work, however, when I do that,  OpenShift throws an error whereby it
says that I am not permitted to modify other than a few handful.

Is there any way to get this permission? I already have added set the
allowHostDirVolumePlugin to true and my containers run as root.

Any guidance on this would be appreciated.

Regards
Gaurav
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users


git caching for image build

2018-03-06 Thread Patrick Hemmer
Is there a way to implement some sort of git cache when building images?

When working locally (via minishift), on some of our projects the `git
clone` step of the build takes quite a while, especially over slow
links. This is compounded by the fact that we're using build chaining, a
"builder" image and a "runtime" Image, for which the Dockerfiles live in
the repo, and thus the repo gets cloned twice.

Thus it would be beneficial if there were some way to reduce the amount
of network traffic between openshift and the git repo.
If there were some way that openshift would use a persistent volume for
the repo, and perform a git fetch/pull instead of a full clone, then
that would work. Alternatively would be utilizing some sort of git
caching proxy. But not sure what options exist here.

Any suggestions on how to address the issue?

-Patrick
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users


Re: Re-Loading Console / API endpoint certificates

2018-03-06 Thread Clayton Coleman
Other than running an HA setup, no.

On Mar 6, 2018, at 12:56 AM, Alex Stockinger  wrote:

The certificates get properly picked up when I restart the origin docker
container, but I observed that this procedure seems to imply a short
downtime (when not running a HA setup).

Is there a way to have the daemon process pick up the new certificates
without a downtime in my scenario?

Clayton Coleman  schrieb am Di., 6. März 2018 um
02:30 Uhr:

> Even when you restart, you aren’t seeing the new certs loaded?
>
> On Mar 5, 2018, at 2:58 AM, Alex Stockinger  wrote:
>
> Hi,
>
> I am trying to secure my OpenShift installation's Console / API on port
> 8443 with let's encrypt certificates. I got this working nicely using the
> servingInfo/namedCertificates section in the master-config.yaml file.
> However upon certificate renewal the process doesn't seem to pick up the
> new certificates.
>
> So my question is: is there a (downtime-free) way to trigger a reload of
> the certificates used for port 8443?
>
> Thanks in advance for your help!
>
> Cheers,
> Alex
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users