OpenShift Runtime: Difference between revisions
Jump to navigation
Jump to search
| Line 36: | Line 36: | ||
In a non-HA deployment, the [[master api daemon]] and [[master controller daemon]] are coalesced in a single process. | In a non-HA deployment, the [[master api daemon]] and [[master controller daemon]] are coalesced in a single process. | ||
==master | ===master controller Daemon=== | ||
== | ===master api Daemon=== | ||
= | |||
=== | |||
=Regular Node= | =Regular Node= | ||
==node Daemon== | ==node Daemon== | ||
Revision as of 20:21, 17 May 2017
Internal
Master Node
The master node runs, in order, these services:
The master daemon (or daemons) must be started after etcd is started, they depend on etcd.
etcd Daemon
Unit: etcd.service
Unit File: /usr/lib/systemd/system/etcd.service
Working Directory: /var/lib/etcd
Configuration File: /etc/etcd/etcd.conf
Process:
/usr/bin/etcd --name=master1.rdu20.internal --data-dir=/var/lib/etcd/ --listen-client-urls=https://192.199.0.199:2379
master Daemons
In a non-HA deployment, the master api daemon and master controller daemon are coalesced in a single process.