OpenShift 3.6 Ingress Guest Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 23: Line 23:
{{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.}}
{{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.
=Other Configuration=


  192.168.122.10 in in.local lb lb.local
* Add the IP addresses for masters, other nodes, support and lb (itself) to /etc/hosts, the DNS server may not be operational when we need it.
  192.168.122.12 support support.local
 
  192.168.122.13 master1 master1.local
  192.168.122.22 ingress ingress.ocp36.local api-lb api-lb.ocp36.local
  192.168.122.14 master2 master2.local
  192.168.122.23 support support.ocp36.local ns ns.ocp36.local nfs nfs.ocp36.local ansible ansible.ocp36.local
  192.168.122.16 master3 master3.local
  192.168.122.24 master master.ocp36.local
  192.168.122.25 infranode infranode.ocp36.local
  192.168.122.26 node1 node1.ocp36.local
192.168.122.27 node1 node1.ocp36.local

Revision as of 03:03, 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.
Cloning a Guest

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.

Other Configuration

  • Add the IP addresses for masters, other nodes, support and lb (itself) to /etc/hosts, the DNS server may not be operational when we need it.
192.168.122.22 ingress ingress.ocp36.local api-lb api-lb.ocp36.local
192.168.122.23 support support.ocp36.local ns ns.ocp36.local nfs nfs.ocp36.local ansible ansible.ocp36.local
192.168.122.24 master master.ocp36.local
192.168.122.25 infranode infranode.ocp36.local
192.168.122.26 node1 node1.ocp36.local
192.168.122.27 node1 node1.ocp36.local
Retrieved from "https://kb.novaordis.com/index.php?title=OpenShift_3.6_Ingress_Guest_Configuration&oldid=30695"