Nodeless Kubernetes for Single Cloud
Nodeless Kubernetes provisions just-in-time right-sized cost-effective compute for your app when your app starts and terminates the compute when the app terminates. This eliminates operational complexity, prevents wasted spend, and strengthens multi-tenant security.
Build/test workloads are bursty in nature and require predictable resources. Nodeless is a great fit for CI since it eliminates wait times during unexpected spikes and prevents wasted spend on unused capacity during downtimes (ex: nights, weekends). Nodeless works seamlessly with any CI orchestrator you have in place (Buildkite, CircleCI, GitHub Actions, Jenkins, etc).
“At Flare.build, we needed an auto-scaling solution for CI on GKE and EKS as part of our fully-managed Buildkite and Bazel offering. Nodeless Kubernetes helps us scale Buildkite agents and underlying infrastructure automatically based on pending build jobs, thereby simplifying operations; this allows us to effectively and efficiently manage thousands of CI machines for hundreds of customers with a small team.”
- Zach Gray, CEO, Flare.build
ML workloads like Ray are a great fit for Nodeless since they are bursty and benefit from GPU devices which are expensive to waste. Join us at 2021 Cloud Native Rejekts to learn more about Ray on Nodeless Kubernetes!
Nodeless Kubernetes for Mac
The availability of mac1.metal instances on AWS is a game-changer in consolidating Mac workloads on the cloud. Whether it is iOS build and test workloads, or prod, you no longer need to special-case Mac in your Operations. Nodeless Kubernetes eliminates DevOps overhead associated with:
Since mac1.metal is a bare metal form factor billed at 24-hour cadence, Nodeless Kubernetes is a great way to auto-magically consume cloud Mac shapes instead of fussing over hand managing bare metal and worrying about the billing cycle.
Nodeless Kubernetes for Multi Cloud
Heterogenous compute shapes across various cloud providers makes it hard to manually figure out which workloads stacks need to land on which cloud provider’s Kubernetes control plane. For example, should your healthcare stack run on a cloud provider with the best HIPAA compliance today? What if a different cloud provider offers a better HIPAA compliance story in 3 months?
Nodeless Kubernetes enables you to use a single Kubernetes control plane to schedule workloads across EKS/AKS/GKE/OKE based on application SLAs (ex: “my app needs to be alive in 5 seconds”) and user-defined policies (ex: low-cost, HIPAA, SOC 2).
Nodeless Kubernetes for Hybrid Cloud
If you have a primary compute footprint on an on-prem data center and want to consume public cloud occasionally for unexpected compute needs (ex: a spike in workload during Black Friday), it does not make sense to spend time and money maintaining a Kubernetes control plane on a cloud vendor for “just in case” needs.
Nodeless Kubernetes is a good fit to burst from the on-prem control plane to the public cloud seamlessly during spikes and bring back compute to the on-prem once the spike passes. Learn more about cloud bursting using Nodeless in this CNCF webinar!