Re: openshift-1.4.0.rc1 on EC2

Hi Thomas, EC2 does not add network interfaces with the public address to the VM; I think this is because public addresses are typically only associated with the instance while it's running. As a result, incoming traffic is NATted, with a private address that remains constant even while the VM

Re: PV manual reclamation and recyling

Thanks Clayton. Keep us posted. On Wed., 30 Nov. 2016 at 2:48 am, Clayton Coleman wrote: > It's likely, don't have an eta yet while the scope of the pick is assessed. > > On Thu, Nov 24, 2016 at 5:52 PM, Lionel Orellana > wrote: > > This is a pretty bad

Re: PV manual reclamation and recyling

It's likely, don't have an eta yet while the scope of the pick is assessed. On Thu, Nov 24, 2016 at 5:52 PM, Lionel Orellana wrote: > This is a pretty bad issue in Kubernetes. We are talking about deleting > data from NFS volumes. Lucky for me I'm just doing a POC. Is this

openshift-1.4.0.rc1 on EC2

Folks, I’m trying to install the openshift-1.4.0-rc1 binary on a RHEL7 instance on EC2 like this . When I access the console at https://52.214.39.204:8443/console, it loads forever and then returns

RE: Deployment error on node: Relabeling content in /usr is not allowed

Thanks Maciej. I’m trying hello-openshift now, and its also telling me it is privileged: Image openshift/hello-openshift runs as the root user which might not be permitted by your cluster administrator. I’m surprised a hello world image for openshift would run as root. Is that expected? I

Re: Deployment error on node: Relabeling content in /usr is not allowed

OpenShift, by default does not allow running privileged containers, and iirc guestbook does that: Handler for POST /containers/create returned error: Relabeling content in /usr is not allowed. I'd suggest starting of with hello-openshift [1] which although creates just a pod can be easily turned