OpenShift 3.6 Ingress Guest Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (12 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
=Clone the Basic Template= | =Clone the Basic Template= | ||
Use the [[OpenShift_3.6_Basic_Guest_Template#Overview|basic template]] as a base image and clone it, as described | Use the [[OpenShift_3.6_Basic_Guest_Template#Overview|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. | |||
{{Internal|Linux Virtualization Cloning a KVM Guest Virtual Machine|Cloning a Guest}} | {{Internal|Linux Virtualization Cloning a KVM Guest Virtual Machine|Cloning a Guest}} | ||
The process will produce a ocp36.ingress. | 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. | |||
{{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.}} | |||
=Name Resolution= | |||
* 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 | |||
=HAProxy= | |||
Make sure HAProxy is installed. It will be configured by the OpenShift installation utility, later. | |||
yum list | grep haproxy | |||
=Create the Key for Internal Users= | |||
cd ~ovidiu | |||
ssh-keygen -q -b 2048 -f ~/.ssh/id_rsa -t rsa | |||
Latest revision as of 03:58, 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.
Name Resolution
- 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
HAProxy
Make sure HAProxy is installed. It will be configured by the OpenShift installation utility, later.
yum list | grep haproxy
Create the Key for Internal Users
cd ~ovidiu ssh-keygen -q -b 2048 -f ~/.ssh/id_rsa -t rsa