Shashank Veerapaneni

You cannot modify any sysctl setting from a pod that doesn’t run under privileged security context. You would see Read-only file system error.

My USB/wireless printer worked fine for 10 days and then stopped working. Print jobs are queued but are not printed and even CUPS doesn’t detect the printer anymore. After looking at the logs at /var/log/messages, it appears that the printer was constantly getting disconnected.

I have an old HP 1018 USB printer at home. It has been serving well for 10 years and is still going strong. Back then we had just one computer at home - a desktop computer which was shared by everyone. Now everyone has their own smartphones desktop/laptops but there is only one printer. Time has come for the printer to be available wirelessly on the network. As a temporary solution, I have connected the printer to the desktop and enabled printer sharing so that any device connected to the same home wifi can use the printer. But the desktop has to be always on which is cumbersome and also increases the electricity bill. Following are the approaches I considered for solving this.

MetalLB is a load-balancer implementation for bare metal Kubernetes clusters. I’ve used it succesfully to add support for LoadBalancer type service on bare-metal kubernetes clusters to expose my services outside the cluster.

Exposing services externally on Kubernetes clusters provided by cloud providers is as simple as setting spec.type as LoadBalancer in the service specification and the cloud provider takes care of spinning up a network load balancer. It is not that simple on bare metal Kubernetes clusters as there is no support for LoadBalancer service out of the box as of today. I had this problem recently at work and figured out few approaches to deal with this after some google-fu and researching on how IngressControllers like nginx deal with it.