Which document would you like to address?
deploying-kepler-on-a-local-kind-cluster
What is the issue?
The current documentation for deploying Kepler using make build-manifest on Kind only provides an example with Prometheus enabled:
make build-manifest OPTS="PROMETHEUS_DEPLOY"
kubectl apply -f _output/generated-manifest/deployment.yaml
This forces users into a full monitoring stack, even when they only need basic exporter functionality without Prometheus.
How do you suggest this is fixed?
Add a "Minimal deployment (no Prometheus)" section under the “Deploying Kepler on Kind”.
git clone --depth 1 https://github.com/sustainable-computing-io/kepler.git
cd kepler
make build-manifest OPTS=""
kubectl apply -f _output/generated-manifest/deployment.yaml
Clarify that omitting PROMETHEUS_DEPLOY fully skips ServiceMonitor/RBAC/etc.
Thank you for considering this enhancement!
Which document would you like to address?
deploying-kepler-on-a-local-kind-cluster
What is the issue?
The current documentation for deploying Kepler using
make build-manifeston Kind only provides an example with Prometheus enabled:make build-manifest OPTS="PROMETHEUS_DEPLOY" kubectl apply -f _output/generated-manifest/deployment.yamlThis forces users into a full monitoring stack, even when they only need basic exporter functionality without Prometheus.
How do you suggest this is fixed?
Add a "Minimal deployment (no Prometheus)" section under the “Deploying Kepler on Kind”.
Clarify that omitting PROMETHEUS_DEPLOY fully skips ServiceMonitor/RBAC/etc.
Thank you for considering this enhancement!