📖 Rename Packet to Equinix Metal (in title only) #5774
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
The Packet API (api.packet.net) continues to be supported and is fully integrated with the Equinix Metal experience, so CAPP continues to be a viable provider for existing Packet users and new Equinix Metal users.
This PR avoids confusion by retitling "Packet" to "Equinix Metal" in the documentation.
Binaries and variables should continue to use "Packet" names until a replacement to CAPP is made.
CAPP has already adopted some renaming and rearchitecting to adopt Equinix Metal branded tooling and settings. This work continues in kubernetes-sigs/cluster-api-provider-packet#289 (@detiber).