OpenShift 3.6 Ingress Guest Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
* Turn off external root access. | * Turn off external root access. | ||
{{Warn|There is no need to install HAProxy manually to serve as master node load balancer, the OpenShift installation procedure will do it.}} | {{Warn|There is no need to install HAProxy manually to serve as master node load balancer, the OpenShift installation procedure will do it. After that, we can use the same HAProxy instance to load balance to the application router.}} | ||
* Add the IP addresses for masters, support and lb (itself) to /etc/hosts, the DNS server may not be operational when we need it. | * Add the IP addresses for masters, support and lb (itself) to /etc/hosts, the DNS server may not be operational when we need it. | ||
Revision as of 02:50, 9 November 2017
Internal
Clone the Basic Template
Use the basic template as a base image and clone it, as described below.
While cloning the guest, make sure to:
- Adjust the memory and the number of virtual CPUs.
- Provision a directly-mapped network interface.
- Provision just one storage device - the guest image device.
The process will produce a ocp36.ingress.
External Access Configuration
- Create external accounts to be exposed publicly and configure their ssh access (~/.ssh/authorized_keys).
- Turn off external root access.
There is no need to install HAProxy manually to serve as master node load balancer, the OpenShift installation procedure will do it. After that, we can use the same HAProxy instance to load balance to the application router.
- Add the IP addresses for masters, support and lb (itself) to /etc/hosts, the DNS server may not be operational when we need it.
192.168.122.10 in in.local lb lb.local 192.168.122.12 support support.local 192.168.122.13 master1 master1.local 192.168.122.14 master2 master2.local 192.168.122.16 master3 master3.local