Welcome to the Linux Foundation Forum!

Rolling Update vs Revisions

Hello,

This question is about Lesson 9, Deployments (II).

I am confused about the term revision.

The lesson states that a revision is triggered as a result of a planned action, such as an update in the container image, port, volumes, mounts... Whereas a change in the deployment template (ie update in the container image) would trigger a Rolling update.

I am confused when the lesson states that after the Rolling update has been implemented, K8s records the prior state changes of the Deployment as a Revision.

I would appreciate if someone could kindly shed some light on this.

Thank you.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Best Answer

Answers

  • Posts: 82
    edited October 2024

    Following the demo "Demo: Deployment Rolling Update and Rollback", I can see that once a deployment has been rollout, it becomes Revision 1 (for the original version), then when there are changes on the Deployment template, it becomes Revision n+1 after changes have been rollout.

  • My apologies, comment above is not correct.

  • @chrispokorni , thank you.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training