Kubernetes Patterns: Difference between revisions
Jump to navigation
Jump to search
| Line 47: | Line 47: | ||
{{Internal|Kubernetes_Patterns_Ambassador#Overview|Ambassador}} | {{Internal|Kubernetes_Patterns_Ambassador#Overview|Ambassador}} | ||
=Configuration Patterns= | =Configuration Patterns= | ||
{{External|https://12factor.net/config}} | |||
Mixing code and configuration is an anti-pattern for a continuous delivery approach, where the application image is created once and then moves unaltered through various stages of the deployment pipeline until reaches production. Configuration must be maintained separately. | Mixing code and configuration is an anti-pattern for a continuous delivery approach, where the application image is created once and then moves unaltered through various stages of the deployment pipeline until reaches production. Configuration must be maintained separately. | ||
==EnvVar Configuration== | ==EnvVar Configuration== | ||
Revision as of 23:06, 16 February 2024
External
- Kubernetes Patterns, 2nd Edition by Bilgin Ibryam, Roland Huss https://learning.oreilly.com/library/view/kubernetes-patterns-2nd/9781098131678/
Internal
Overview
Foundational Patterns
Predictable Demand
Declarative Deployment
Health Probe
Managed Lifecycle
Automated Placement
Behavioral Patterns
Batch Job
Periodic Job
Daemon Service
Singleton Service
Stateless Service
Stateful Service
Service Discovery
Self Awareness
Structural Patterns
Init Container
Sidecar
Adapter
Ambassador
Configuration Patterns
Mixing code and configuration is an anti-pattern for a continuous delivery approach, where the application image is created once and then moves unaltered through various stages of the deployment pipeline until reaches production. Configuration must be maintained separately.