You need Kubernetes ClusterRole
authority to install the Operator in cluster
mode. You should use Cluster mode to do one of the following:
- Install a single Spinnaker Operator to manage an entire Kubernetes cluster of Spinnaker installations
- Install a single Armory Operator to manage an entire Kubernetes cluster of Armory CD installations
You can find the Operator's deployment configuration in spinnaker-operator/deploy/operator/cluster
after you download and unpack the archive. You don't need to update any configuration values.
-
Get the latest Operator release:
Armory Operator for Armory CD Installation
{{< figure src="/images/proprietary.svg" >}}
mkdir -p spinnaker-operator && cd spinnaker-operator bash -c 'curl -L https://github.com/armory-io/spinnaker-operator/releases/latest/download/manifests.tgz | tar -xz'
Spinnaker Operator for Open Source Spinnaker Installation
mkdir -p spinnaker-operator && cd spinnaker-operator bash -c 'curl -L https://github.com/armory/spinnaker-operator/releases/latest/download/manifests.tgz | tar -xz'
-
Install or update CRDs across the cluster:
kubectl apply -f deploy/crds/
-
Create the namespace for the Operator:
In
cluster
mode, if you want to use a namespace other thanspinnaker-operator
, you need to edit the namespace indeploy/operator/cluster/role_binding.yaml
.kubectl create ns spinnaker-operator
-
Install the Operator:
kubectl -n spinnaker-operator apply -f deploy/operator/cluster
-
Verify that the Operator is running:
kubectl -n spinnaker-operator get pods
The command returns output similar to the following if the pod for the Operator is running:
NAMESPACE READY STATUS RESTARTS AGE spinnaker-operator-7cd659654b-4vktl 2/2 Running 0 6s