etcdhealth probably is sufficient but in any case
I was recently wondering myself what etcdhealth measured + does it
gaurantee the nodes are consistent, synced, no split brain?
We used to do something like this:
curl -L -X PUT http://node1:2379/v2/keys/message -d value="ABCD"
&& curl -L
On Thu, Jan 12, 2017 at 8:36 PM, Clayton Coleman
wrote:
> Is git-lfs packaged in epel ben?
>
does not appear to be, no. There is a rhel package, but it's not produced
by us:
https://github.com/git-lfs/git-lfs/wiki/Installation#rhelcentos
>
> On Jan 12, 2017, at 4:10
Hi Karl.
you can use the passthrough mode and terminate the gRPC service with https
directly.
https://docs.openshift.org/latest/architecture/core_concepts/routes.html#secured-routes
=Passthrough Termination
This is the TCP mode you searching for ;-).
Hth
Aleks
On Fri, 13
You can check cluster health with etcdctl command, just run the following
command on one of yours etcd servers:
$ cd /etc/etcd/
$ etcdctl --cert-file peer.crt --key-file peer.key --ca-file ca.crt -C
https://:2379 cluster-health
---
Diego Castro / The CloudFather
GetupCloud.com - Eliminamos a
2017-01-10 20:17 GMT+01:00 Scott Dodson :
> openshift-ansible doesn't currently provide this, there's an issue
> requesting it https://github.com/openshift/openshift-ansible/issues/1772
> which links to a blog post describing how to do it, though I've not
> validated that
Hi,
ist it possible to run gRPC on Openshift?
As far as I understand gRPC uses HTTP/2 and the Openshift Router/Haproxy doesn't support HTTP/2
yet. Only way I can think of to make this work is modifying the Haproxy config to use "mode
tcp" instead of "mode http" which is the default. But the
2017-01-12 17:12 GMT+01:00 Alex Wauck :
> Are you using the built-in OpenShift etcd on that one node, or are you
> using real etcd?
>
I use registry.access.redhat.com/rhel7/etc standard docker OpenShift image.
Best regards,
Stéphane