Serverless
Warning
This site is still under development.
Serverless Kubernetes allows you to run your applications without having to manage the underlying infrastructure and focus on your business logic. Different from other serverless solutions, CAPI Cloud allows you to run your applications on a Kubernetes cluster, giving you the flexibility of Kubernetes and the simplicity of serverless.
How it works
Your cluster will run on a shared Kubernetes cluster managed by CAPI Cloud and will be isolated from other clusters. You can deploy your applications to the cluster using the standard Kubernetes API and CAPI Cloud will take care of the rest.
The isolation works at three different levels:
Network: Each cluster has its own network and is isolated from other clusters. Your workloads can only communicate with other workloads in the same cluster. See Network Policies for more information.
API: Each cluster has its own Kubernetes API server and is isolated from other clusters. You can only access the API server of your cluster.
Kernel: Each cluster has its own kernel and is isolated from other clusters. Your workloads can only access the kernel of your cluster. See gVisor for more information.
Even if your cluster is a standard Kubernetes cluster, some features are not available due to the shared nature of the cluster. Some of these features are NodePort services, DaemonSets, HostPath volumes, or privileged containers.
Expose your applications
You can expose your applications using an Ingress. CAPI Cloud will automatically provision it to route traffic to your application; even if you have not deployed an Ingress controller to your cluster. You only need to create an Ingress resource and add an entry to your DNS server.
Note
You can add the cert-manager.io/cluster-issuer: letsencrypt-prod
annotation to your Ingress to automatically provision a TLS certificate for your application.
Autoscaling
CAPI Cloud will automatically scale your cluster based on the resource usage of your applications.
Storage
CAPI Cloud will automatically provision a Persistent Volume for your application when you create a Persistent Volume Claim.
Both ReadWriteOnce and ReadOnlyMany access modes are supported.