[Yandex Cloud documentation](../../index.md) > [Yandex Managed Service for Kubernetes](../index.md) > FAQ > Resources

# Resources

* [What resources do I need to maintain a Kubernetes cluster with a group of, say, three nodes?](#required-resources)

* [Can I change resources for each node in a Kubernetes cluster?](#change-resources)

* [Who handles Kubernetes cluster scaling?](#scaling)

* [Do the Kubernetes cluster nodes need internet access?](#internet-access)

#### What resources do I need to maintain a Kubernetes cluster with a group of, say, three nodes? {#required-resources}

Each [node](../concepts/index.md#node-group) needs resources to run the Kubernetes components that allow the node to work as part of the [Kubernetes cluster](../concepts/index.md#kubernetes-cluster). For more information, see [Dynamic resource allocation](../concepts/node-group/allocatable-resources.md).

#### Can I change resources for each node in a Kubernetes cluster? {#change-resources}

You can only change resources for a node group. You can create groups with different configurations in a single Kubernetes cluster and spread them across multiple [availability zones](../../overview/concepts/geo-scope.md). For more information, see [Updating a Managed Service for Kubernetes node group](../operations/node-group/node-group-update.md).

#### Who handles Kubernetes cluster scaling? {#scaling}

In Managed Service for Kubernetes, you can enable [cluster autoscaling](../concepts/autoscale.md#ca).

#### Do the Kubernetes cluster nodes need internet access? {#internet-access}

To connect to external resources, e.g., Docker image registries such as [Container Registry](../../container-registry/concepts/index.md), [Cloud Registry](../../cloud-registry/concepts/index.md), or [Docker Hub](https://hub.docker.com/) as well as [Object Storage buckets](../../storage/concepts/bucket.md), the group nodes must have internet access.

To enable internet access, [assign](../operations/node-group/node-group-update.md#node-internet-access) a public IP address to the nodes and [configure](../operations/connect/security-groups.md#rules-internal-nodegroup) a security group. As an alternative to public IP addresses, you can also create and configure a [NAT gateway](../../vpc/operations/create-nat-gateway.md) or a [NAT instance](../../vpc/tutorials/nat-instance/index.md) in the subnet hosting the nodes.

For more information, see [Internet access for cluster worker nodes](../concepts/network.md#nodes-internet).