Guide to Using HKE Helm Chart
This guide shows you how to deploy the HKE Helm Chart to the created HKE cluster.
Prerequisites
A Hostspace Kubernetes Engine (HKE) cluster
Helm CLI (comes pre-installed with HKE clusters)
Available Charts in the HKE Helm Repository
HKE Cleaner DaemonSet:
Deploys a DaemonSet to automatically prune dangling images.
Scheduled via a cron job (runs every Saturday).
It can be customized with the
crictlVersion
or a custom cron schedule.
Netdata:
Monitors system and health metrics from your cluster and nodes.
Provides useful metrics visible in your HostSpaceCloud dashboard.
It includes health checks and integration with Alerta for alert notifications.
Netdata supports restarting policies and hierarchical monitoring (parent-child claims).
Redis:
Deploys Redis with the option to disable authentication and select storage classes (
local-path
by default).Can be exposed via
LoadBalancer
service type.
Velero:
Provides backup and restore capabilities for your Kubernetes cluster.
Configured with AWS S3 or Minio as the backup storage provider.
Integrates with AWS using provided credentials stored in Kubernetes secrets.
OpenTelemetry Collector:
A fully customizable OpenTelemetry Collector for scraping metrics from your cluster.
Includes dynamic detection of Kubernetes node IPs and auto-discovery for
node-exporter
,kube-state-metrics
, and Blackbox Exporter.Can send metrics to a remote Prometheus instance.
Wazuh Agent:
Installs a Wazuh agent on your cluster to collect security events and logs.
Deploying the Charts
Step 1: Add the HKE Helm Repository
Step 2: Update the Helm Repository Cache
Step 3: Install or Upgrade the HKE Chart
Enabling and Customizing Individual Charts
To deploy specific charts and enable features, use the --set
flag.
a. HKE Cleaner DaemonSet
To customize the cron job schedule or the crictlVersion
:
b. Netdata
To enable health checks, Alerta integration, and parent-child monitoring:
c. Redis
To specify a node for Redis deployment:
d. Velero
e. OpenTelemetry Collector
f. Wazuh Agent
Deploying Multiple Charts at Once
You can enable multiple charts in a single command by using multiple --set
flags. For example:
Last updated