> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gcore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# About Gcore Managed Kubernetes

Gcore Managed Kubernetes runs container workloads on [Gcore Cloud](/cloud) infrastructure:

* **Bare Metal support**. Cluster node pools deploy on [Virtual Instances](/cloud/virtual-instances/create-an-instance) or [Bare Metal Kubernetes](/cloud/kubernetes/bare-metal-kubernetes) instances, including GPU Bare Metal instances, because dedicated hardware reduces latency and avoids noisy-neighbor effects from shared VMs.
* **Secure master node management**. Customers access worker nodes directly, while Gcore administrators manage master nodes and the control plane. Access to master nodes is restricted to maintain security and service stability.
* **Flexible pool configuration**. Each cluster organizes worker nodes into pools. Add pools and set **Minimum nodes** and **Maximum nodes** per pool on the Create cluster form in the [Gcore Customer Portal](https://portal.gcore.com).
* **Autoscaling**. The Cluster Autoscaler adds and removes nodes based on demand when pool minimum and maximum limits differ. Configure [autoscaling](/cloud/kubernetes/clusters/autoscaling/about-autoscaling) in pool settings and in the **Cluster Autoscaler** section under Advanced settings.
* **Autohealing nodes**. The service monitors node health and replaces failed nodes automatically. The **Autohealing nodes** option is enabled by default when creating a pool.
* **Data storage**. PersistentVolumeClaims (PVC) work with Gcore [volumes](/cloud/virtual-instances/volumes/create-and-configure-volumes) to persist application data. [Create a PVC](/cloud/kubernetes/storage/create-a-pvc-and-bind-it-to-a-pod) from the storage settings.
* **Networking**. Route application traffic with an [Nginx ingress](/cloud/kubernetes/networking/install-and-set-up-the-nginx-ingress-controller) controller.
* **High availability and SLA**. Managed Kubernetes is built on Cluster API and includes a 99.99% SLA.

## Shared responsibilities

Managed Kubernetes handles many operational tasks, but not all responsibilities for running applications on Kubernetes. Gcore follows a shared responsibility model.

**Gcore's responsibilities:**

* Managing the control plane.
* Maintaining high availability and SLAs.
* Provisioning worker nodes according to cluster settings.

**Customer responsibilities:**

* Managing [SSH keys](/cloud/virtual-instances/connect/connect-to-your-instance-via-ssh#generate-an-ssh-key-in-the-ssh-keys-section) according to industry best practices.
* Validating that services and applications work with selected settings and configurations.