Packet is an officially supported provider for the Kubernetes Cluster API. The Cluser API is an effort to make cluster bootstrapping declarative, while also using a single interface for a variety of Kubernetes providers (i.e. cloud providers like Packet, AWS, GCP, or provisioners like kubeadm).
The Cluster API, regardless of which provider backend is used, has a workflow that begins with your templates for the machines that will make up the configured cluster, templates for bootstrapping machines, and then the resources spawned from these templates, with options for traditional patterns like replication controllers to manage the deployment itself.
In practice, this results in things like multi-tenant clusters, templated access controls, and operations surrounding deploying multiple clusters of identical configurations automatable like any other part of your Kubernetes strategy.
Using the Packet provider, cluster configurations, infrastructure requirements, and things like certificate management,
Service CIDRs, and addons can be checked into your cluster-api manifests. The result is that resources like
MachineDeployment as well as the cluster itself becomes manageable as YAML like other Kubernetes resources.
Using Cluster API with Packet
You may use the examples for Packet to quickly get up and running with clusterctl.
- How Cluster API Promotes Self-Service Infrastructure
- The Cluster API Book
- Packet cluster-api Provider
- Packet Example Files for Cluster API
Was it helpful?