Global hosting provider phoenixNAP, an Infrastructure-as-a-Service (IaaS) company delivering dedicated servers, colocation, and bare metal cloud, has released its Bare Metal Cloud (BMC) Controller for Kubernetes. This integration would ensure easier and more efficient infrastructure management operations for bare metal cloud resources in DevOps and multi-cloud scenarios.
The bare metal cloud controller for Kubernetes, which is available on phoenixNAP’s official GitHub page, would allow developers to define, deploy, and administer bare metal cloud servers in a uniform manner directly from a Kubernetes cluster. Without the use of third-party infrastructure management solutions, DevOps teams can use the Kubernetes API to provide bare metal cloud resources. This would allow developers to focus on pushing code to production without leaving the Kubernetes environment, which may simplify infrastructure administration.
Creating a Kubernetes manifest file and running typical Kubernetes CLI commands is now all it takes to deploy bare metal cloud (BMC) servers with phoenixNAP. The controller serves as a link between the bare metal cloud platform and Kubernetes, coordinating interactions between the Kubernetes API and the BMC API. This would save time and money for developers when dealing with infrastructure deployments by allowing them to make the best use of these BMC resources.
“The release of the BMC Controller for Kubernetes is part of our ongoing commitment to providing DevOps teams with the necessary tools for facilitating automated BMC resource provisioning and management at scale,” said Ian McClarty, President of phoenixNAP.
“This integration benefits not only DevOps organizations, but also empowers businesses that run Kubernetes on on-prem infrastructure to move their workloads to a clout native-ready environment. Our custom-built Kubernetes Controller makes it more convenient and flexible to deploy high-performance dedicated machines with cloud-like flexibility directly from a Kubernetes cluster with familiar Kubernetes commands. There’s no need to use the web-based dashboard or external infrastructure management tools because everything developers need is already available within their Kubernetes environment.”
Data Centers in the U.S., Europe, and Asia
The BMC Controller for Kubernetes is built in Go, and the source code may be downloaded from phoenixNAP’s official GitHub account. Developers can use it to provision and configure any of the 20+ BMC server instance types across data centers in the U.S., Europe, and Asia using Ubuntu, CentOS, and Windows Server operating systems.
In addition to this Kubernetes connectivity, the phoenixNAP BMC development team is constantly working to introduce connectors with popular Infrastructure as Code (IaC) modules, as well as GitHub Actions and automation scripts, to make the process of deploying bare metal cloud servers as quick and easy as possible. Developers that have not yet implemented Kubernetes can use Terraform, Ansible, Pulumi, and Chef to provision BMC servers using simple code instructions. All of the IaC models’ source code is also available on phoenixNAP’s GitHub account.
Bare Metal Cloud Explained
phoenixNAP’s Bare Metal Cloud offering is a dedicated server platform that is not virtualized and provides cloud-like flexibility and speed. Users have more freedom to customize their environments according to specific security and performance needs since they have unfettered access to the server’s actual CPU, RAM, and storage resources.
It would be as simple as deploying a virtual machine (VM) to set up a Bare Metal Cloud server. Users can control their infrastructure using the API, CLI, or custom-built Infrastructure as Code modules. Users can choose from a variety of server instance types, including general-purpose, compute-optimized, and memory-optimized servers, allowing them to perform a wide range of demanding tasks.