Is there an existing issue for this?

• I have searched the existing issues
  To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.

Summary

There's competing needs for users of Appsmith: ensure that they stay up-to-date and also not surprise users with upgrades.

We have an autoupdate.enabled value in the Helm chart disabled by default, which would leave someone to believe that the their deployment wouldn't be automatically updated without their intervention. However, there's some behavior that's surprising users:

When someone installs from the Helm chart using the default values, the Deployment object references the Appsmith image using the latest tag by default, and the value for imagePullPolicy is also set to ifNotPresent. The combination of those two means that when operations happen in the Kubernetes cluster unrelated to Appsmith, like a node being replaced by an autoscaler or a Kubernetes upgrade happens, the Appsmith install is upgraded to whatever is latest. That happens despite having autoupdate.enabled enabled and has been surprising to some.

We should pin the version of the app in the Helm chart to ensure that users have to knowingly run helm upgrade or update their pinned version via values to make changes to their Appsmith install by default. Changes to the Helm chart can also be used to coordinate updates to new environment variables or other new things related to Appsmith that the app may need over time.

Why should this be worked on?

Reduction of surprising behavior by the default Helm chart deployment.