Accept ANY or list of eligible server types for a deploy request
It would be great if the terraform provider would allow for the plan type to be a list of flavors of servers instead of just a string. Much the same way that facility is today. https://registry.terraform.io/providers/packethost/packet/latest/docs/resources/device is what I am referring to here.
MTCS Certification for Equinix Metal in Singapore
MTCS certification for Equinix Metal will be key if we want to win FSI and Gov customers. https://en.m.wikipedia.org/wiki/SS584
Mirantis Container Cloud (MCC) Provider
Support Mirantis' Container Cloud (MCC) for deployments on Equinix Metal.
Portworx (K8s Storage) Example
Create and document a sample architecture for Portworx on Equinix Metal, provide an example deployer.
Cluster Autoscaler integration into CAPI
It would be useful for CAPI to add Cluster Autoscaler into the workload clusters. Since CAPI already has CCM automatic deployment, it would be beneficial to also have this integration for scaling the cluster as workloads increase/decrease.
Support for Yubikey 2FA for console auth
Add support for hardware tokens such as a Yubikey for 2FA user authentication to the console.
WHMCS Provisioning Module
A marketplace available provisioning module for WHMCS https://marketplace.whmcs.com/product/category/Provisioning+Modules
CLI Support for Running Integrations via Packet API
It is currently possible to control Terraform, Ansible, GO, Python via the Packet API. However, this is not possible through the Packet CLI. Update: We get to update / change / add new functionality to the API, but forget to add the functionality to the CLI (and other tools!) - we do we update / change to both - keep them at least within a few days (weeks) of the functionality added to one, added to the other and vice versa. This may be more of a development cycle request - that all functionalities / bugs / wrappers are applied to all tools that touch / have that technology integration / platform / infrastructure.