Block a user
Monitor an application within a tenant
install_prometheus seems a bit inaccurate: we're not installing prometheus here, we're installing the receivers to run on prometheus
Monitor an application within a tenant
I'm not sure it's really a good thing that we try to Serialize the K8sClient 🤔
Monitor an application within a tenant
This trait shouldn't be extending PrometheusMonitoring as they're not really related to each other. It's 2 different capabilities.
Monitor an application within a tenant
This file is almost identical to k8s_prometheus_alerting_score, the only difference being that this one has a namespace attribute whereas the k8s one has a sender that is used to retrieve the namespace.
fix(cli): simplify running the CLI by hiding the maestro inside the implemtation
fix(cli): reduce noise & better track progress within Harmony
fix(cli): reduce noise & better track progress within Harmony
@johnride About this, could we actually reverse things a little bit?
As of now, when we initialize the maestro, it tries to prepare the Topology right away. But because of this, when later on…
refactor(topo/k8s_anywhere): simplify local installation of k3d