-
Notifications
You must be signed in to change notification settings - Fork 1k
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
docs: Template prometheus values based on Karpenter namespace #5698
Conversation
✅ Deploy Preview for karpenter-docs-prod ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
website/content/en/docs/getting-started/getting-started-with-karpenter/prometheus-values.yaml
Show resolved
Hide resolved
Pull Request Test Coverage Report for Build 7993812500Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
...docs/getting-started/getting-started-with-karpenter/scripts/step09-add-prometheus-grafana.sh
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
Fixes #N/A
Description
The Monitoring with Grafana part of the getting started guide for Karpenter hardcodes the Karpenter namespace to "kube-system" in the prometheus scrape targets configuration. This is a configurable option in the walk-through. This PR templates the prometheus values file.
How was this change tested?
Does this change impact docs?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.