CP-21656: Dynamically Populate Service Endpoints

[bdrennz]

This PR modifies the generate command so that it populates the kube_state_metrics_service_endpoint and prometheus_node_exporter_service_endpoint using the work done in #27, to find all services within a cluster.

(system) ➜  cloudzero-agent-validator git:(cp-21656) ✗ ./bin/cloudzero-agent-validator config generate --kubeconfig /tmp/bdren.kubeconfig --account 123 --cluster test --region us-east-1 --kubeconfig /tmp/bdren.kubeconfig                                                      <region:us-east-1>(⎈|arn:aws:eks:us-east-1:975482786146:cluster/bdren:default)
versions:
  chart_version: 0.0.26
  agent_version: latest

logging:
  level: info
  location: ./cloudzero-agent-validator.log

deployment:
  account_id:  123
  cluster_name:  test
  region:  us-east-1

cloudzero:
  host:  https://api.cloudzero.com
  credentials_file: /etc/config/prometheus/secrets/value

prometheus:
  kube_state_metrics_service_endpoint:  http://cz-prom-agent-kube-state-metrics.default.svc.cluster.local:8080
  prometheus_node_exporter_service_endpoint:  http://cz-prom-agent-prometheus-node-exporter.default.svc.cluster.local:9100
  configurations:
    - /etc/config/prometheus/configmaps/prometheus.yml

diagnostics:
  stages:
    - name: pre-start
      enforce: true
      checks:
        - egress_reachable
        - api_key_valid
    - name: post-start
      enforce: false
      checks:
        - k8s_version
        - kube_state_metrics_reachable
        - node_exporter_reachable
        - scrape_cfg
    - name: pre-stop
      enforce: false
      checks:

[bdrennz]

This command was initially to prove out that we can list the services installed on a Cluster. Now that this functionality has moved into the generate command, I opted to remove it.

[josephbarnett]

I wonder if we still want this as a hidden command? I think there is a flag for that. It might be a useful - non-destructive test we could have hidden

[josephbarnett]

Nice! 🚀