Merge pull request #357 from Qovery/update_helm_documentation_labels

Add warning on label/annotation to add

website/docs/using-qovery/configuration/helm.md

@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2023-12-19"
+last_modified_on: "2023-12-21"
 title: "Helm"
 description: "Learn how to configure your Helm on Qovery"
 ---
@@ -91,6 +91,24 @@ You can override values in the arguments section with the `--set` option.
 
 </Alert>
 
+<Alert type="warning">
+
+If you want to get all the Qovery features (access your container logs, apply the stop/restart actions, display the pod status in the overview page), make sure to create an override and assign the macros `qovery.labels.service` and `qovery.annotations.service` to the labels and annotations of any deployed Pods/Deployments/Services/Jobs.
+
+Override example:
+
+```yaml
+commonLabels:
+  mylabel: "test"
+  qovery.labels.service
+annotations:
+  qovery.annotations.service
+```
+
+These macros will be automatically replaced by Qovery during the deployment phase.
+
+</Alert>
+
 You can use the Qovery environment variables as overrides by using the placeholder “qovery.env.<env_var_name>” (Example: qovery.env.DB_URL. Qovery will manage the replacement of those placeholders at deployment time.
 
 </li>
@@ -222,6 +240,24 @@ You can override values in the arguments section with the `--set` option.
 
 </Alert>
 
+<Alert type="warning">
+
+If you want to get all the Qovery features (access your container logs, apply the stop/restart actions, display the pod status in the overview page), make sure to create an override and assign the macros `qovery.labels.service` and `qovery.annotations.service` to the labels and annotations of any deployed Pods/Deployments/Services/Jobs.
+
+Override example:
+
+```yaml
+commonLabels:
+  mylabel: "test"
+  qovery.labels.service
+annotations:
+  qovery.annotations.service
+```
+
+These macros will be automatically replaced by Qovery during the deployment phase.
+
+</Alert>
+
 ### Ports
 
 Within this section you can define the port exposed publicly.

website/docs/using-qovery/configuration/helm.md.erb

@@ -79,6 +79,24 @@ You can override values in the arguments section with the `--set` option.
 
 </Alert>
 
+<Alert type="warning">
+
+If you want to get all the Qovery features (access your container logs, apply the stop/restart actions, display the pod status in the overview page), make sure to create an override and assign the macros `qovery.labels.service` and `qovery.annotations.service` to the labels and annotations of any deployed Pods/Deployments/Services/Jobs.
+
+Override example:
+
+```yaml
+commonLabels:
+  mylabel: "test"
+  qovery.labels.service
+annotations:
+  qovery.annotations.service
+```
+
+These macros will be automatically replaced by Qovery during the deployment phase.
+
+</Alert>
+
 You can use the Qovery environment variables as overrides by using the placeholder “qovery.env.<env_var_name>” (Example: qovery.env.DB_URL. Qovery will manage the replacement of those placeholders at deployment time.
 
 </li>
@@ -210,6 +228,24 @@ You can override values in the arguments section with the `--set` option.
 
 </Alert>
 
+<Alert type="warning">
+
+If you want to get all the Qovery features (access your container logs, apply the stop/restart actions, display the pod status in the overview page), make sure to create an override and assign the macros `qovery.labels.service` and `qovery.annotations.service` to the labels and annotations of any deployed Pods/Deployments/Services/Jobs.
+
+Override example:
+
+```yaml
+commonLabels:
+  mylabel: "test"
+  qovery.labels.service
+annotations:
+  qovery.annotations.service
+```
+
+These macros will be automatically replaced by Qovery during the deployment phase.
+
+</Alert>
+
 ### Ports
 
 Within this section you can define the port exposed publicly.