The importance of the operation and maintenance of version

Two days ago I encountered a problem that Huawei to deploy an application in a cloud of container, no matter how updated version of the application seems to have not really been updated.

Here's a very interesting question: how do you judge the application is not updated problem, not solve the problem or updated?

This issue, so we addressed:

In all packaged java application (including front-end web application above all marked version), so I checked ... com / app1 / version / latest.json

image


Found git-sha is the old version, build time is not right.

From the above discovery version is v1.0, compilation time is 10:43, git-sha1 are d558049, based on this information to check whether to go with the latest code.

Huawei again to see if pushed to the cloud image library, according digest id is correct.

Finally I discovered that there are a k8s image pull policy, with Ifnotpresent, that is, if there is local, then do not pull the latest images.

Uh uh. . .

Instead always normal.


Back to the initial question: Do you now run the application, you know that it is a branch of git, which commit version of it?

Do not tell Bob, I want to I think. . . Do not you think. . .










Correct.

Guess you like

Origin www.cnblogs.com/king_astar/p/12329415.html