Kubernetes Management

In the GlobalAI Infrastructure module, Kubernetes management goes beyond defining standalone manifests. The platform provides a structured system for creating reusable templates, deploying them across clusters, and managing their full lifecycle.

This framework is built on three core capabilities:

• Application templates: Versioned blueprints that define how your application should be deployed.
• Cluster groups: Logical collections of clusters that support automatic target selection based on deployment rules.
• Deployment lifecycle controls: Automated resource management features that help reduce costs in non-production environments.

Application templates

Application templates act as reusable blueprints for deploying workloads. They enable consistent and repeatable deployments across multiple clusters.

Key characteristics include:

• Standardization: Templates typically leverage Helm charts and can be uploaded as .zip or .tar.gz packages. They allow you to define parameters, namespaces, and configuration values in a structured way.

• Versioning: Each template can have multiple versions. Once a version has at least one deployment, it becomes read-only to ensure consistency.

• Updates & revisions: When you update a deployment to a newer version, the platform creates a revision. You can review previous revisions and revert if needed.

Cluster groups

As your infrastructure grows, manually selecting the correct cluster for each deployment becomes inefficient. Cluster Groups simplify this process by letting you treat multiple clusters as a single logical destination.

Each group uses a Deployment Rule to determine how clusters are selected:

Rule Type	Description
Random	A cluster is chosen at random from the group. Useful for stateless or interchangeable workloads.
Round Robin	Clusters are selected sequentially, balancing deployments evenly across the group.

When you deploy a template version associated with a Cluster Group:

• The platform automatically selects the target cluster based on the rule.
• You may still override the choice and select a different cluster manually.

Geo-specific deployments

Use Cluster Groups to enforce regional placement, for example, a “Europe” group ensures deployments remain within EU-approved clusters.

Deployment lifecycle controls

GlobalAI includes lifecycle settings that help optimize infrastructure costs, especially for development, demo, or temporary environments.

Each deployment can define:

• Default Time (how long the deployment stays active)
• Additional Time / Grace Period
• Time values use ISO 8601 duration format (e.g., P1D = 1 day)

Deployment lifecycle options

Each deployment can be configured with a lifecycle option that determines how GlobalAI manages its compute resources and data once the defined time window expires.

Option	Resource Impact	Data Persistence	Best Use Case
Manual	Resources remain active indefinitely until manually removed.	Full persistence.	Production workloads or long-running environments that must remain online.
Stop	Workload resources (CPU and RAM) are halted while storage remains intact.	Secrets, configs, and Persistent Volumes are retained.	Development or testing environments you want to pause without losing data.
Terminate	All resources are removed once the configured time expires.	No persistence.	Temporary demos, previews, or POCs that require full cleanup after use.

Related articles

Now that you understand the core concepts behind Kubernetes management, explore the next steps:

Configure Clusters

Connect your Kubernetes clusters and configure monitoring.

Manage Cluster Groups

Set up routing rules and organize your clusters.

Deploy Applications

Create deployments using your templates.