Kubernetes clusters

Exposing complex applications running within a Kubernetes cluster to the internet and traffic routing requires a comprehensive approach. The Ingress controller is a tool that solves these tasks along with a variety of additional options.

servers.com offers a service for creating and managing bare-metal-based Kubernetes clusters. Learn more about our Kubernetes cluster service in this article.

To create a Kubernetes cluster in the Customer Portal, you need to choose dedicated server configurations and the quantity of servers to be used as worker nodes. We will take care of master nodes. You can add and remove worker nodes to and from a cluster at any time.

In order for kubectl to find and access a Kubernetes cluster, it needs a configuration file (kubeconfig file). Download the configuration file for your cluster from the "Kubernetes Cluster Details" page in the Customer Portal.

As per Kubernetes documentation, "Dashboard is a web-based Kubernetes user interface. You can use Dashboard to deploy containerized applications to a Kubernetes cluster, troubleshoot your containerized application, and manage the cluster resources".

You can add worker nodes to a cluster at any time in the Customer Portal.

We offer integrated support for two types of load balancing to make a service publicly accessible: TCP for Service objects & HTTP(S) for Ingress resources.

The provisioned version of the Kubernetes software for each cluster is displayed on a cluster's "Details" page in the Customer Portal.

Servers.com does not offer provider-specific storage options for Kubernetes at the moment. We suggest you to consider one of the following publicly available options.

The Ingress controller is not installed by default on the servers.com Kubernetes cluster. To deploy it, follow the simple steps outlined in this knowledge base article.