openelb VS k8s-api-interaction

My project was "CNCF - OpenELB: Provide the OpenELB Web UI for managing EIP and IP pool". I had to develop a web console for creating and managing the OpenELB resources. Now you might be wondering what is OpenELB. Well, OpenELB is an open-source load balancer implementation designed for exposing the LoadBalancer type of Kubernetes services in bare metal, edge, and virtualization environments. You can learn more about it here https://openelb.io/. Here's the project URL https://github.com/openelb/openelb. It is a sandbox project in CNCF.

Then on June 18th, 2022, I got a chance to meet our mentors and the other mentee of OpenELB (the mentee and the mentors of OpenFunction were also there). There I was informed about how to start working on the project, so I started learning about using the Kubernetes API client. After experimenting with the official Kubernetes Client, I learned that it's not very feasible to use that for dealing with CRDs (custom resource definitions), so I explored the controller-runtime client as per what I found in many sources, and found that it was a great fit for the backend of our project. During that time, I also built a simple project to see if everything would work as expected or not (as this was the first time I dealt with a Kubernetes client, I considered that debugging would be easier in a smaller project).