Openshift 4 Blue green deployment at HomeLab

Try to deploy two openshift separate clusters in homelab. Remember in OCP3, 1 master and 2 workers can work perfectly in one single PC. Openshift 4 need more on resource and here is minimum requirement.

Minimum resource requirements

Each cluster machine must meet the following minimum requirements:

MachineOperating SystemvCPUVirtual RAMStorage

Bootstrap

FCOS

4

16 GB

120 GB

Control plane

FCOS

4

16 GB

120 GB

Compute

FCOS or RHEL 7.6

2

8 GB

120 GB    

https://docs.okd.io/latest/installing/installing_bare_metal/installing-bare-metal.html

For minimum installation require 1 Bootstrap, 3 control plane and 2 compute nodes. total vcpu: 20 and 80GB RAM. It is better to have 10 cores (1:2). 

Lab Environment:

Just upgrade one of my server to Intel(R) Xeon(R) CPU E5-2650L v3 @ 1.80GHz (2nd hand). It is good enough to run openshift in VMware. (12 cores, 96GB RAM)

URL: https://console-openshift-console.apps.green.hkopenshift.com/dashboards


On the other hand, I have two servers to create in RHV cluster with GlusterFS shared storage.

One PC is Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz with 32GB RAM about 10 years old. (4 cores)

Another supermicro Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz CPU with 128GB RAM. Because limited CPU resource, it never finish installation on its own. (4 cores)

With total 8 cores, barely can install with some troubleshooting, fix timeout issue, CSR not auto signed, etc. For disk IO, the following tuning help a lot on disk performance. Finally, at least we have the console running and can deploy application on it.

Gluster volume: (applied using gluster volume set <volume> group virt): disable quick-read, read-ahead, io-cache translatorsenable eager-lock, remote-dio volume parameters

https://access.redhat.com/sites/default/files/attachments/rhev-gluster-128-guests_0.pdf






Example of warning related to limited resource.
etcd cluster "etcd": 8.571428571428571 leader changes within the last 15 minutes. Frequent elections may be a sign of insufficient resources, high network latency, or disruptions by other components and should be investigated.

URL: https://console-openshift-console.apps.blue.hkopenshift.com/

"Blue" "green" deployment example. We can deploy application on two OCP and use the external load balancer (or DNS) to control traffic to the app. As the infrastructure(VMware and RHV) is total different and isolated, change on one platform will not affect another.


Small modify on example of hello world, just for demo.

https://github.com/bluesky255255/openshift-php-hello-world

#Openshift

#homelab

Deploy method IPI, Tested Version, OCP 4.6


Comments

Popular posts from this blog

Openshift cert-manager integrate with ACME IdM on RHEL (Technical Preview)

TimeSync using ansible and rhel-system-roles.timesync

Remove HPE iLO license