You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The helm chart supports image pinning and it's part of the default values.yaml.
However, doing the same with the Operator breaks the update checker.
To reproduce:
Set spec.version: 10.4.2 for the Mattermost resource; observe that it starts up fine
Set spec.version: 10.4.2@sha256:f655fae92b8126e7d7f5dcbb796a8bbe32883f0af9cd20841c1be035e241052f
Observe that the update checker fails to start up because the Operator sets an invalid image of mattermost/[email protected]@sha256:f655fae92b8126e7d7f5dcbb796a8bbe32883f0af9cd20841c1be035e241052f
The first @ should actually be a colon.
The text was updated successfully, but these errors were encountered:
The operator supports either the Tag or the Digest. This is not how dependency update tools like Renovate-Bot work, however. They set both in order to set the version to be used and to be able to compare the version number with available version numbers to create Pull Requests. The Digest is set to make sure that moving tags won't surprise us without being tested and from a security standpoint.
It would be awesome if the operator could be adjusted to support the scenario where the version contains the tag and the digest. A simple fix would be to change this line:
if strings.Contains(d.Version, "sha256:") {
with this:
if strings.HasPrefix(d.Version, "sha256:") {
Adding an @ as opposed to a : is only necessary if the version number only contains the digest. As soon as it contains something ahead of the digest, It's safe to assume that it's both.
The helm chart supports image pinning and it's part of the default values.yaml.
However, doing the same with the Operator breaks the update checker.
To reproduce:
spec.version: 10.4.2
for the Mattermost resource; observe that it starts up finespec.version: 10.4.2@sha256:f655fae92b8126e7d7f5dcbb796a8bbe32883f0af9cd20841c1be035e241052f
mattermost/[email protected]@sha256:f655fae92b8126e7d7f5dcbb796a8bbe32883f0af9cd20841c1be035e241052f
The first
@
should actually be a colon.The text was updated successfully, but these errors were encountered: