Node Pools

A node pool is essentially a collection of nodes within a Kubernetes cluster that have similar configurations, such as the same machine type, operating system, and instance size.

All nodes in a node pool are configured identically, making it easier to manage and maintain consistency across your cluster. This is especially useful when scaling the cluster, as additional nodes added to the pool will have the same specifications.

When a Cluster is created on SleakOps, a set of node pools are created, based on the architecture type you’ve selected during the cluster selection.

sleakops-build-arm64 & sleakops-build-amd64: A default ones to run properly your builds. They can’t be edited or deleted.
sleakops-core: Ensures the scalability of the critical components and cluster addons.
ondemand-arm/amd: Ready for you to use.
spot-arm/amd: Ready for you to use.

aviso

Do not delete manually the following node pools: sleakops-build-arm64, sleakops-build-amd64, sleakops-core.

What are the different kind of node pools?

On-Demand: are instances in a Kubernetes cluster that run with a fixed pricing model, providing reliable access to compute resources without the risk of interruption. Can be used:
- Critical Workloads: Applications that require consistent uptime, such as databases, financial systems, or other critical services.
- Long-Running Tasks: Tasks that cannot be interrupted without significant consequence.
Spot: are instances that take advantage of spare capacity in a cloud provider’s data center. They are available at a significant discount compared to On-Demand instances, but they come with the risk of being terminated if the provider needs the capacity back. Ideal for:
- Stateless Applications: Suitable for workloads that can tolerate interruptions, such as batch processing jobs, testing environments, and distributed computing.
- Cost-Sensitive Workloads: Ideal for tasks where cost savings are a priority over availability.

How many Node Pools can I have?

SleakOps base plan, allows you to have three extra node pool besides the build ones. If you need more, contact us.

Can I convert a spot node pool into an on demand and viceversa?

You can't directly convert a Spot node pool into an On-Demand node pool or vice versa, but you can achieve the desired outcome through a series of steps in SleakOps. Here’s how you can transition between node pools types:

Create a Node Pool of the new desired type.
Updade your executions and projects to run into the new Node Pool.
Delete the old node pool if it is not longer needed.

Can I convert a ARM node pool into an X86 and viceversa?

You can't change the architect type of a node pool, but you can achieve the desired outcome through a series of steps in SleakOps. Here’s how you can transition between node pools architectures: