>
>
> *From:* users-boun...@lists.openshift.redhat.com <
> users-boun...@lists.openshift.redhat.com> *On Behalf Of *Samuel Martín
> Moro
> *Sent:* Freitag, 31. Mai 2019 20:43
> *To:* bjoern.baertsc...@swisscom.com
> *Cc:* OpenShift Users List
> *Subject:* Re: Issue by in
should be configured for openshift
> hosts. I thought about defining a network for external connection
> (internet) and a network for internal connection specific to openshift but
> I'm not sure is it ok...
>
>
>
> Regards, J
>
>
>
>
>
>
>
>
>
>
>
>
>
> k8s.io/client-go/informers/factory.go:130\n
> <http://k8s.io/client-go/informers/factory.go:130/n>
> ","stream":"stderr","time":"2019-05-24T12:19:13.747735832Z"}
> {"log":"I0524 14:19:13.745340 1 reflecto
2019 18:15
To: Jérôme Meyer
Cc: users@lists.openshift.redhat.com
Subject: Re: Issue by installing OKD OpenShift 3.11
Hi,
if you have master and etcd colocated on the same node, you should use
'node-config-master-infra' node group instead of 'node-config-master'.
Check the last 2 paragraphs of [1
nformers/factory.go:130/n>","stream":"stderr","time":"2019-05-24T12:19:13.747740084Z"}
{"log":"I0524 14:19:13.745907 1 reflector.go:133] Starting reflector
*v1beta1.ReplicaSet (0s) from
k8s.io/client-go/informers/factory.go:1
Hi,
As a general rule, you may want to check for the corresponding container
health and logs.
You won't find any apache or nginx listening. The process serving on :8443
is openshift, it should be started in a container.
Note that the master-api container, in charge of that service, closely rely
Hi,
if you have master and etcd colocated on the same node, you should use
'node-config-master-infra' node group instead of 'node-config-master'.
Check the last 2 paragraphs of [1].
Andrej
[1]
