meshery VS gloo-mesh

Meshery is an open-source cloud infrastructure and Kubernetes management platform that provides a unified interface for simplifying the deployment, management, and observability of cloud-native applications. It acts as a central control plane for managing Kubernetes clusters, containerized applications, and associated resources.

After searching through many different open source repositories, I was unable to find anything that peaked my interest. I was struggling and was slowly loosing hope. However, one thing that kept on occurring was my ongoing PR fixes for my release 0.3 external project Meshery. My ongoing PR was full of reviews, and I was constantly making small changes based off those comments. That is when it sparked to me that this pull request was essentially what our professor was looking for in release 0.4, so I decided to do two things.

Most Open-Source projects have a contributing doc(usually a CONTRIBUTING.md file at the root of the repo) that contains all the necessary details on how to set up your development environment, coding conventions you have to follow and much more.

My first issue was This which was regarding the improper margins on the management page, a component/ui and framework/react issue :) Tbh, it wasn't a huge amount of work, I just had to fix the padding values of the component as shown below and I was good to go

I'm only a K8s amateur and I've never used it in Prod, but I've used Gloo Mesh with Istio and EKS Anywhere to make a unified control plane between on prem and AWS-EKS. It was a pretty small scale deployment, but if you have low enough latency, it felt like I should scale pretty well.

Gloo Mesh is one of those products. It provides a good example of how to reduce the complexity of managing the entire application networking in your infrastructure to a minimum. As can be understood, this implies multi-cluster architectures.