Feel free to disregard, but it would help me understand if you briefly explain how this fits in with / compares to existing tools like argocd.
I watched your video and I saw that argo was one of the tools you were installing, so clearly this is occupying a different niche - But I'm not sure what that is yet :)
It is often used by developers to get a glimpse of the state of core application of a company without cluster access.
Glasskube focuses on the packages your core application depends on. Managing the life cycle of these infrastructure components, testing updates and providing upgrading paths. You can still put Glasskube packages into your GitOps repo and sync them via ArgoCD into the cluster. Our PackageController will do the rest.