Optimizing Modern Kubernetes environments demands more than just one-time or manual effort. They require continuous optimization that you can run confidently in production—without compromising application availability. That’s the foundation of Ocean, Flexera’s container optimization solution.
Ocean continuously optimizes Kubernetes clusters to deliver maximum efficiency and cost savings by:
- Handling Spot Instance interruptions automatically
- Right-Sizing cluster workloads automatically
- Rebalancing nodes through intelligent bin-packing
- Reverting workloads to lower-cost instance types
- Moving capacity back to Spot when possible
- Leveraging unused Savings Plans and Reserved Instances
These actions unlock significant, ongoing savings—but they also involve node replacement and pod eviction.
The Kubernetes eviction gap
In standard Kubernetes behavior, availability risks can emerge when resources are insufficient. By default, when a node is drained:
- Pods are evicted first
- Traffic stops flowing to them
- Replacement pods are created afterward by the ReplicaSet
- Those pods can be in a “Pending” state until there is sufficient capacity
For single-replica, stateful, or latency-sensitive workloads, even a short interruption can translate into failed requests, degraded user experience, or missed SLAs.
This often forces teams to slow down optimization, limit Spot usage, or accept unnecessary costs just to stay safe.
Introducing Pre-Eviction Warmup in Ocean: optimization that adapts to applications
Pre-Eviction Warmup changes the eviction flow – without slowing Ocean down.
When enabled for a workload, Ocean ensures that:
- A replacement pod is created first
- The new pod reaches a Ready state
- A configurable warmup period is honored
- Only then is the original pod evicted
In other words, capacity is added before capacity is removed.
Traffic continues to flow, requests are served seamlessly, and applications remain available – even during Spot interruptions or aggressive cost-driven node replacements.
Simple to enable, built for flexibility
Pre-Eviction Warmup is enabled directly in your Deployment spec:
The value is defined as a duration string (for example 30s, 2m, or 5m), giving teams flexible, human-readable control over warmup behavior per workload.
The label value defines the maximum time Ocean will wait between creating the warmup replacement pod and evicting the original one.
Even when platform eviction deadlines are tight, Ocean behaves safely—evicting the pod up to 5 seconds before the enforced deadline if required.
The real value: freedom to optimize boldly
Pre-Eviction Warmup doesn’t just prevent downtime – it fundamentally expands what teams can safely do with Ocean.
Unlock deeper savings
Run production workloads on Spot with confidence and allow Ocean to rebalance more aggressively.
Always-on optimization
No need to pause, throttle, or second-guess optimization cycles to protect availability.
Application-aware decisions
Ocean goes beyond infrastructure signals, aligning optimization actions with workload readiness.
Production-grade reliability
Ideal for customer-facing, revenue-critical, and stateful services where seconds matter.
Granular control
Opt-in per workload using simple Kubernetes labels – apply protection exactly where it’s needed.
Optimize boldly. Stay online.
With Pre-Eviction Warmup, Ocean removes the final barrier between aggressive Kubernetes optimization and production-grade availability.
Ready to optimize without compromise?
Learn more about Ocean or reach out to see Pre-Eviction Warmup in action.
