Product EULA
Spotinst SaaS service agreement
How does Spotinst Ocean work?
Spotinst Ocean improves on the foundation of our tried-and-true Kubernetes Autoscaler and provides pod-driven autoscaling for Kubernetes clusters. Ocean adjusts infrastructure capacity and size to meet pod, container, and application needs and makes sure that all pods in the cluster have a place and capacity to run. The icing on the cake is that beyond eliminating the overhead of maintaining and scaling infrastructure, Ocean significantly reduces costs by reliably leveraging excess capacity and automatically bin-packing containers to ensure the most efficient use of infrastructure. Ocean recognizes when multiple containers should be placed on the same instance, or when they should spread out across a group.
Ocean will work with a designated pod inside your Kubernetes cluster that will report constant updates about the clusters’ condition via a one-way link.
Using that information, Ocean will scale the cluster up or down according to the overall nodes utilization and your pods’ needs.
In order to create this connection between your k8s cluster and Ocean, you will need to implement a small configuration change on both the k8s cluster side and the Ocean side as instructed below:
In order to run the Spotinst in-cluster autoscaler, you’ll need to run the following controller application in your OpenShift cluster spotinst-kubernetes-cluster-controller
This controller needs the following parameters
spotinst.token – The Spotinst access token (can be generated from the Spotinst console / API)spotinst.account – The spotinst account Id (Learn more about Accounts and Organizations)spotinst.cluster-identifier – This identifier should be identical to the controllerClusterId parameter that was configured on the Ocean cluster.
Installation Instructions:
- Register to Spotinst Ocean
- Install using Helm (in the Ocean documentation there's explenation on Terraform and Kubectl installations as well)
- For helm versions
2.* and below:
# Create a ServiceAccount for Tiller$ kubectl create serviceaccount tiller \--namespace=kube-system
# Create a ClusterRoleBinding$ kubectl create clusterrolebinding tiller-cluster-rule \--clusterrole=cluster-admin \--serviceaccount=kube-system:tiller
# Patch Tiller's Deployment to use `tiller` service account$ kubectl patch deployment tiller-deploy \--namespace=kube-system \--patch='{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'
User Guide
Oceans Documentation
Support
For any issue or question, you can always contact support@spotinst.com.
