The operator acts like a SRE inside your own cluster, properly deploying and configuring the various Speedscale components.
The Speedscale Kubernetes Operator works similarly to a service mesh controller like Istio or Linkerd. It waits for deployments to be applied to the cluster that contain specific annotations. It then automatically stands up an isolation test environment around the deployment. The operator itself is a deployment that will be always present on the cluster.
The fastest and most reliable way to install Speedscale components is using the
speedctl install wizard.
kubectl create namespace speedscale
speedctl install operator
Answer the wizard's questions to install the Speedscale Operator and instrument your service with Speedscale.
Adding Image Pull Secrets
If you need custom image pull secrets (for example, if you're rehosting Speedscale images in a dedicated registry), you may provide one or more secret names with the
--imgpullsecrets argument, and the secrets will be attached to the service account.
speectl install --imgpullsecrets my-secret1,my-secret2p
Specifying nodeSelectors, tolerations and affinity
If you want to schedule Speedscale related resources only on certain nodes using the mechanisms mentioned, you can set these via the
values.yaml during Helm installation or by manually setting them on the
speedscale-operator deployment after initial install. The settings applied to the operator will be applied to all related resources whether they are present for the full control plane lifecycle or ephemeral during a replay.
Before you uninstall the operator, make sure that you have uninjected the sidecar from your pods.
To uninstall the Speedscale Operator, run the following command:
speedctl deploy operator | kubectl delete -f -
helm install speedscale-operator
kubectl delete namespace/speedscale
This command must be run to properly delete the Operator.