Skip to main content

OKD - Create a Homelab OKD Cluster - Keepalived

We'll be working on the Servers that are surrounded by the continous lines in this drawing:

Keepalived is a useful tool to share a single Virtual IP (VIP) between multiple nodes without dealing with pacemaker, corosync and fencing. Keepalived is also fairly lightweight and easy to configure, so a good fit four this setup.

Start by installing keepalived:

 [archy@helper01 ~]$ sudo dnf -4y --refresh install keepalived  
 [archy@helper02 ~]$ sudo dnf -4y --refresh install keepalived  

After the packages are done installing, configure keepalived on the first helper node:

 [archy@helper01 ~]$ sudo vim /etc/keepalived/keepalived.conf  
 ! Configuration File for keepalived  
 global_defs {  
   notification_email {  
     admins@archyslife.lab  
   }  
   notification_email_from root@helper01.okd.archyslife.lab  
   smtp_server 127.0.0.1  
   smtp_connect_timeout 30  
   script_user root root  
 }  
 vrrp_script chk_haproxy {  
   script '/usr/bin/pidof haproxy'  
   interval 2  
 }  
 vrrp_instance VI_1 {  
   state MASTER  
   interface enp1s0  
   priority 100  
   virtual_router_id 51  
   unicast_src_ip 172.31.10.173  
   unicast_peer {  
      }  
   authentication {  
     auth_type PASS  
     auth_pass 8-character-secret-here  
   }  
   track_script {  
     chk_haproxy  
   }  
   virtual_ipaddress {  
     172.31.10.240  
   }  
 }  

Restart keepalived on the first node to check if the keepalived configuration works as expected. If the check returns with rc 0, the node will be considered eligible for the virtual ip address (172.31.10.240)

 [archy@helper01 ~]$ sudo systemctl enable --now keepalived.service  

Check for IP Addresses:

 [archy@helper01 ~]$ ip -s -c -h -4 addr show enp1s0  
 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000  
   inet 172.31.10.173/24 brd 172.31.10.255 scope global dynamic noprefixroute enp1s0  
     valid_lft 223503sec preferred_lft 223503sec  
   inet 172.31.10.240/32 scope global enp1s0  
     valid_lft forever preferred_lft forever  
   RX: bytes packets errors dropped missed  mcast        
      33.5G  44.9M   0    1    0    0   
   TX: bytes packets errors dropped carrier collsns        
      33.4G  44.5M   0    0    0    0   
Okay, so the IP has been successfully assigned. The Configuration is correct and we can configure the next helper node.
Keepalived has already been installed in a previous step so we'll start with the configuration here:
 [archy@helper02 ~]$ sudo vim /etc/keepalived/keepalived.conf  
 ! Configuration File for keepalived  
 global_defs {  
   notification_email {  
     admins@archyslife.lab  
   }  
   notification_email_from root@helper02.okd.archyslife.lab  
   smtp_server 127.0.0.1  
   smtp_connect_timeout 30  
   script_user root root  
 }  
 vrrp_script chk_haproxy {  
   script '/usr/bin/pidof haproxy'  
   interval 2  
 }  
 vrrp_instance VI_1 {  
   state BACKUP  
   interface enp1s0  
   priority 100  
   virtual_router_id 51  
   unicast_src_ip 172.31.10.178  
   unicast_peer {  
      }  
   authentication {  
     auth_type PASS  
     auth_pass 8-character-secret-here  
   }  
   track_script {  
     chk_haproxy  
   }  
   virtual_ipaddress {  
     172.31.10.240  
   }  
 }  
Restart and enable keepalived.service to ensure it starts at next boot and the configuration is correct:
 [archy@helper02 ~]$ sudo systemctl enable --now keepalived.service  
For additional information, the logs of keepalived can be checked using 'journalctl -b -u keepalived.service'. However, this should be all there is to set up for keepalived in that scenario.

Feel free to comment and / or suggest a topic.

Comments

Popular posts from this blog

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0 ...

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but  for a detailed comparison check out this  article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla...

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?...

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key"; controls { inet 172.31.0.1 port 953 allow { 172.31.0.5; } keys ...

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the...