Issues with Percona Everest (enable monitoring, changing cluster)

Hi, Thank you for your question

“Registered instance name” should be left blank, it is required if you want to change an already registered pmm instance.

Also, URLs should be specified without / at the end.

An example of my installation that I tested today.

➜  0.6.0 everestctl monitoring enable
? Everest URL endpoint http://34.29.192.255:8080
? Everest Token ********************************************************************************************************************************
? Registered instance name
? PMM URL Endpoint http://44.202.59.130
? Username admin
? Password ******
? Name for the new monitoring instance pmm
2024-01-19T09:11:36Z	info	monitoring/enable.go:186	Preparing k8s cluster for monitoring	{"component": "monitoring/enable", "action": "monitoring"}
2024-01-19T09:11:36Z	info	monitoring/enable.go:164	Installing victoriametrics-operator operator	{"component": "monitoring/enable"}
2024-01-19T09:11:40Z	info	monitoring/enable.go:180	victoriametrics-operator operator has been installed	{"component": "monitoring/enable"}
2024-01-19T09:11:58Z	info	monitoring/enable.go:194	K8s cluster monitoring has been provisioned successfully	{"component": "monitoring/enable", "action": "monitoring"}
2024-01-19T09:11:59Z	info	monitoring/enable.go:198	Deploying VMAgent to k8s cluster	{"component": "monitoring/enable"}
2024-01-19T09:12:18Z	info	monitoring/enable.go:229	VMAgent deployed successfully	{"component": "monitoring/enable"}

These are two known issues with the monitoring setup, we will definitely improve this.