Stash operator can be installed via a script or as a Helm chart.
Using Script
To install Stash in your Kubernetes cluster, run the following command:
$ curl -fsSL https://github.com/stashed/installer/raw/v0.9.0-rc.2/deploy/stash.sh | bash
After successful installation, you should have a stash-operator-*** pod running in the kube-system namespace.
$ kubectl get pods -n kube-system | grep stash-operator
stash-operator-846d47f489-jrb58 1/1 Running 0 48s
Customizing Installer
The installer script and associated yaml files can be found in the /deploy folder. You can see the full list of flags available to installer using -h flag.
$ curl -fsSL https://github.com/stashed/installer/raw/v0.9.0-rc.2/deploy/stash.sh | bash -s -- -h
stash.sh - install stash operator
stash.sh [options]
options:
-h, --help show brief help
-n, --namespace=NAMESPACE specify namespace (default: kube-system)
--docker-registry docker registry used to pull stash images (default: appscode)
--pushgateway-registry docker registry used to pull Prometheus pushgateway image (default: prom)
--image-pull-secret name of secret used to pull stash operator images
--run-on-master run stash operator on master
--enable-mutating-webhook enable/disable mutating webhooks for Kubernetes workloads
--enable-validating-webhook enable/disable validating webhooks for Stash crds
--bypass-validating-webhook-xray if true, bypasses validating webhook xray checks
--enable-status-subresource if enabled, uses status sub resource for crds
--use-kubeapiserver-fqdn-for-aks if true, uses kube-apiserver FQDN for AKS cluster to workaround https://github.com/Azure/AKS/issues/522 (default true)
--enable-analytics send usage events to Google Analytics (default: true)
--uninstall uninstall stash
--purge purges stash crd objects and crds
--monitoring-agent specify which monitoring agent to use (default: none)
--monitoring-backup specify whether to monitor stash backup and restore activity (default: false)
--monitoring-operator specify whether to monitor stash operator (default: false)
--prometheus-namespace specify the namespace where Prometheus server is running or will be deployed (default: same namespace as stash-operator)
--servicemonitor-label specify the label for ServiceMonitor crd. Prometheus crd will use this label to select the ServiceMonitor. (default: 'app: stash')
If you would like to run Stash operator pod in master instances, pass the --run-on-master flag:
$ curl -fsSL https://github.com/stashed/installer/raw/v0.9.0-rc.2/deploy/stash.sh \
| bash -s -- --run-on-master
Stash operator will be installed in a kube-system namespace by default. If you would like to run Stash operator pod in stash namespace, pass the --namespace=stash flag:
$ kubectl create namespace stash
$ curl -fsSL https://github.com/stashed/installer/raw/v0.9.0-rc.2/deploy/stash.sh \
| bash -s -- --namespace=stash [--run-on-master]
If you are using a private Docker registry, you need to pull the following image:
To pass the address of your private registry and optionally a image pull secret use flags --docker-registry and --image-pull-secret respectively.
$ kubectl create namespace stash
$ curl -fsSL https://github.com/stashed/installer/raw/v0.9.0-rc.2/deploy/stash.sh \
| bash -s -- --docker-registry=MY_REGISTRY [--image-pull-secret=SECRET_NAME]
Stash implements validating admission webhooks to validate Stash CRDs and mutating webhooks for Kubernetes workload types. This is helpful when you create Restic before creating workload objects. This allows stash operator to initialize the target workloads by adding sidecar or, init-container before workload-pods are created. Thus stash operator does not need to delete workload pods for applying changes. This is particularly helpful for workload kind StatefulSet, since Kubernetes does not support adding sidecar / init containers to StatefulSets after they are created. This is enabled by default for Kubernetes 1.9.0 or later releases. To disable this feature, pass the --enable-validating-webhook=false and --enable-mutating-webhook=false flag respectively.
$ curl -fsSL https://github.com/stashed/installer/raw/v0.9.0-rc.2/deploy/stash.sh \
| bash -s -- --enable-validating-webhook=false --enable-mutating-webhook=false
Stash v0.9.0-rc.2 or later releases can use status sub resource for CustomResourceDefintions. This is enabled by default for Kubernetes 1.11.0 or later releases. To disable this feature, pass the --enable-status-subresource=false flag.
Using Helm 2
Stash can be installed via Helm using the chart from AppsCode Charts Repository. To install the chart with the release name my-release:
$ helm repo add appscode https://charts.appscode.com/stable/
$ helm repo update
$ helm search appscode/stash
NAME CHART VERSION APP VERSION DESCRIPTION
appscode/stash v0.9.0-rc.2 v0.9.0-rc.2 Stash by AppsCode - Backup your Kubernetes Volumes
$ helm install appscode/stash --name stash-operator --version v0.9.0-rc.2 --namespace kube-system
To see the detailed configuration options, visit here.
Using Helm 3
Stash can be installed via Helm using the chart from AppsCode Charts Repository. To install the chart with the release name my-release:
$ helm repo add appscode https://charts.appscode.com/stable/
$ helm repo update
$ helm search repo appscode/stash
NAME CHART VERSION APP VERSION DESCRIPTION
appscode/stash v0.9.0-rc.2 v0.9.0-rc.2 Stash by AppsCode - Backup your Kubernetes Volumes
$ helm install stash-operator appscode/stash --version v0.9.0-rc.2 --namespace kube-system
To see the detailed configuration options, visit here.
If you are installing Stash on a GKE cluster, you will need cluster admin permissions to install Stash operator. Run the following command to grant admin permision to the cluster.
Now, to confirm CRD groups have been registered by the operator, run the following command:
Stash provides a CLI using kubectl plugin to work with the stash Objects quickly. Download pre-build binaries from stashed/cli Githhub release and put the binary to some directory in your PATH. To install linux 64-bit you can run the following commands:
If you prefer to install kubectl Stash cli from source code, you will need to set up a GO development environment following these instructions. Then, install the CLI using go get from source code.
