Table of Contents generated with DocToc
This documentation describes configuration and automation for Kubeflow Optional-Test-Infra.
The architecture doc will give you a deep understanding how optional-test-infra works and how different clusters interact with each other.
Today we still rely on human to manipulate test-infra AWS resources, such as the number of EC2 instances. We're now experimenting IaC(Infrastructure as Code) tool CDK to manage test-infra resources.
The diagram shows the phases that kubeflow tests goes through when you send a PR.
- Prow Dashboard shows what jobs are running or have recently run in prow
- Argo Dashboard shows you what Argo workflow are running and logs
- Tekton Dashboard shows you what Tekton PipelineRuns are running and logs
- Adopting Optional-Test-Infra provides a detailed instruction for kubeflow application WG to onboard their kubeflow repo to use optional-test-infra.
- Writing Argo Workflow for E2E Tests
- [TODO] PatrickXYS: need to provide more detailed instructions
[TODO] PatrickXYS: need detailed guidance
Each sub-folder refer to different functionality for Optional-Test-Infra
- User: user-modifiable configuration files for all the clusters under Optional-Test-Infra concepts
- GitOps: ArgoCD sync changes in the folder to update cluster resources
- Doc: documentations for optional-test-infra
- Picture: pictures embedded in the documentations
- testing: testing artifacts storage
- Access: Infra Access Control for Kubeflow Community
Let's join us and start contributing!
[TODO] PatrickXYS: Provide a detailed guidance for people who want to start contributing to optional-test-infra.
[TODO] PatrickXYS: Provide a deep-dive doc for design of optional-test-infra.