I'm very interested in this as well, as I'd like to use it in classes I'm
teaching on OpenShift.
Let's keep a very strict separation between types of traffic. There's the
traffic between nodes (kubelet,) master API servers, and components such as
logging and metrics. That's on the *.internal
That's interesting, and a very different approach to what I was
anticipating using the Ansible playbooks.
Any thoughts from anyone on what is the best approach for this?
Any other approaches/experiences on how to handle this important issue?
Tim
On 25/08/2017 17:09, Tomas Nozicka wrote:
Hi
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
Does anyone have any experience on how best to use Let' Encrypt
certificates for an OpenShift Origin cluster?
In once sense this is simple. The Ansible installer can be specified to
use this custom certificate and key to sign all the certificates it
generates, and doing so ensures you don't
Thanks. That PR seems to fix it.
Tim
On 25/08/2017 14:55, Scott Dodson wrote:
I think we broke this recently, can you try this PR?
https://github.com/openshift/openshift-ansible/pull/5178
On Fri, Aug 25, 2017 at 9:20 AM, Tim Dudgeon >
Thanks, I figured out how to do it.
In case someone wants to the same thing:
oc get pods -o custom-columns=NAME:.metadata.name,Ready:status.
containerStatuses[0].ready
This will list all the pods with readiness status
NAME Ready
pod-1 true
Are there any plans to include this in OpenShift?
https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md
___
users mailing list
users@lists.openshift.redhat.com