kubernetes-sigs · tylerauerbeck · May 2, 2025
diff --git a/cmd/clusterctl/client/config/providers_client.go b/cmd/clusterctl/client/config/providers_client.go
@@ -57,7 +57,6 @@ const (
 	NutanixProviderName        = "nutanix"
 	OCIProviderName            = "oci"
 	OpenStackProviderName      = "openstack"
-	PacketProviderName         = "packet"
 	TinkerbellProviderName     = "tinkerbell-tinkerbell"
 	SideroProviderName         = "sidero"
 	VCloudDirectorProviderName = "vcd"
@@ -199,11 +198,6 @@ func (p *providersClient) defaults() []Provider {
 			url:          "https://github.com/kubernetes-sigs/cluster-api-provider-gcp/releases/latest/infrastructure-components.yaml",
 			providerType: clusterctlv1.InfrastructureProviderType,
 		},
-		&provider{
-			name:         PacketProviderName,
-			url:          "https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/latest/infrastructure-components.yaml",
-			providerType: clusterctlv1.InfrastructureProviderType,
-		},
 		&provider{
 			name:         TinkerbellProviderName,
 			url:          "https://github.com/tinkerbell/cluster-api-provider-tinkerbell/releases/latest/infrastructure-components.yaml",

diff --git a/cmd/clusterctl/client/config_test.go b/cmd/clusterctl/client/config_test.go
@@ -98,7 +98,6 @@ func Test_clusterctlClient_GetProvidersConfig(t *testing.T) {
 				config.OpenNebulaProviderName,
 				config.OpenStackProviderName,
 				config.OutscaleProviderName,
-				config.PacketProviderName,
 				config.ProxmoxProviderName,
 				config.SideroProviderName,
 				config.TinkerbellProviderName,
@@ -166,7 +165,6 @@ func Test_clusterctlClient_GetProvidersConfig(t *testing.T) {
 				config.OpenNebulaProviderName,
 				config.OpenStackProviderName,
 				config.OutscaleProviderName,
-				config.PacketProviderName,
 				config.ProxmoxProviderName,
 				config.SideroProviderName,
 				config.TinkerbellProviderName,

diff --git a/cmd/clusterctl/cmd/config_repositories_test.go b/cmd/clusterctl/cmd/config_repositories_test.go
@@ -147,7 +147,6 @@ oci                     InfrastructureProvider     https://github.com/oracle/clu
 opennebula              InfrastructureProvider     https://github.com/OpenNebula/cluster-api-provider-opennebula/releases/latest/                    infrastructure-components.yaml
 openstack               InfrastructureProvider     https://github.com/kubernetes-sigs/cluster-api-provider-openstack/releases/latest/                infrastructure-components.yaml
 outscale                InfrastructureProvider     https://github.com/outscale/cluster-api-provider-outscale/releases/latest/                        infrastructure-components.yaml
-packet                  InfrastructureProvider     https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/latest/                   infrastructure-components.yaml
 proxmox                 InfrastructureProvider     https://github.com/ionos-cloud/cluster-api-provider-proxmox/releases/latest/                      infrastructure-components.yaml
 sidero                  InfrastructureProvider     https://github.com/siderolabs/sidero/releases/latest/                                             infrastructure-components.yaml
 tinkerbell-tinkerbell   InfrastructureProvider     https://github.com/tinkerbell/cluster-api-provider-tinkerbell/releases/latest/                    infrastructure-components.yaml
@@ -343,10 +342,6 @@ var expectedOutputYaml = `- File: core_components.yaml
   Name: outscale
   ProviderType: InfrastructureProvider
   URL: https://github.com/outscale/cluster-api-provider-outscale/releases/latest/
-- File: infrastructure-components.yaml
-  Name: packet
-  ProviderType: InfrastructureProvider
-  URL: https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/latest/
 - File: infrastructure-components.yaml
   Name: proxmox
   ProviderType: InfrastructureProvider

diff --git a/docs/book/src/developer/providers/contracts/clusterctl.md b/docs/book/src/developer/providers/contracts/clusterctl.md
@@ -335,7 +335,6 @@ providers.
 | CAPONE        | cluster.x-k8s.io/provider=infrastructure-opennebula   |
 | CAPO          | cluster.x-k8s.io/provider=infrastructure-openstack    |
 | CAPOCI        | cluster.x-k8s.io/provider=infrastructure-oci          |
-| CAPP          | cluster.x-k8s.io/provider=infrastructure-packet       |
 | CAPT          | cluster.x-k8s.io/provider=infrastructure-tinkerbell   |
 | CAPV          | cluster.x-k8s.io/provider=infrastructure-vsphere      |
 | CAPVC         | cluster.x-k8s.io/provider=infrastructure-vcluster     |

diff --git a/docs/book/src/reference/providers.md b/docs/book/src/reference/providers.md
@@ -35,7 +35,6 @@ updated info about which API version they are supporting.
 - [CloudStack](https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack)
 - [CoxEdge](https://github.com/coxedge/cluster-api-provider-coxedge)
 - [DigitalOcean](https://github.com/kubernetes-sigs/cluster-api-provider-digitalocean)
-- [Equinix Metal (formerly Packet)](https://github.com/kubernetes-sigs/cluster-api-provider-packet)
 - [Google Cloud Platform (GCP)](https://cluster-api-gcp.sigs.k8s.io/)
 - [Hetzner](https://github.com/syself/cluster-api-provider-hetzner)
 - [Hivelocity](https://github.com/hivelocity/cluster-api-provider-hivelocity)

diff --git a/docs/book/src/user/quick-start.md b/docs/book/src/user/quick-start.md
@@ -281,7 +281,7 @@ Additional documentation about experimental features can be found in [Experiment
 Depending on the infrastructure provider you are planning to use, some additional prerequisites should be satisfied
 before getting started with Cluster API. See below for the expected settings for common providers.
 
-{{#tabs name:"tab-installation-infrastructure" tabs:"Akamai (Linode),AWS,Azure,CloudStack,DigitalOcean,Docker,Equinix Metal,GCP,Harvester,Hetzner,Hivelocity,Huawei,IBM Cloud,IONOS Cloud,K0smotron,KubeKey,KubeVirt,Metal3,Nutanix,OCI,OpenNebula,OpenStack,Outscale,Proxmox,VCD,vcluster,Virtink,vSphere,Vultr"}}
+{{#tabs name:"tab-installation-infrastructure" tabs:"Akamai (Linode),AWS,Azure,CloudStack,DigitalOcean,Docker,GCP,Harvester,Hetzner,Hivelocity,Huawei,IBM Cloud,IONOS Cloud,K0smotron,KubeKey,KubeVirt,Metal3,Nutanix,OCI,OpenNebula,OpenStack,Outscale,Proxmox,VCD,vcluster,Virtink,vSphere,Vultr"}}
 {{#tab Akamai (Linode)}}
 
 ```bash
@@ -547,20 +547,6 @@ export CLUSTER_TOPOLOGY=true
 clusterctl init --infrastructure docker
 ```
 
-{{#/tab }}
-{{#tab Equinix Metal}}
-
-In order to initialize the Equinix Metal Provider (formerly Packet) you have to expose the environment
-variable `PACKET_API_KEY`. This variable is used to authorize the infrastructure
-provider manager against the Equinix Metal API. You can retrieve your token directly
-from the Equinix Metal Console.
-
-```bash
-export PACKET_API_KEY="34ts3g4s5g45gd45dhdh"
-
-clusterctl init --infrastructure packet
-```
-
 {{#/tab }}
 {{#tab GCP}}
 
@@ -916,7 +902,7 @@ before configuring a cluster with Cluster API. Instructions are provided for com
 Otherwise, you can look at the `clusterctl generate cluster` [command][clusterctl generate cluster] documentation for details about how to
 discover the list of variables required by a cluster templates.
 
-{{#tabs name:"tab-configuration-infrastructure" tabs:"Akamai (Linode),AWS,Azure,CloudStack,DigitalOcean,Docker,Equinix Metal,GCP,Harvester,Huawei,IBM Cloud,IONOS Cloud,K0smotron,KubeKey,KubeVirt,Metal3,Nutanix,OpenNebula,OpenStack,Outscale,Proxmox,Tinkerbell,VCD,vcluster,Virtink,vSphere,Vultr"}}
+{{#tabs name:"tab-configuration-infrastructure" tabs:"Akamai (Linode),AWS,Azure,CloudStack,DigitalOcean,Docker,GCP,Harvester,Huawei,IBM Cloud,IONOS Cloud,K0smotron,KubeKey,KubeVirt,Metal3,Nutanix,OpenNebula,OpenStack,Outscale,Proxmox,Tinkerbell,VCD,vcluster,Virtink,vSphere,Vultr"}}
 {{#tab Akamai (Linode)}}
 
 ```bash
@@ -1046,35 +1032,6 @@ It is also possible but **not recommended** to disable the per-default enabled [
 export POD_SECURITY_STANDARD_ENABLED="false"
 ```
 
-{{#/tab }}
-{{#tab Equinix Metal}}
-
-There are several required variables you need to set to create a cluster. There
-are also a few optional tunables if you'd like to change the OS or CIDRs used.
-
-```bash
-# Required (made up examples shown)
-# The project where your cluster will be placed to.
-# You have to get one from the Equinix Metal Console if you don't have one already.
-export PROJECT_ID="2b59569f-10d1-49a6-a000-c2fb95a959a1"
-# This can help to take advantage of automated, interconnected bare metal across our global metros.
-export METRO="da"
-# What plan to use for your control plane nodes
-export CONTROLPLANE_NODE_TYPE="m3.small.x86"
-# What plan to use for your worker nodes
-export WORKER_NODE_TYPE="m3.small.x86"
-# The ssh key you would like to have access to the nodes
-export SSH_KEY="ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDvMgVEubPLztrvVKgNPnRe9sZSjAqaYj9nmCkgr4PdK username@computer"
-export CLUSTER_NAME="my-cluster"
-
-# Optional (defaults shown)
-export NODE_OS="ubuntu_18_04"
-export POD_CIDR="192.168.0.0/16"
-export SERVICE_CIDR="172.26.0.0/16"
-# Only relevant if using the kube-vip flavor
-export KUBE_VIP_VERSION="v0.5.0"
-```
-
 {{#/tab }}
 {{#tab GCP}}
 
@@ -2002,7 +1959,6 @@ kind delete cluster
 [KubeVirt]: https://kubevirt.io/
 [oci-provider]: https://oracle.github.io/cluster-api-provider-oci/#getting-started
 [openstack-resource-controller]: https://k-orc.cloud/
-[Equinix Metal getting started guide]: https://github.com/kubernetes-sigs/cluster-api-provider-packet#using
 [provider]:../reference/providers.md
 [provider components]: ../reference/glossary.md#provider-components
 [vSphere getting started guide]: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/master/docs/getting_started.md

diff --git a/docs/release/role-handbooks/communications/README.md b/docs/release/role-handbooks/communications/README.md
@@ -195,9 +195,8 @@ We should inform at least the following providers via a new issue on their respe
 * OCI: https://github.com/oracle/cluster-api-provider-oci/issues/new
 * Openstack: https://github.com/kubernetes-sigs/cluster-api-provider-openstack/issues/new
 * Operator: https://github.com/kubernetes-sigs/cluster-api-operator/issues/new
-* Packet: https://github.com/kubernetes-sigs/cluster-api-provider-packet/issues/new
 * vSphere: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/issues/new
 
 To create GitHub issues at the Cluster API providers repositories and inform about a new minor beta release, use ["provider_issues.go"](../../../../hack/tools/release/internal/update_providers/provider_issues.go) go utility.
 - Ensure that the [provider repos pre-requisites](../../../../hack/tools/release/internal/update_providers/README.md#pre-requisites) are completed.
-- From the root of this repository, run `make release-provider-issues-tool` to create git issues at the provider repositories.
+- From the root of this repository, run `make release-provider-issues-tool` to create git issues at the provider repositories.
diff --git a/hack/tools/release/internal/update_providers/provider_issues.go b/hack/tools/release/internal/update_providers/provider_issues.go
@@ -55,7 +55,6 @@ var (
 		"oracle/cluster-api-provider-oci",
 		"kubernetes-sigs/cluster-api-provider-openstack",
 		"kubernetes-sigs/cluster-api-operator",
-		"kubernetes-sigs/cluster-api-provider-packet",
 		"tinkerbell/cluster-api-provider-tinkerbell",
 		"kubernetes-sigs/cluster-api-provider-vsphere",
 		"metal3-io/cluster-api-provider-metal3",