Skip to content

Conversation

@fabxc
Copy link
Contributor

@fabxc fabxc commented Nov 19, 2018

@jkohen required some fiddling but this is working well AFAICS.

I removed the setup with an operator since that repo has very extensive documentation and customization options for setting up full k8s monitoring.
The full deployment now has a proper configuration rather than just trying to scrape all ports it can find. It can also scrape the cadvisor metrics now, which are the most important ones probably.

Maybe we can first point out the injection option in the docs and then also the full deployment with the noted caveat that this is just very basic.

Signed-off-by: Fabian Reinartz <freinartz@google.com>
@jkohen jkohen self-requested a review November 19, 2018 21:54
Copy link
Contributor

@jkohen jkohen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@@ -0,0 +1,23 @@
#!/bin/sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you document how this should be invoked? What is the first argument ($1)?

Same for patch.sh

kube/README.md Outdated
* `KUBE_CLUSTER`: cluster name parameter for the sidecar
* `GCP_REGION`: GCP region parameter for the sidecar
* `GCP_PROJECT`: GCP project parameter for the sidecar
* `DATA_DIR`: data directory for the sidecar (`patch.sh` only)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't patch.sh require reconfiguring Prometheus to use the /data directory and mount a named volume? If so, how about splitting this into its own section, and explaining how to set up Prometheus correctly?

If I understood correctly, Prometheus Operator already sets the data volume, right?

Copy link
Contributor Author

@fabxc fabxc Nov 20, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general, a Prometheus server would already have a mounted volume. So the DATA_DIR and DATA_VOLUME are just about attaching that volume to the sidecar as well and using the same data dir as Prometheus already does.

Signed-off-by: Fabian Reinartz <freinartz@google.com>
Copy link
Contributor

@jkohen jkohen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much!

@fabxc fabxc merged commit d0c162e into master Nov 20, 2018
@fabxc fabxc deleted the kubeexample branch November 21, 2018 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants