Skip to main content

​
What you need before you start

RequirementHow to confirm
Kubernetes cluster runningkubectl cluster-info
Active kubeconfig pointing to the right clusterkubectl config current-context
kube-prometheus-stack installed (optional – see note)kubectl get pods -n monitoring – Prometheus and Grafana pods should be Running
kubectl configured for your clusterkubectl get nodes
Helm v3+ installedhelm version
gcloud CLI installed and authenticatedgcloud version and gcloud auth print-access-token
SambaRack Manager (snctl) installed and configuredsnctl version
Nodes labeled with snRduArchkubectl get nodes --show-labels – see note below
kube-prometheus-stack is the reference architecture SambaNova recommends, but it is not required. If you already manage your own Prometheus and Grafana, you can skip installing kube-prometheus-stack and configure your Prometheus scrape targets directly from the exporter endpoints. Contact SambaNova support for guidance on custom monitoring setups.
Node labels: SambaNova nodes must be labeled with snRduArch for the DaemonSets to schedule correctly. If you set up SambaStack following the on-prem quickstart, this label was applied during that process. If a node is missing its snRduArch label and DaemonSet pods become Pending, see Troubleshooting for steps to apply the label.

​
Credentials you will need

You need three sets of credentials:

​
1. Google Cloud service account key file (from SambaNova)

This key file is used to create an image pull secret that allows Kubernetes to authenticate with the SambaNova artifact registry. Contact your SambaNova representative. They provide the .json key file, the registry URL, and the chart version number.

​
2. XRDU BMC credentials (from your BMC configuration)

The XRDU exporter authenticates to each XRDU BMC to collect metrics. This requires a read-only user configured on your XRDU BMCs. This user is set up on the BMC during SambaRack installation. Contact your SambaNova representative or your infrastructure team for the read-only username and password. If one has not been created yet, it must be configured on the BMC before proceeding. You can also retrieve BMC credentials from SambaRack Manager: 
snctl secret get --device-type bmc --show-value

​
3. BMC and XRDU IP addresses (from snctl)

The XRDU exporter needs the management IP of every XRDU BMC it will scrape. For each rack in your system, repeat the following steps: 
# List all nodes with their details
snctl node list --output wide

# Show XRDU details for a specific node
snctl node show <node-name>
For each node, note down:
  • The Kubernetes node name (matches kubectl get nodes output exactly)
  • The XRDU BMC IP address(es) – a node can have multiple XRDUs attached (a standard rack has 8 XRDUs)
The .env file and GCP key file you create during installation contain credentials. Restrict permissions after creating them:
chmod 600 .env
chmod 600 /path/to/gcp-key.json
echo ".env" >> .gitignore

Next: Install and verification

Install the Helm chart and verify all three exporters are running