Kubernetes Deployments Again

 

๐—ž๐˜‚๐—ฏ๐—ฒ๐—ฟ๐—ป๐—ฒ๐˜๐—ฒ๐˜€ ๐——๐—ฒ๐—ฝ๐—น๐—ผ๐˜†๐—บ๐—ฒ๐—ป๐˜๐˜€ ๐—”๐—ด๐—ฎ๐—ถ๐—ป

Deployment defines the desired state of a set of replica Pods. Kubernetes maintains that desired state by deleting, creating, and replacing those Pods.


It creates replicas to maintain its continuous status and determines the number of copies of the container. Kubernetes deployments offer scalability and applicability.


๐—ž๐˜‚๐—ฏ๐—ฒ๐—ฟ๐—ป๐—ฒ๐˜๐—ฒ๐˜€ ๐—ฅ๐—ผ๐—น๐—น๐—ผ๐˜‚๐˜ ๐——๐—ฒ๐—ฝ๐—น๐—ผ๐˜†๐—บ๐—ฒ๐—ป๐˜


๐˜™๐˜ฆ๐˜ค๐˜ณ๐˜ฆ๐˜ข๐˜ต๐˜ฆ


Deleting all the previous pods and targeting new pods. This provides some issues when updating. One is that needs to stop the service from going onto the app.


๐˜™๐˜ฐ๐˜ญ๐˜ญ๐˜ช๐˜ฏ๐˜จ ๐˜œ๐˜ฑ๐˜ฅ๐˜ข๐˜ต๐˜ฆ


One by one changing from the original state to the new one. Half of the pod remains and half are changed then half service webpage and the remaining are updated.


What do you think?

Just Be Sure

Post a Comment

0 Comments