Kubernetes Deployments: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
{{Internal|Kubernetes Deployment Manifest|Deployment Manifest}} | {{Internal|Kubernetes Deployment Manifest|Deployment Manifest}} | ||
=Pod Names= | =Pod Names= | ||
{{External|https://medium.com/faun/kubernetes-pod-naming-convention-78272fcc53ed}} | |||
⚠️ The pod template manifest allows specifying a pod name, however it will be ignored. If it is not specified, that is fine. The pod names will be generated based on the deployment name, appending random sequences of characters: | ⚠️ The pod template manifest allows specifying a pod name, however it will be ignored. If it is not specified, that is fine. The pod names will be generated based on the deployment name, appending random sequences of characters: | ||
<syntaxhighlight lang='text'> | <syntaxhighlight lang='text'> | ||
Revision as of 23:39, 20 October 2020
External
Internal
Overview
A Deployment brings scalability, self-healing, zero-downtime rolling updates and versioned rollbacks to a set of pods.
Deployment Manifest
Pod Names
⚠️ The pod template manifest allows specifying a pod name, however it will be ignored. If it is not specified, that is fine. The pod names will be generated based on the deployment name, appending random sequences of characters:
httpd-6b8bb7895d-m9bzt
Playground Example
Scaling
A Deployment has a Scale sub-resource, allowing it to be controlled by a horizontal pod autoscaler.