These are the frequently asked questions for Vultr Kubernetes Engine (VKE).
Vultr Kubernetes Engine (VKE) is a fully managed Kubernetes service that simplifies Kubernetes management by handling the control plane and worker node management. It provides features such as automatic scaling, load balancing, and integrated storage solutions. VKE allows users to focus on deploying and scaling applications without needing to manage the underlying Kubernetes infrastructure.
Vultr Kubernetes Engine (VKE) supports both manual and automatic scaling of node pools. You can manually adjust the number of nodes in a pool or use the autoscaler feature to automatically adjust the number of nodes based on workload demands. The autoscaler maintains a specified range of nodes to ensure your applications remain responsive during traffic spikes and cost-effective during low usage periods.
Yes, Vultr Kubernetes Engine (VKE) allows you to create multiple Node Pools within a single cluster, each with different compute types. This enables you to run mixed workloads by selecting different Node Pool types (e.g., Regular Cloud Compute, High Frequency, AMD/Intel High Performance) suited to your specific workload requirements.
Vultr Kubernetes Engine (VKE) uses Vultr's Container Storage Interface (CSI) to provide persistent block storage. You can choose between HDD and NVMe block storage based on performance needs. Persistent Volume Claims (PVCs) are used to allocate and manage storage for applications, ensuring data persistence even if worker nodes are recreated.
The minimum requirements include:
The minimum size for a block storage volume is:
No, Vultr Kubernetes Engine (VKE) does not include a preconfigured ingress controller. You will need to deploy an ingress controller such as Nginx, Traefik, or HAProxy to manage external access to services in your cluster.
Vultr Kubernetes Engine (VKE) provides a dedicated Manage Upgrades tab for controlling cluster upgrades. You can upgrade the Kubernetes version or apply patches as new updates become available. Vultr handles the control plane upgrades while you manage worker node upgrades. For smooth operation, ensure that workloads can tolerate node restarts during upgrades.
To enhance the security of Vultr Kubernetes Engine (VKE) cluster:
Vultr Kubernetes Engine (VKE) uses the Calico Container Network Interface (CNI) for networking. Calico provides a scalable networking solution with support for advanced networking features like network policies, IP address management, and high performance.
If you delete a worker node outside the Vultr Kubernetes Engine (VKE) Dashboard, Vultr Kubernetes Engine (VKE) cluster will automatically redeploy the node to maintain the node pool configuration and ensure cluster stability. The system handles the replacement to keep your cluster’s desired state intact.