document helm version upgrade

source/user_guide/FAQ_user.rst

@@ -3,7 +3,18 @@
 FAQ
 ===============================================================================
 
-**Why does Kubernetes indicat that it cannot pull image?** / **Job failed in log-fetcher-in-dev job : image can't pulled**
+Job failed in log-fetcher-in-dev job / image can't pulled
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+See :ref:`why_image_cannot_be_pulled`
+
+
+
+
+.. _why_image_cannot_be_pulled:
+
+Why does Kubernetes indicat that it cannot pull image?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you have a waring/error in job *log-fetcher-in-dev* despite job passed for *Build* and *deploy-example*, 
 
@@ -38,7 +49,8 @@ or if you get the "503 Service unavailable" page when trying to access to your a
 | If so, read :ref:`Private registry helm` to indicate that the registry is private, and then provide the credentials with :ref:`Define registry token`.
 
 
-**How to fix build error during docker-compose during R packages installation ?**
+How to fix build error during docker-compose during R packages installation ?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 During the build of docker image following ``docker-compose`` command line, it's possible that installation error occur.
 
@@ -125,3 +137,47 @@ After modification, you have just to run again the ``docker-compose`` command li
 
 
 
+.. _update_chart_dependency:
+How to upgrade my helm dependency / I can't enable a feature 
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Basic use case is that the doc mention a feature, you enable it in values.yaml, but don't see the effect. 
+The cause can be that you don't use latest version of the helm package, the part of the toolkit which provide feature such as storage, nodowntime, ... 
+Until June 2024, version was pinned to a specific version, only allowing minor release (see `Use 0.6.*`)
+We now recommend that you alsways use the latest version. 
+To do so update the file my-project/chart/Chart.yaml, set the version of the shiny-server dependency to ``*``.
+
+.. tabs::
+
+    .. code-tab:: yaml
+        :caption: Use latest version (recommended)
+        :emphasize-lines: 9
+        :selected:
+
+
+        apiVersion: v2
+        name: shiny-example
+        description: An example
+
+        ...
+
+        dependencies:
+        - name: shiny-server
+          version: "*"
+          repository: "https://gitlab.pasteur.fr/api/v4/projects/5334/packages/helm/stable"
+
+    .. code-tab:: yaml
+        :caption: Use 0.6.* (Until June 2024)
+        :emphasize-lines: 9
+
+
+        apiVersion: v2
+        name: shiny-example
+        description: An example
+
+        ...
+
+        dependencies:
+        - name: shiny-server
+          version: "~0.6.0"
+          repository: "https://gitlab.pasteur.fr/api/v4/projects/5334/packages/helm/stable"
\ No newline at end of file

source/user_guide/helm_settings.rst

@@ -463,7 +463,7 @@ Storage
 
 .. note::
 
-    This feature is in beta as of March 2024, and will be available in v0.7
+    This feature was released in v0.7, to update your dependencies, see :ref:`update_chart_dependency`
 
 By default, everything you write on the storage of your application is lost 
 when your application restart or have an upgrade.