Thanks Rob. I got it running by definition a prometheus resource on the monitoring.coreos.com/v1 api.
On Friday, 10 August 2018 17:16:11 UTC+1, Rob Szumski wrote: > > Nope, the Operator talks directly to the Kubernetes API to start and watch > the Prometheus instances. Where you see Helm used is to deploy the Operator > itself, but that is completely optional and you can just use the > Deployment + RBAC role from the docs. > > If you didn't see a Prometheus cluster started, did you remember to make > an instance of the custom resource within the namespace where the Operator > is running? > > - Rob > > On Fri, Aug 10, 2018 at 2:15 AM Tim Blackwell <[email protected] > <javascript:>> wrote: > >> I might be getting the wrong end of the stick but after reading >> https://coreos.com/operators/prometheus/docs/latest/user-guides/getting-started.html >> >> I was under the impression that it created and managed prometheus. >> I have the operator running but it does not create prometheus. >> >> Having looked at the git repo, I see they have a helm directory, do I >> need helm installed on my cluster for the operator to work? >> >
