This document lists the people and organizations that are using Tinkerbell in production or in a significant deployment capacity. Thank you to all that have adopted Tinkerbell and are willing to be listed as adopters!
To add yourself or your organization, please send a pull request to this file. People and organizations are listed in alphabetical order.
- You must be using Tinkerbell in production or have a significant deployment
- You must represent the listed person or organization
- Information provided must be publicly shareable
- A production deployment includes:
- Enterprise/company usage
- Cloud service provider offering
- Significant home lab/personal deployment
Use this template in the Adopters List section:
### Organization Name
- **Description**: Brief description of your organization
- **Usage**: How you use Tinkerbell (components, scale, etc.)
- **Links**:
- [Website](https://example.com)
- [Docs](https://docs.example.com)
- **Contacts**: (optional)
- GitHub: @username
- CNCF Slack: @slackhandle- Organizations are listed alphabetically
- Contact information is optional but encouraged for community building
- Links should be publicly accessible
- If you have questions about your deployment and this list, please reach out via the CNCF Slack Tinkerbell Channel or via GitHub discussions.
- Description: Autodiscover data center hardware and provision Kubernetes cluster with native support for Tinkerbell.
- Usage: The Tinkerbell stack to orchestrate bare metal automations.
- Links:
- Contacts:
- CNCF Slack: @John Dietz, @Jared Edwards
- Description: AWS's managed Kubernetes distribution that enables customers to create and operate Kubernetes clusters on-premises
- Usage: The Tinkerbell stack and CAPT (Cluster API Provider Tinkerbell) are used to provision bare metal EKS Anywhere clusters
- Links:
- Contacts:
- CNCF Slack: @Jacob Weinstock