Skip to content

Commit 5ce4059

Browse files
authored
[Docs] Fix broken links in README.md (#63)
1 parent 24ed45d commit 5ce4059

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -35,11 +35,11 @@ service selector).
3535
**Custom metrics API implementation:**
3636

3737
The Autoscaler makes decisions based on data queried from Kubernetes
38-
[custom metrics API.](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/custom-metrics-api.md)
38+
[custom metrics API.](https://github.com/kubernetes/design-proposals-archive/blob/main/instrumentation/custom-metrics-api.md)
3939
There are several possible tools that implement it, we internally use
4040
[Prometheus](https://prometheus.io/) with the [Prometheus-Adapter](https://github.com/DirectXMan12/k8s-prometheus-adapter)
4141
but you can use which ever you want! You can find some recommended implementations
42-
[here](https://github.com/kubernetes/metrics/blob/master/IMPLEMENTATIONS.md#custom-metrics-api)
42+
[here](https://github.com/kubernetes/metrics/blob/release-1.14/IMPLEMENTATIONS.md#custom-metrics-api)
4343

4444
## Getting Started
4545
The infrastructure is designed to be generic, flexible and extendable, so as to serve any resource we'd wish to scale
@@ -52,7 +52,7 @@ therefore it's suggested to put your resource-scaler in its own repo
5252

5353
Examples:
5454
* [Nuclio functions resource-scaler](https://github.com/nuclio/nuclio/blob/master/pkg/platform/kube/resourcescaler/resourcescaler.go)
55-
* [Iguazio's app service resource-scaler](https://github.com/v3io/app-resource-scaler/blob/development/resourcescaler.go)
55+
* [Iguazio's app service resource-scaler](https://github.com/v3io/app-resource-scaler/blob/development/pkg/resourcescaler/resourcescaler.go)
5656

5757
## Installing
5858
[Go plugins](https://appliedgo.net/plugins/) is the magic that glues the resource-scaler and this infrastructure
@@ -66,8 +66,8 @@ move the binary artifact of the build command (the `plugin.so` file) to the `plu
6666
It is much easier to do everything using Dockerfiles, here are some great examples:
6767
* [Nuclio function Autoscaler dockerfile](https://github.com/nuclio/nuclio/blob/master/cmd/autoscaler/Dockerfile)
6868
* [Nuclio function DLX dockerfile](https://github.com/nuclio/nuclio/blob/master/cmd/dlx/Dockerfile)
69-
* [Iguazio's app service Autoscaler dockerfile](https://github.com/v3io/app-resource-scaler/blob/development/autoscaler/Dockerfile)
70-
* [Iguazio's app service DLX dockerfile](https://github.com/v3io/app-resource-scaler/blob/development/dlx/Dockerfile)
69+
* [Iguazio's app service Autoscaler dockerfile](https://github.com/v3io/app-resource-scaler/blob/development/cmd/autoscaler/Dockerfile)
70+
* [Iguazio's app service DLX dockerfile](https://github.com/v3io/app-resource-scaler/blob/development/cmd/dlx/Dockerfile)
7171

7272
You can install the components using the [scaler helm chart](https://github.com/v3io/helm-charts/tree/development/stable/scaler)<br>
7373
`$ helm install --name my-release v3io-stable/scaler`

0 commit comments

Comments
 (0)