Add a test for V100 against the GKE staging endpoint.
We use 8 V100 per node because that's the supported configuration currently.
@@ -461,6 +461,10 @@ test_groups:
gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-staging-latest-device-plugin-gpu
alert_stale_results_hours: 24
num_failures_to_alert: 4 # Runs every 2h. Alert when it's been failing for 8 hours.
+- name: ci-kubernetes-e2e-gke-staging-latest-device-plugin-gpu-v100
+ gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-staging-latest-device-plugin-gpu-v100
+ alert_stale_results_hours: 36
+ num_failures_to_alert: 3 # Runs every 12h. Alert when it's been failing for 36h.
- name: ci-kubernetes-e2e-gke-updown
gcs_prefix: kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-updown
- name: ci-kubernetes-e2e-gci-gke-updown
@@ -2732,6 +2736,8 @@ dashboards:
test_group_name: ci-kubernetes-e2e-gke-staging-default-parallel
- name: gke-staging-latest-device-plugin-gpu
test_group_name: ci-kubernetes-e2e-gke-staging-latest-device-plugin-gpu
+ - name: gke-staging-latest-device-plugin-gpu-v100
+ test_group_name: ci-kubernetes-e2e-gke-staging-latest-device-plugin-gpu-v100
- name: gke-staging-1-7-1-8-upgrade-master
test_group_name: ci-kubernetes-e2e-gke-staging-1-7-1-8-upgrade-master
- name: gke-staging-1-7-1-8-upgrade-cluster
@@ -3639,6 +3645,11 @@ dashboards:
base_options: 'exclude-filter-by-regex=^BeforeSuite$'
alert_options:
alert_mail_to_addresses: 'gke-kubernetes-accelerators-bugs@google.com'
+ - name: gke-staging-latest-device-plugin-gpu-v100
+ test_group_name: ci-kubernetes-e2e-gke-staging-latest-device-plugin-gpu-v100
+ base_options: 'exclude-filter-by-regex=^BeforeSuite$'
+ alert_options:
+ alert_mail_to_addresses: 'gke-kubernetes-accelerators-bugs@google.com'
- name: gke-device-plugin-gpu-monitoring
test_group_name: ci-kubernetes-e2e-gke-device-plugin-gpu-monitoring
base_options: 'exclude-filter-by-regex=^BeforeSuite$'
