Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Orchestrate CockroachDB in a Single Kubernetes Cluster - prometheus issue #8888

Closed
dbist opened this issue Nov 11, 2020 · 4 comments · Fixed by #10578
Closed

Orchestrate CockroachDB in a Single Kubernetes Cluster - prometheus issue #8888

dbist opened this issue Nov 11, 2020 · 4 comments · Fixed by #10578
Assignees

Comments

@dbist
Copy link
Contributor

dbist commented Nov 11, 2020

Re: Orchestrate CockroachDB in a Single Kubernetes Cluster

Issue Description

this step kubectl port-forward prometheus-cockroachdb-0 9090 is not working as there's no resource with that name available

Suggested Resolution

is there a step missing?

@keith-mcclellan
Copy link
Contributor

I dont think that the prometheus endpoint is currently being exposed by the operator. There probably needs to be an enhancement request made to the operator

@taroface taroface self-assigned this Nov 11, 2020
@taroface
Copy link
Contributor

I think this PR I opened on our prometheus.yaml might be the needed fix? cockroachdb/cockroach#56025

With the serviceAccountName field is commented out, I'm able to apply the manifest and run the port-forward command.

@taroface
Copy link
Contributor

@keith-mcclellan Do you think the above is a relevant fix?

@jseldess jseldess changed the title Orchestrate CockroachDB in a Single Kubernetes Cluster Doc Update Orchestrate CockroachDB in a Single Kubernetes Cluster - prometheus issue Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants