Note: These are beta projects, use at your own discretion
Before installing Helm Charts, you will need:
- an existing or a new namespace of a Spin project;
- install
kubectl
andhelm
; - obtain the
kubeconfig
from the Spin cluster where your project runs (either the "development" or "production" cluster).
- Login to rancher2.spin.nersc.gov;
- click the cluster name (as of May 12, 2024, either "development" or "production");
- click "Project/Namespaces" on the sidebar, click "Create Namespace" beside your chosen project.
For up-to-date information, please refer to the official documentation.
- Obtain
kubectl
viacurl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl
; - Set the downloaded
kubectl
to be executable (chmod +x kubectl
); - move
kubectl
to its desired destination (e.g.mv kubectl $HOME/bin/kubectl
); - parent directory of
kubectl
should be include in yourPATH
environment variable, add it if needed (e.g.export PATH=$HOME/bin:$PATH
)
For up-to-date information, please refer to the official documentation.
- Download your desired version
- Unpack it (e.g.
tar -zxvf helm-v3.0.0-linux-amd64.tar.gz
) - Find the helm binary in the unpacked directory, and move it to its desired
destination (e.g.
mv linux-amd64/helm $HOME/bin/helm
); - parent directory of
helm
should be include in yourPATH
environment variable, add it if needed (e.g.export PATH=$HOME/bin:$PATH
)
KUBECONFIG is a YAML file containing the deteails of the k8s cluster, such as its address, and your own authentication credentials. It can be downloaded from the Spin.
- Login to rancher2.spin.nersc.gov;
- click the cluster name (as of May 12, 2024, either "development" or "production");
- hover the mouse pointer over the "page" icon on the top right of the page, it should say "Download KubeConfig", click it to download.
- create
$HOME/.kube
directory if not existing, and save the downloaded file to$HOME/.kube/config
; alternatively, you can set theKUBECONFIG
environment variable to the path to the downloaded YAML file.
Using kubectl
, create a kubeconfig
secret in the targeted namespace
(replace <targeted_namespace>
and <path to kubeconfig>
accordingly):
kubectl -n <targeted_namespace> create secret generic kubeconfig --from-file=kubeconfig=<path to kubeconfig>