- Kubernetes Design Patterns and Extensions
- Onur Yilmaz
- 161字
- 2021-07-23 16:57:38
Job Pattern
The general use case of pods in Kubernetes is that they are used for long-running processes that are always up. To this aim, Kubernetes provides higher-level resources such as replication sets or deployments. These high-level resources manage the life cycles of pods by creating replicas, checking for health statuses, and controlling update mechanisms. On the other hand, there is a need for microservices that do one job and successfully exit upon completion. For instance, database initializations, backups, or converting a video should run once and exit without consuming any extra resources. For this requirement, Kubernetes provides a higher-level resource named Job. Kubernetes jobs represent an isolated work run until completion and are ideal for use cases that are required to only run once.
- For always running pods, the restartPolicy is set to Always
- For jobs, the restartPolicy could be set as OnFailure or Never
- 電氣自動化專業英語(第3版)
- 自動控制工程設計入門
- 軟件架構設計
- Spark編程基礎(Scala版)
- TIBCO Spotfire:A Comprehensive Primer(Second Edition)
- 流處理器研究與設計
- JMAG電機電磁仿真分析與實例解析
- PostgreSQL Administration Essentials
- JBoss ESB Beginner’s Guide
- AWS Administration Cookbook
- Embedded Programming with Modern C++ Cookbook
- PostgreSQL 10 Administration Cookbook
- 網絡服務搭建、配置與管理大全(Linux版)
- INSTANT VMware vCloud Starter
- 三菱FX/Q系列PLC工程實例詳解