From b5ee64bf380b0a44964cf3141a0ac72acf075469 Mon Sep 17 00:00:00 2001 From: Saverio Proto Date: Tue, 24 Jul 2018 13:15:24 +0200 Subject: [PATCH] Improve docs about TLS secret --- deploy/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/deploy/README.md b/deploy/README.md index ba1692fc..000b092d 100644 --- a/deploy/README.md +++ b/deploy/README.md @@ -2,13 +2,15 @@ Example Deployment ================== 1. Make sure you've built the included Dockerfile with `make docker-build`. The image should be tagged as `directxman12/k8s-prometheus-adapter:latest`. - + 2. Create a secret called `cm-adapter-serving-certs` with two values: `serving.crt` and `serving.key`. These are the serving certificates used by the adapter for serving HTTPS traffic. For more information on how to generate these certificates, see the [auth concepts documentation](https://github.com/kubernetes-incubator/apiserver-builder/blob/master/docs/concepts/auth.md) in the apiserver-builder repository. + The kube-prometheus project published two scripts [gencerts.sh](https://github.com/coreos/prometheus-operator/blob/master/contrib/kube-prometheus/experimental/custom-metrics-api/gencerts.sh) + and [deploy.sh](https://github.com/coreos/prometheus-operator/blob/master/contrib/kube-prometheus/experimental/custom-metrics-api/deploy.sh) to create the `cm-adapter-serving-certs` secret. 3. `kubectl create namespace custom-metrics` to ensure that the namespace that we're installing the custom metrics adapter in exists.