You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Kubernetes focuses on persistent workloads, but ephemeral services do not require persistent resources after the job is complete. Ephemeral pods will introduce light-weight pods that can be automatically spun up or killed after completing specific tasks.
Solution
We can offer the option of labeling a pod as ephemeral when creating or deploying it. These pods can be scaled up or down based on demand, and automatic cleanup functionality can discard after the job is done or after a timeout.
Additional information
No response
👨👧👦 Contributing
🙋♂️ Yes, I'd love to make a PR to implement this feature!
The text was updated successfully, but these errors were encountered:
Problem
Currently, Kubernetes focuses on persistent workloads, but ephemeral services do not require persistent resources after the job is complete. Ephemeral pods will introduce light-weight pods that can be automatically spun up or killed after completing specific tasks.
Solution
We can offer the option of labeling a pod as ephemeral when creating or deploying it. These pods can be scaled up or down based on demand, and automatic cleanup functionality can discard after the job is done or after a timeout.
Additional information
No response
👨👧👦 Contributing
The text was updated successfully, but these errors were encountered: