Skip to main content
This guide covers how to safely upgrade SambaStack in both deployment types:
  • Hosted — kubectl / ConfigMap-driven installs
  • On-Prem — Helm-driven installs
Some version upgrades may require inference endpoints to restart or cause downtime. Contact your SambaNova representative before upgrading.

Prerequisites

Before upgrading, ensure you have:
  • Access to the Kubernetes cluster with appropriate permissions
  • The target <NEW_VERSION> number confirmed with SambaNova
  • A backup of your current configuration (recommended)

On-prem installs use helm upgrade with the chart version and your existing values file.
1

Upgrade with Helm

Run the upgrade commands for both the base chart and the main chart:
# Upgrade the base chart
helm upgrade \
  --namespace sambastack \
  --version <NEW_VERSION> \
  sambastack-base \
  oci://<REGISTRY_URL>/sambastack/sambastack-base
# Upgrade the main chart with your values file
helm upgrade \
  --namespace sambastack \
  --version <NEW_VERSION> \
  sambastack \
  -f sambastack.yaml \
  oci://<REGISTRY_URL>/sambastack/sambastack-base
Replace <NEW_VERSION> with your target version and <REGISTRY_URL> with your OCI registry URL.
2

Validate the upgrade

Confirm the release status and verify all pods are running:
helm status sambastack -n sambastack
kubectl get pods -n sambastack
All pods should reach Running status within a few minutes.

Rollback

If you need to revert to a previous version, repeat the upgrade steps above using the older version number in place of <NEW_VERSION>.
Rollback follows the same process as upgrading—simply specify the previous version in either the Helm command or ConfigMap.