Selon le contexte (e.g. K3dLocal), introduire une nouvelle implementation K3d/sTenantManager qui permet d'aller chercher dans docker l'adresse ip a definir ici.
is there a reason why these double clone().clone()? there's a lot of them in this file
install_prometheus seems a bit inaccurate: we're not installing prometheus here, we're installing the receivers to run on prometheus
I'm not sure it's really a good thing that we try to Serialize the K8sClient 🤔
This trait shouldn't be extending PrometheusMonitoring as they're not really related to each other. It's 2 different capabilities.
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.
@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…
1ab66af718
Merge pull request 'refactor(topo/k8s_anywhere): simplify local installation of k3d' (#90) from simply-k3d-installation into master