Kubernetes Workloads in Thalassa Cloud

Kubernetes workloads define how applications run within a cluster. In Thalassa Cloud Kubernetes, workloads are managed using Pods, Deployments, DaemonSets, and StatefulSets, each suited for different application types. These resources enable users to run applications in a scalable, resilient, and automated manner.

Pods

A Pod is the smallest deployable unit in Kubernetes, representing one or more containers that share storage, networking, and lifecycle. Pods ensure that tightly coupled applications run together as a single unit.

• Each Pod is assigned a unique IP address within the cluster.
• Containers inside a Pod share the same network namespace and storage volumes.
• Pods are ephemeral by default, meaning they may be recreated if they fail.

For more details, see the Kubernetes Pod Documentation.

Deployments

A Deployment provides a declarative way to manage application workloads. It ensures that a specified number of identical Pods run at all times and can handle rolling updates and rollbacks.

• Supports scalability by defining the desired number of replicas.
• Automates updates and rollbacks for application releases.
• Ensures self-healing, restarting failed Pods automatically.

Example use case: Web applications, APIs, background jobs.

For more details, see the Kubernetes Deployment Documentation.

DaemonSets

A DaemonSet ensures that a specific Pod runs on every (or some) node in the cluster. This is ideal for running system-wide services such as logging, monitoring, or networking components.

• Guarantees that one Pod per node is running.
• Automatically adds Pods to new nodes as they join the cluster.
• Typically used for infrastructure services like logging agents and networking proxies.

Example use case: Fluentd for log aggregation, CoreDNS for cluster DNS.

For more details, see the Kubernetes DaemonSet Documentation.

StatefulSets

A StatefulSet is designed for workloads that require stable network identities and persistent storage, such as databases and distributed applications.

• Each Pod gets a unique, stable network identity.
• Maintains a persistent volume for each instance.
• Pods are created and deleted in a specific order.

Example use case: Databases (PostgreSQL, MySQL), Kafka, Zookeeper.

For more details, see the Kubernetes StatefulSet Documentation.