digitaloceangoogle-cloudharvesterkubernetesmicrosoft-azuresuse-virtualizationterraformvirtualization
Tested the functionality of deploying VMs with a pre-existing SSH key and applied some bugfixes |
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| images | ||
| modules | ||
| projects | ||
| tests | ||
| .gitignore | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
README.md
harvester-cloud
A project for deploying Harvester on cloud providers instead of bare-metal infrastructure.
Why?
To make it easy for anyone to spin up a Harvester environment for labs, testing, and basic PoCs.
⚠️ Not intended for production use.
How the repository is structured
.
├── modules/
│ └── ...
├── projects/
│ └── ...
├── docs/
│ └── ...
└── # images/, tests/, LICENSE, etc.
The modules/ directory contains templates for deploying VMs on different cloud providers (Google Cloud, Microsoft Azure, and DigitalOcean), along with all necessary scripts to configure Harvester.
The projects/ directory combines modules to create different deployment recipes based on specific use cases. For example, you can deploy a 3-node Harvester cluster on Google Cloud VMs or, given an existing Harvester cluster, deploy images, networks, and additional VMs.
What does the docs/ folder contain?
- Terraform CLI preparatory steps
- OpenTofu CLI preparatory steps
- Infrastructure estimated costs
- Harvester cluster deployment process
- Performance analyses
- How to create a basic Harvester VM and access it via SSH from the local CLI
- How to create a downstream K8s cluster from Rancher using the Harvester Cloud Provider
- How to perform an upgrade in an air-gapped Harvester cluster
- Microsoft Azure known issues
How to get started with the various projects
- Azure
- DigitalOcean
- Harvester Operations: