---
title: FAQ
url: https://docs.vultr.com/products/compute/kubernetes/faq
description: A comprehensive resource addressing common questions about Vultr Kubernetes Engine features, functionality, and management.
publish_date: 2024-09-23T20:20:41.120603Z
last_updated: 2026-05-26T18:59:54.023968Z
---

# Frequently Asked Questions (FAQs) About Vultr Kubernetes Engine

These are the frequently asked questions for Vultr Kubernetes Engine (VKE).

???+ note "What is Vultr Kubernetes Engine (VKE) and how does it simplify Kubernetes management?"

    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.

??? note "Can I attach an existing VPC to a new VKE cluster?"

    Yes, you can attach an existing VPC to a new VKE cluster, but both the VPC and the cluster must be in the same region. When creating a VKE cluster, you can select an existing VPC from the VPC Network dropdown. If you do not select an existing VPC, VKE will automatically provision a new VPC in the same location by default.

??? note "How does Vultr Kubernetes Engine (VKE) cluster handle scaling?"

    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.

??? note "Can I run mixed workloads with different compute types in the same Vultr Kubernetes Engine (VKE) cluster?"

    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.

??? note "How does Vultr Kubernetes Engine (VKE) cluster handle persistent data storage?"

    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.

??? note "What are the minimum requirements for deploying a Vultr Kubernetes Engine (VKE) cluster?"

    The minimum requirements include:

    * At least one Node Pool with a minimum of one worker node.
    * Worker nodes should have at least 2 GB of RAM.
    * Basic network setup in the deployment location.
    * Kubernetes version selection.

??? note "What is the minimum size for a block storage volume in Vultr Kubernetes engine (VKE)?"

    The minimum size for a block storage volume is:

    * 10 GB for NVMe storage.
    * 40 GB for HDD storage. 
    These sizes are enforced by Vultr's CSI, and you can specify the desired size when creating a Persistent Volume Claim (PVC).

??? note "Does Vultr Kubernetes Engine (VKE) include an ingress controller?"

    No, Vultr Kubernetes Engine (VKE) does not include a pre-configured 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.

??? note "How does Vultr Kubernetes Engine (VKE) cluster handle upgrades?"

    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.

??? note "What are the security best practices for managing Vultr Kubernetes Engine (VKE) cluster?"

    To enhance the security of Vultr Kubernetes Engine (VKE) cluster:

    * Only use kubeconfig files from trusted sources, as maliciously crafted files could compromise the cluster.
    * Regularly audit Kubernetes Role-Based Access Control (RBAC) policies.
    * Keep your Kubernetes version up to date using VKE's managed upgrades.
    * Implement network policies to restrict unnecessary communication between pods.

??? note "What is the default networking solution in 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.

??? note "What happens if I delete a worker node outside the Vultr Kubernetes Engine (VKE) dashboard?"

    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.