Kubernetes Management with OneKS on

Kubernetes Cluster Lifecycle Management

Tue, 12 May 2026 00:00:00 +0000

This section describes the main lifecycle operations for OneKS K8s Clusters. It covers how to create, access, scale, upgrade, recover, and delete K8s Clusters.

A OneKS K8s Cluster lifecycle normally follows this sequence:

Create a K8s Cluster: Provision the control plane and required infrastructure.
Access the K8s Cluster: Retrieve the kubeconfig and validate Kubernetes API access.
Add or Scale Worker Capacity: Create or resize node groups.
Upgrade the K8s Cluster: Move the K8s Cluster to a supported Kubernetes version.
Recover Failed Operations: Retry selected failed lifecycle actions.
Delete the K8s Cluster: Deprovision the K8s Cluster and associated resources.

OneKS exposes these operations through Sunstone, the CLI, and the REST API, depending on the deployment and user permissions.

Kubernetes Cluster Monitoring and Troubleshooting

Tue, 12 May 2026 00:00:00 +0000

OneKS uses event-based monitoring to follow VM provisioning, deprovisioning, and lifecycle changes. Its current visibility model is centered on lifecycle state, events, and logs.

Event-driven monitoring is implemented through OpenNebula VM and dependency event watchers. It tracks VM allocation and state changes, seed VM state changes, and dependency lifecycle changes.

K8s Cluster States

OneKS exposes the following K8s Cluster states:

State	Description
`PENDING`	A K8s Cluster document has been created.
`PROVISIONING`	Control-plane provisioning has started.
`RUNNING`	All expected groups are running.
`SCALING`	A node group is being added, removed, or resized.
`UPGRADING`	The K8s Cluster version is being upgraded.
`DEPROVISIONING`	The K8s Cluster resources are being deleted.
`WARNING`	One or more groups are inconsistent or degraded.
`DONE`	K8s Cluster deprovisioning has completed.
`PROVISIONING_FAILURE`	Provisioning failed.
`SCALING_FAILURE`	Scaling failed.
`UPGRADING_FAILURE`	Upgrade failed.
`DEPROVISIONING_FAILURE`	Deprovisioning failed.

Node Group States

OneKS exposes the following group states:

Kubernetes Cluster Configuration

Tue, 12 May 2026 00:00:00 +0000

This page summarizes the main runtime configuration used by the OneKS service. It covers the settings that define the service behavior and the server configuration options.

Configuration File

By default, the main OneKS server configuration file is:

/etc/one/oneks-server.conf

When OpenNebula is installed with ONE_LOCATION set, the same configuration file is resolved relative to that installation path:

$ONE_LOCATION/etc/oneks-server.conf

The file follows the same YAML syntax used by other OpenNebula services.

Kubernetes Cluster Profiles Customization

Tue, 12 May 2026 00:00:00 +0000

OpenNebula Elastic Kubernetes Service (OneKS) defines Kubernetes deployment profiles exposed to users through families, flavours, dependencies, and user inputs. Administrators can customize these specs to change the capacities offered by each flavour, expose new input parameters, update supported Kubernetes versions, or tune the dependencies used during provisioning.

Profiles are used by both control-plane and node-group profiles. By default, the OneKS profile configuration files are located in the following paths:

/var/lib/one/oneks/controlplane/general/controlplane.conf
/var/lib/one/oneks/nodegroup/general/nodegroup.conf

After changing a profile configuration, restart the OneKS service so the updated profile definition is loaded. For service commands, see Service Management.