Skip to main content

Posts

Showing posts from February, 2022

Kubernetes - NFS mount example

By default, containers are stateless meaning they're not storing any data besides the image itself on disk. This behavior can be quite unfortunate when running workloads that require working with data such as databases. One of the easiest ways is to mount an NFS share to the container(s) and let them store everything on the NFS share so here's an example. First, prepare the NFS Share: [root@nfssrv ~]# echo '/var/nfs/test 172.31.10.0/24(rw,secure,sync,no_root_squash)' >> /etc/exports [root@nfssrv ~]# exportfs -rav Create the manifest for the Persistent Volume: --- apiVersion: v1 kind: PersistentVolume metadata: name: var-nfs-test spec: capacity: storage: 512Mi volumeMode: Filesystem accessModes: - ReadWriteMany persistentVolumeReclaimPolicy: Recycle storageClassName: nfs mountOptions: - vers=4.2 - namlen=255 - proto=tcp - timeo=30 - retrans=3 nfs: pa

FreeIPA - Recover a broken replica

It happened to me that a node broke in a way that was not feasible to 'repair'. By broken, I mean that I was not able to recover by re-creating all keytabs for the dirserver and named that were invalid according to the logs. Anyway, here's the way I took to recover the node and make all nodes replicate again First, log in to a working node and remove the faulty node from the replication: [archy@ipa02 ~]$ ipa server-del ipa01.archyslife.lan \ --ignore-topology-disconnect ----------------------------------------- Deleted IPA server "ipa01.archyslife.lan" ----------------------------------------- If you're running on the latest version of 4.9.6 and EL8.5, you might encounter this error . After you've removed the host, check if there are any traces left in your ldap tree: [archy@ipa02 ~]$ ipa server-find --------------------- 2 IPA servers matched --------------------- Server name: ipa02.archyslife.lan Min domain level: 1 Ma

Network Teaming - LACP on EL8 with Network Manager

I've already written this article for EL7 and it has been fairly popular so here it is for EL8. First of all, what is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwidth. NOTE: every client's 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 depend on the number 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. With EL8, there's really only the Network Manager method I would recommend since the network scripts are being deprecated. Also, I'm not going to cover ansible. First, create the te