You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the genesis kit assumes when selecting "monitor CF installation" that CF will be installed inside of the control plane.
As a user of Prometheus within the genesis control plane, I need the ability to monitor child genesis CF deployments from the control plane.
below is the output of the preflight check that outlined the issue when attempting this configuration:
$ genesis deploy smo-control-plane.yml
Checking availability of the 'smo-control-plane' BOSH director...
Preparing to deploy smo-control-plane to 'smo-control-plane' BOSH director.
Fetching cloud config from 'smo-control-plane'
Downloading cloud config from 'smo-control-plane' BOSH director...
$.instance_groups.prometheus.jobs.bosh_exporter.properties.bosh_exporter.bosh.uaa.client_secret: secret secret/smo/control/plane/bosh/uaa/clients/prometheus:secret not found
$.instance_groups.prometheus.jobs.cf_exporter.properties.cf_exporter.cf.api_url: secret secret/exodus/smo-control-plane/cf:api_url not found
$.meta.cf_firehose_uaa_vault: secret secret/exodus/smo-control-plane/cf:vaulted_uaa_clients not found
$.meta.cf_system_domain: secret secret/exodus/smo-control-plane/cf:system_domain not found
$.meta.uaa_client_secret: failed to retrieve (( vault "secret/exodus/" meta.bosh_exodus_path "/cf from Vault (https://10.222.96.163): no handler for route '(( vault "secret/exodus/" meta.bosh_exodus_path "/cf'
Unable to merge smo-control-plane manifest (run failed):
The text was updated successfully, but these errors were encountered:
If you want to monitor CF, you have to spin a separate prometheus instance per CF. Due to the nature of the prometheus-boshrelease, you cannot co-mingle CFs in one prometheus.
For that reason, the Genesis Kit pretty much expects to find the CF in the same environment as the BOSH director that is deploying the Prometheus, which is not the case in with the Operations Tier / Control Plane.
Currently, the genesis kit assumes when selecting "monitor CF installation" that CF will be installed inside of the control plane.
As a user of Prometheus within the genesis control plane, I need the ability to monitor child genesis CF deployments from the control plane.
below is the output of the preflight check that outlined the issue when attempting this configuration:
$ genesis deploy smo-control-plane.yml
Checking availability of the 'smo-control-plane' BOSH director...
Preparing to deploy smo-control-plane to 'smo-control-plane' BOSH director.
Downloading cloud config from 'smo-control-plane' BOSH director...
[smo-control-plane] running cloud-config and environmental parameter checks...
cloud-config [OK]
✔ secret/smo/control/plane/prometheus/nginx/ssl_certificate [OK]
environment files [OK]
[smo-control-plane] running manifest viability checks...
5 error(s) detected:
Unable to merge smo-control-plane manifest (run failed):
The text was updated successfully, but these errors were encountered: