You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-api-machinery/555-server-side-apply/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -533,7 +533,7 @@ repo. The integration between that repo and kubernetes/kubernetes will mainly
533
533
be tested by integration tests in [test/integration/apiserver/apply](https://github.com/kubernetes/kubernetes/tree/master/test/integration/apiserver/apply)
534
534
and [test/cmd](https://github.com/kubernetes/kubernetes/blob/master/test/cmd/apply.sh),
535
535
as well as unit tests where applicable. The feature will also be enabled in the
536
-
[alpha-features e2e test suite](https://k8s-testgrid.appspot.com/sig-release-master-blocking#gce-cos-master-alpha-features),
536
+
[alpha-features e2e test suite](https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-alpha-features),
537
537
which runs every hour and everytime someone types `/test pull-kubernetes-e2e-gce-alpha-features`
538
538
on a PR. This will ensure that the cluster can still start up and the other
539
539
endpoints will function normally when the feature is enabled.
Once you've made the following changes, open a PR against the test-infra repo adding the sig testing label (`/sig testing`) and cc'ing @kubernetes/sig-testing-pr-reviews. Once your PR merges you should be able to view your results on https://k8s-testgrid.appspot.com/ which should be ready to be consumed by the necessary stakeholders (sig-release, sig-testing, etc).
217
+
Once you've made the following changes, open a PR against the test-infra repo adding the sig testing label (`/sig testing`) and cc'ing @kubernetes/sig-testing-pr-reviews. Once your PR merges you should be able to view your results on https://testgrid.k8s.io/ which should be ready to be consumed by the necessary stakeholders (sig-release, sig-testing, etc).
Copy file name to clipboardExpand all lines: keps/sig-cloud-provider/providers/2530-alibaba-cloud/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ Usage of aliyun container services can be seen from github issues in the existin
66
66
67
67
### Testgrid Integration
68
68
Alibaba cloud provider is reporting conformance test results to TestGrid as per the [Reporting Conformance Test Results to Testgrid KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/0018-testgrid-conformance-e2e.md).
69
-
See [report](https://k8s-testgrid.appspot.com/conformance-alibaba-cloud-provider#Alibaba%20Cloud%20Provider,%20v1.10) for more details.
69
+
See [report](https://testgrid.k8s.io/conformance-alibaba-cloud-provider#Alibaba%20Cloud%20Provider,%20v1.10) for more details.
70
70
71
71
### CNCF Certified Kubernetes
72
72
Alibaba cloud provider is accepted as part of the [Certified Kubernetes Conformance Program](https://github.com/cncf/k8s-conformance).
Copy file name to clipboardExpand all lines: keps/sig-cloud-provider/providers/2531-baidu-cloud/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ CCE-ticket-3: User want to have multi-tenant ability in a shared large CCE clust
60
60
61
61
### Testgrid Integration
62
62
63
-
Baidu applied for the testgrid in 2018, The original report for testgrid is [here](https://k8s-testgrid.appspot.com/conformance-cloud-provider-baiducloud). We are currently working on renewing the testgrid.
63
+
Baidu applied for the testgrid in 2018, The original report for testgrid is [here](https://testgrid.k8s.io/conformance-cloud-provider-baiducloud). We are currently working on renewing the testgrid.
Copy file name to clipboardExpand all lines: keps/sig-cluster-lifecycle/kubeadm/3614-etcd-learner-mode/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -371,7 +371,7 @@ We expect no non-infra related flakes in the last month as a GA graduation crite
371
371
- <test>: <link to test coverage>
372
372
-->
373
373
374
-
[kubeadm-kinder-learner-mode-latest](https://testgrid.k8s.io/sig-cluster-lifecycle-kubeadm#kubeadm-kinder-learner-mode-latest) was added as part of the [kubeadm dashboard](https://k8s-testgrid.appspot.com/sig-cluster-lifecycle-kubeadm) since v1.27. All tests in this dashboard use the [kinder](https://github.com/kubernetes/kubeadm/tree/main/kinder) tool.
374
+
[kubeadm-kinder-learner-mode-latest](https://testgrid.k8s.io/sig-cluster-lifecycle-kubeadm#kubeadm-kinder-learner-mode-latest) was added as part of the [kubeadm dashboard](https://testgrid.k8s.io/sig-cluster-lifecycle-kubeadm) since v1.27. All tests in this dashboard use the [kinder](https://github.com/kubernetes/kubeadm/tree/main/kinder) tool.
375
375
376
376
- During Alpha (disabled by default): add a new e2e test that enables the feature gate EtcdLearnerMode
377
377
- During Beta (enabled by default): modify the e2e test to test the feature gate EtcdLearnerMode as disabled
As migration to new message structure will be done manually we will be focusing on logs that have the greatest impact for log querying and processing. We will be focusing on log messages Proposed plan of measurements:
212
212
213
-
* Using log data from single run of kubernetes [gce-master-scale-performance](https://k8s-testgrid.appspot.com/sig-scalability-gce#gce-master-scale-performance) tests
213
+
* Using log data from single run of kubernetes [gce-master-scale-performance](https://testgrid.k8s.io/sig-scalability-gce#gce-master-scale-performance) tests
For migration to structured API we would like to propose to remove `statusStack` and `addedInfo` arguments. Our reasons:
451
451
* Log format already neglects to put metadata for them, breaking the convention.
452
-
* We didn't find any case of those fields being non empty in [gce-master-scale-performance](https://k8s-testgrid.appspot.com/sig-scalability-gce#gce-master-scale-performance)
452
+
* We didn't find any case of those fields being non empty in [gce-master-scale-performance](https://testgrid.k8s.io/sig-scalability-gce#gce-master-scale-performance)
Copy file name to clipboardExpand all lines: keps/sig-node/2043-pod-resource-concrete-assigments/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -263,7 +263,7 @@ The infrastructure required is expensive and it is not clear what additional tes
263
263
264
264
#### Alpha
265
265
-[X] Implement the new service API.
266
-
-[X][Ensure proper e2e node tests are in place](https://k8s-testgrid.appspot.com/sig-node-kubelet#node-kubelet-serial&include-filter-by-regex=DevicePluginProbe).
266
+
-[X][Ensure proper e2e node tests are in place](https://testgrid.k8s.io/sig-node-kubelet#node-kubelet-serial&include-filter-by-regex=DevicePluginProbe).
267
267
268
268
#### Alpha to Beta Graduation
269
269
-[X] Demonstrate that the endpoint can be used to replace in-tree GPU device metrics in production environments (NVIDIA, sig-node April 30, 2019).
Copy file name to clipboardExpand all lines: keps/sig-node/606-compute-device-assignment/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -191,7 +191,7 @@ covered by e2e tests
191
191
192
192
#### Alpha
193
193
-[X] Implement the new service API.
194
-
-[X][Ensure proper e2e node tests are in place](https://k8s-testgrid.appspot.com/sig-node-kubelet#node-kubelet-serial&include-filter-by-regex=DevicePluginProbe).
194
+
-[X][Ensure proper e2e node tests are in place](https://testgrid.k8s.io/sig-node-kubelet#node-kubelet-serial&include-filter-by-regex=DevicePluginProbe).
195
195
196
196
#### Alpha to Beta Graduation
197
197
-[X] Demonstrate that the endpoint can be used to replace in-tree GPU device metrics in production environments (NVIDIA, sig-node April 30, 2019).
Copy file name to clipboardExpand all lines: keps/sig-storage/3107-csi-nodeexpandsecret/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -173,7 +173,7 @@ N/A
173
173
support to mentioned sidecar, the e2e tests will be added and validated using
174
174
example CSI driver [tests](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/storage/drivers/csi-test/driver/driver.go).
175
175
- E2E test PR is available [here](https://github.com/kubernetes/kubernetes/pull/115451)
176
-
and this test has been enabled in the [testgrid](https://k8s-testgrid.appspot.com/presubmits-kubernetes-nonblocking#pull-kubernetes-e2e-gce-cos-alpha-features)
176
+
and this test has been enabled in the [testgrid](https://testgrid.k8s.io/presubmits-kubernetes-nonblocking#pull-kubernetes-e2e-gce-cos-alpha-features)
- Azurefile has [migration testgrid](https://testgrid.k8s.io/provider-azure-azurefile-csi-driver#pr-azurefile-csi-driver-e2e-migration).
313
313
- Openstack has CSI migration tests for GCE/AWS/Azure/Cinder at [testgrid](https://testgrid.k8s.io/redhat-openshift-ocp-release-4.10-broken#Summary). And an upgrade test will be added soon in the future.
Copy file name to clipboardExpand all lines: keps/sig-windows/1301-windows-runtime-class/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -408,7 +408,7 @@ The existing tests relying on `dockershim` will be run side by side until it is
408
408
409
409
#### Unit testing with CRITest
410
410
411
-
Unit tests will be added in CRITest which is in the [Cri-Tools] repo. Tests are already running on Windows - see [testgrid](https://k8s-testgrid.appspot.com/sig-node-containerd#cri-validation-windows).
411
+
Unit tests will be added in CRITest which is in the [Cri-Tools] repo. Tests are already running on Windows - see [testgrid](https://testgrid.k8s.io/sig-node-containerd#cri-validation-windows).
0 commit comments