kubernetes-sigs/prometheus-adapter
1
0
Fork 1
mirror of https://github.com/kubernetes-sigs/prometheus-adapter.git synced 2026-04-05 17:27:51 +00:00
Code Issues Projects Releases Packages Activity Actions

[docs] Minor walkthough fixes

Browse source 
This fixes a typo in the walkthrough with a missing `</details>` closing
tag, and clarifies that you'll need RBAC set up for delegation.
This commit is contained in:
Solly Ross 2017-09-25 13:26:27 -04:00
parent f9a9893093
commit 109ad80627
1 changed files with 9 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/walkthrough.md
View file

@ -210,14 +210,20 @@ Then, store your serving certificates in a secret:
$ kubectl -n prom create secret tls serving-cm-adapter --cert=/path/to/cm-adapter/serving.crt --key=/path/to/cm-adapter/serving.key
```
Finally, you'll need to make sure that the default service account for
your namespace has permission to list resources in the cluster:
Next, you'll need to make sure that the service account used to launch the
Deployment has permission to list resources in the cluster:
```shell
$ kubectl create clusterrole resource-lister --verb=list --resource="*"
$ kubectl create clusterrolebinding cm-adapter-resource-lister --clusterrole=resource-lister -- serviceaccount=prom:prom-cm-adapter
```
Finally, ensure the deployment has all the necessary permissions to
delegate authentication and authorization decisions to the main API
server. See [Concepts: Auth and
Certificates](https://github.com/kubernetes-incubator/apiserver-builder/blob/master/docs/concepts/auth.md)
for more information.
Next, amend the file above to run the adapter as well. You may need to
modify this part if you wish to inject the needed certificates a different
way.
@ -328,7 +334,7 @@ spec:
namespace: prom
```
<details>
</details>
Register that registration object with the aggregator: