mirror of
https://github.com/outbackdingo/cluster-api-provider-proxmox.git
synced 2026-01-27 10:18:38 +00:00
7d9b12bce9
* Bumped some versions as the controller-gen crashed * Added ProxmoxClusterTemplate properly * Proper alignment //+kubebuilder, and provide annotatons as specified by spec * Added concurrency to controllers. Added constructors to controllers * Added capiflags * metrics-bind-address is obsolete. Use diagnostics address * Add finalizer on secret * Cleanup to minimize differences * Processing review feedback * Processing feedback * Update * Processing feedback * Fixing tests * Update * Delete capi cluster first * Processing review feedback * Renamed test context * Processing review feedback: solve linting issues --------- Co-authored-by: Mohamed Chiheb Ben Jemaa <mc.benjemaa@gmail.com>
Kubernetes Cluster API Provider for Proxmox Virtual Environment - CAPMOX
Overview
The Cluster API brings declarative, Kubernetes-style APIs to cluster creation, configuration and management. Cluster API Provider for Proxmox VE is a concrete implementation of Cluster API for Proxmox VE.
Launching a Kubernetes cluster on Proxmox VE
Check out the quickstart guide for launching a cluster on Proxmox VE.
Compatibility with Cluster API and Kubernetes Versions
This provider's versions are compatible with the following versions of Cluster API:
| Cluster API v1beta1 (v1.4) | Cluster API v1beta1 (v1.5) | Cluster API v1beta1 (v1.6) | Cluster API v1beta1 (v1.7) | |
|---|---|---|---|---|
| CAPMOX v1alpha1 (v0.1) | ✓ | ✓ | ☓ | ☓ |
| CAPMOX v1alpha1 (v0.2) | ☓ | ✓ | ✓ | ☓ |
| CAPMOX v1alpha1 (v0.3) | ☓ | ✓ | ✓ | ✓ |
| CAPMOX v1alpha1 (v0.4) | ☓ | ✓ | ✓ | ✓ |
| CAPMOX v1alpha1 (v0.5) | ☓ | ☓ | ✓ | ✓ |
(See Kubernetes support matrix of Cluster API versions).
Documentation
Further documentation is available in the /docs directory.
Community, discussion, contribution, and support
Learn how to engage with the Kubernetes community on the community page.
You can reach the maintainers of this project at:
Security
We take security seriously. Please read our security policy for information on how to report security issues.