Kubernetes (Helm)

Install an XPLG product on a Kubernetes cluster with the Helm chart.

What you will do: install a product with Helm, give it persistent storage and expose its console.

The Helm chart installs the nodes of a product as a release in a namespace of your choice. It works on managed Kubernetes services and on self-managed clusters, including OpenShift.

Prerequisites

  • kubectl access to the cluster and Helm installed.
  • A StorageClass that provides persistent volumes.
  • Node sizes from Sizing and capacity planning.

Steps

  1. Add the XPLG chart repository:
helm repo add xplg <placeholder-chart-repo-url>
helm repo update
  1. Create a values file with the settings you want to change. At minimum set the storage size and the way you expose the console:
persistence:
  storageClass: <placeholder>
  size: <placeholder>
service:
  type: <placeholder>
ingress:
  enabled: <placeholder>
  host: <placeholder>
resources:
  requests:
    cpu: <placeholder>
    memory: <placeholder>
  1. Install the release:
helm install <placeholder-release> xplg/<placeholder-chart> \
  --namespace <placeholder-namespace> --create-namespace \
  -f values.yaml
  1. Wait for the pods to become ready:
kubectl get pods -n <placeholder-namespace> -w
  1. Open the console through the service or ingress you configured, complete the first-run screen and register the deployment.

Collecting from the cluster

PortX collects from Kubernetes and OpenShift directly. The collectors can be enabled from the same values file so that pod logs and events flow into the deployment without extra agents.

Day two

  • Upgrade: helm upgrade with the new chart version; see Upgrades.
  • Scale: change the replica settings in the values file and run helm upgrade.
  • Uninstall: helm uninstall removes the release; persistent volumes follow your StorageClass reclaim policy.

Next: Virtual machine and bare metal

Verify with XPLG engineering before publishing.