Since the Kubeflow GitHub is part of the CNCF enterprise account, we have access to the GitHub Large Runners for our test infrastructure.
The following runners are currently available:
ubuntu-latest-4-cores
ubuntu-latest-8-cores
ubuntu-latest-16-cores
github-arm64-2c-8gb
To utilize these runners, we need to enable Repository Access in the Kubeflow GitHub organization setting. We've successfully implemented the ubuntu-latest-16-cores runner for Kubeflow Trainer E2Es: kubeflow/trainer#2470
As of now, we've enabled it for these repos:
kubeflow/trainer
kubeflow/manifests
kubeflow/mpi-operator
kubeflow/sdk
If other Kubeflow WGs require access to large runners for their testing infrastructure, please reach out, and we will help to enable it.
cc @kubeflow/kubeflow-steering-committee @kubeflow/wg-training-leads @kubeflow/wg-automl-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-data-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-manifests-leads @kubeflow/release-team
Since the Kubeflow GitHub is part of the CNCF enterprise account, we have access to the GitHub Large Runners for our test infrastructure.
The following runners are currently available:
To utilize these runners, we need to enable Repository Access in the Kubeflow GitHub organization setting. We've successfully implemented the
ubuntu-latest-16-coresrunner for Kubeflow Trainer E2Es: kubeflow/trainer#2470As of now, we've enabled it for these repos:
If other Kubeflow WGs require access to large runners for their testing infrastructure, please reach out, and we will help to enable it.
cc @kubeflow/kubeflow-steering-committee @kubeflow/wg-training-leads @kubeflow/wg-automl-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-data-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-manifests-leads @kubeflow/release-team