├── .github ├── ISSUE_TEMPLATE │ └── cncf-community-lab-cluster-request.md ├── settings.yml └── workflows │ └── stale.yml └── README.md /.github/ISSUE_TEMPLATE/cncf-community-lab-cluster-request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: CNCF Community Lab Cluster request 3 | about: CNCF Community Lab Cluster request 4 | title: '' 5 | labels: cluster request 6 | assignees: caniszczyk, jeefy, krook, idvoretskyi 7 | 8 | --- 9 | 10 | Please fill out the details below to file a request for access to the CNCF Community Infrastructure Lab. Please note that access is targeted to people working on specific open source projects; this is not designed just to get your feet wet. The most important answer is the URL of the project you'll be working with. 11 | 12 | If you're looking to learn Kubernetes and related technologies, please try out [Killercoda](https://killercoda.com/playgrounds/course/kubernetes-playgrounds) or [Play With Kubernetes](https://labs.play-with-k8s.com/) instead. 13 | 14 | ### First and Last Name 15 | 16 | ### Email 17 | 18 | ### Company/Organization 19 | 20 | ### Job Title 21 | 22 | ### Project Title (i.e., a summary of what do you want to do, not what is the name of the open source project you're working with) 23 | 24 | ### Briefly describe the project (i.e., what are the details of what you're planning to do with these servers?) 25 | 26 | ### Is the code that you're going to run 100% open source? If so, what is the URL or URLs where it is located? What is your association with that project? 27 | 28 | ### What kind of machines and how many do you expect to use (see: )? 29 | 30 | ### What operating system and networking are you planning to use? 31 | 32 | ### Any other relevant details we should know about? 33 | -------------------------------------------------------------------------------- /.github/settings.yml: -------------------------------------------------------------------------------- 1 | repository: 2 | # See https://developer.github.com/v3/repos/#edit for all available settings. 3 | 4 | # The name of the repository. Changing this will rename the repository 5 | name: cluster 6 | 7 | # A short description of the repository that will show up on GitHub 8 | 🖥🖥🖥🖥 CNCF Community Cluster 9 | 10 | # A URL with more information about the repository 11 | homepage: https://cncf.io/cluster 12 | 13 | # Collaborators: give specific users access to this repository. 14 | collaborators: 15 | # Admins 16 | - username: caniszczyk 17 | permission: admin 18 | 19 | - username: idvoretskyi 20 | permission: admin 21 | 22 | - username: jeefy 23 | permission: admin 24 | 25 | - username: taylorwaggoner 26 | permission: admin 27 | 28 | - username: vielmetti 29 | permission: admin 30 | -------------------------------------------------------------------------------- /.github/workflows/stale.yml: -------------------------------------------------------------------------------- 1 | # This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time. 2 | # 3 | # You can adjust the behavior by modifying this file. 4 | # For more information, see: 5 | # https://github.com/actions/stale 6 | name: Mark stale issues and pull requests 7 | 8 | on: 9 | schedule: 10 | - cron: '22 14 * * *' 11 | 12 | jobs: 13 | stale: 14 | 15 | runs-on: ubuntu-latest 16 | permissions: 17 | issues: write 18 | pull-requests: write 19 | 20 | steps: 21 | - uses: actions/stale@v3 22 | with: 23 | repo-token: ${{ secrets.GITHUB_TOKEN }} 24 | stale-issue-message: 'Checking if there are any updates on this issue' 25 | stale-pr-message: 'Checking if there are any updates on this PR' 26 | stale-issue-label: 'no-issue-activity' 27 | stale-pr-label: 'no-pr-activity' 28 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # CNCF Community Infrastructure Lab (CIL) 2 | 3 | The CNCF Community Infrastructure Lab (CIL) provides free access to state-of-the-art computing resources for open source developers working to advance cloud native computing. We currently offer access to both x86 and ARMv8 bare metal servers for software builds, continuous integration, scale testing, and demonstrations for the CNCF projects. 4 | 5 | The on-demand infrastructure resource is generously contributed and managed by [Equinix Metal](https://metal.equinix.com/), a leading bare metal cloud, as part of its commitment to the cloud native and open source communities. The resources are available from 15 locations across the globe; including New York City, Silicon Valley, Amsterdam, and Tokyo. It allows developers extended testing or the ability to build out continuous integrated infrastructure with the automation and consistency of big public clouds without being required to use virtualization. They offer a variety of hardware [types](https://metal.equinix.com/product/servers/). 6 | 7 | [Apply to Use the On-Demand Infrastructure](https://github.com/cncf/cluster/issues/new?assignees=caniszczyk%2C+jeefy%2C+krook%2C+idvoretskyi&labels=cluster+request&projects=&template=cncf-community-lab-cluster-request.md&title=) 8 | 9 | Request access and then get up and running in minutes! 10 | 11 | ## Infrastructure benefits 12 | 13 | - Allows developers extended testing or the ability to build out continuously integrated infrastructure with the automation and consistency of big public clouds without needing to use virtualization. 14 | - Can be leveraged to curate server configurations for different use cases, test new protocols without layers of complexity, and integrate with leading cloud and developer tools. 15 | - Developers will also have the ability to bring their own image or operating system and have complete control of the cluster, enabling them to test across different environments simultaneously. 16 | - Based on their testing needs, developers can choose from five server configurations offering different sizes, platform features, and architectures (e.g., x86 and ARMv8). 17 | - Each bare metal configuration is API driven, cloud native friendly and takes less than 10 minutes to deploy. 18 | - Equinix Metal does not impose multi-tenancy, virtualization, or an overlay network by default - enabling users to bring the tooling of their choice. 19 | - Carrier-grade features like the ability to announce your own IP space, BGP/Anycast, and native IPv6 support are also included. 20 | 21 | ## Usage guidelines 22 | 23 | - Code being run must be 100 percent open source and must not include any sensitive data. 24 | - Testing should involve cloud native computing, meaning containerization, microservices, orchestration or some combination. 25 | - You agree to write a blog post later about your experiences with the CIL. 26 | - The infrastructure is being provided to CNCF Projects only 27 | - Priority is given first to [CNCF Graduated and Incubating projects](https://www.cncf.io/projects/) then [CNCF Sandbox projects](https://www.cncf.io/sandbox-projects/). 28 | - Resources are limited so we may ask you to reduce your usage when there is high demand for the available credits from Equinix Metal ($1,000,000 per year). 29 | - If the purpose of using the provided infrastructure is CI/CD, please consider using the GitHub-hosted runners with GitHub Actions first, or the CNCF-provided GitHub Runners - 30 | --------------------------------------------------------------------------------