fix(deploy): upgrade minio version to fix CVE-2023-28432 #960
Conversation
![cr-gpt[bot]](https://avatars.githubusercontent.com/in/292659?s=60&v=4){kind=small}
| @@ -18,7 +18,7 @@ clusterDomain: cluster.local | |||
| ## | |||
| image: | |||
| repository: quay.io/minio/minio | |||
| tag: RELEASE.2023-02-27T18-10-45Z | |||
| tag: RELEASE.2023-03-22T06-36-24Z | |||
| pullPolicy: IfNotPresent | |||
|
|
|||
| imagePullSecrets: [] | |||
There was a problem hiding this comment.
with a code review for the patch.
The patch changes the tag of the image from RELEASE.2023-02-27T18-10-45Z to RELEASE.2023-03-22T06-36-24Z. This seems to be an update to a newer version of the image.
From a security perspective, this is a good change to make as it ensures that all components are up-to-date and no known vulnerabilities will exist in the code.
From a bug risk perspective, this change should not have any negative impact. The process of updating to a newer version of the image should be tested before deploying to production.
From an improvement perspective, I would suggest adding version control to the codebase (such as git). This will give you better control over the code and make it easier to track changes. Additionally, it will also provide a backup in case something goes wrong.
Ref: https://nvd.nist.gov/vuln/detail/CVE-2023-28432