Create the MONITORING_ID for alaz in a more gitops-y way?

[kastl-ars]

I am currently playing around with Anteon (self-hosted), as I find it very interesting and see some usecases for our customers.

One thing I would like to see but have not found:

Can I add a cluster without the manual "Create cluster" click in the UI to get the MONITORING_ID for the alaz helm chart?

Best would be some CRD or configmap/secret that I create in Kubernetes that tells Anteon to create a new cluster.
Or is there a command that I can kubectl exec inside one of the anteon pods that does the "create cluster" part and spits out a ID?

My test setup is currently based on vagrant and Ansible, which stops once Anteon is installed due to this issue.

Our customers mostly use GitOps (ArgoCD, Flux) which means we have to add Anteon first, wait for it to be deployed and usable and then prepare the alaz manifests.

Kind Regards,
Johannes