kubernetes-sigs/prometheus-adapter
1
0
Fork 1
mirror of https://github.com/kubernetes-sigs/prometheus-adapter.git synced 2026-04-06 01:38:10 +00:00
Code Issues Projects Releases Packages Activity Actions

Fixing broken links

Browse source 
Updating links to root so they work whilst reading on Github
This commit is contained in:
Nate Fox 2018-07-02 14:18:43 -07:00 • committed by GitHub
parent 7e49e0733f
commit 75e690b430
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/walkthrough.md
View file

@ -133,11 +133,11 @@ label names for configuring the adapter.
### Creating the Resources and Launching the Deployment ### ### Creating the Resources and Launching the Deployment ###
The [deploy/manifests](deploy/manifests) directory contains the The [deploy/manifests](/deploy/manifests) directory contains the
appropriate files for creating the Kubernetes objects to deploy the appropriate files for creating the Kubernetes objects to deploy the
adapter. adapter.
See the [deployment README](deploy/README.md) for more information about See the [deployment README](/deploy/README.md) for more information about
the steps to deploy the adapter. Note that if you're deploying on the steps to deploy the adapter. Note that if you're deploying on
a non-x86_64 (amd64) platform, you'll need to change the `image` field in a non-x86_64 (amd64) platform, you'll need to change the `image` field in
the Deployment to be the appropriate image for your platform. the Deployment to be the appropriate image for your platform.
@ -145,7 +145,7 @@ the Deployment to be the appropriate image for your platform.
You may also need to modify the ConfigMap containing the metrics discovery You may also need to modify the ConfigMap containing the metrics discovery
configuration. If you're using the Prometheus configuration described configuration. If you're using the Prometheus configuration described
above, it should work out of the box in common cases. Otherwise, read the above, it should work out of the box in common cases. Otherwise, read the
[configuration documentation](docs/config.md) to learn how to configure [configuration documentation](/docs/config.md) to learn how to configure
the adapter for your particular metrics and labels. the adapter for your particular metrics and labels.
### The Registered API ### ### The Registered API ###
@ -274,7 +274,7 @@ has elapsed. If you leave it for a bit, the rate will go back down again.
If the metric does not appear, or is not registered with the right If the metric does not appear, or is not registered with the right
resources, you might need to modify your [metrics discovery resources, you might need to modify your [metrics discovery
configuration](docs/config.md), as mentioned above. Check your labels via configuration](/docs/config.md), as mentioned above. Check your labels via
the Prometheus dashboard, and then modify the configuration appropriately. the Prometheus dashboard, and then modify the configuration appropriately.
As noted in the main [README](README.md), you'll need to also make sure As noted in the main [README](README.md), you'll need to also make sure
@ -361,5 +361,5 @@ scaling on application on a metric provided by another application by
setting different labels or using the `Object` metric source type. setting different labels or using the `Object` metric source type.
For more information on how metrics are exposed by the Prometheus adapter, For more information on how metrics are exposed by the Prometheus adapter,
see [config documentation](docs/config.md), and check the [default see [config documentation](/docs/config.md), and check the [default
configuration](deploy/manifests/custom-metrics-config-map.yaml). configuration](/deploy/manifests/custom-metrics-config-map.yaml).