kubernetes
/
autoscaler
mirror of https://github.com/kubernetes/autoscaler.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #6036 from khareyash05/docs 

fix: Broken links to testgrid dashboard
This commit is contained in:
Kubernetes Prow Robot 2023-08-23 00:56:21 -07:00 committed by GitHub
parent 5e20c44db5 0ed75e4490
commit 199570e8bb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
cluster-autoscaler/FAQ.md
View File

@ -125,8 +125,8 @@ Since version 1.0.0 we consider CA as GA. It means that:
* We have enough confidence that it does what it is expected to do. Each commit goes through a big suite of unit tests * We have enough confidence that it does what it is expected to do. Each commit goes through a big suite of unit tests
with more than 75% coverage (on average). We have a series of e2e tests that validate that CA works well on with more than 75% coverage (on average). We have a series of e2e tests that validate that CA works well on
[GCE](https://k8s-testgrid.appspot.com/sig-autoscaling#gce-autoscaling) [GCE](https://testgrid.k8s.io/sig-autoscaling#gce-autoscaling)
and [GKE](https://k8s-testgrid.appspot.com/sig-autoscaling#gke-autoscaling). and [GKE](https://testgrid.k8s.io/sig-autoscaling#gke-autoscaling).
Due to the missing testing infrastructure, AWS (or any other cloud provider) compatibility Due to the missing testing infrastructure, AWS (or any other cloud provider) compatibility
tests are not the part of the standard development or release procedure. tests are not the part of the standard development or release procedure.
However there is a number of AWS users who run CA in their production environment and submit new code, patches and bug reports. However there is a number of AWS users who run CA in their production environment and submit new code, patches and bug reports.

2
vertical-pod-autoscaler/RELEASE.md
View File

@ -23,7 +23,7 @@ We use the issue to communicate what is state of the release.
## Update VPA version const ## Update VPA version const
1. [ ] Wait for all VPA changes that will be in the release to merge. 1. [ ] Wait for all VPA changes that will be in the release to merge.
2. [ ] Wait for [the end to end tests](https://k8s-testgrid.appspot.com/sig-autoscaling-vpa) to run with all VPA changes 2. [ ] Wait for [the end to end tests](https://testgrid.k8s.io/sig-autoscaling-vpa) to run with all VPA changes
included. included.
To see what code was actually tested, look for `===== last commit =====` To see what code was actually tested, look for `===== last commit =====`
entries in the full `build-log.txt` of a given test run. entries in the full `build-log.txt` of a given test run.