Skip to content

How to keep the data persistent for the dashy deployed in the kubernetes via Helm #6081

How to keep the data persistent for the dashy deployed in the kubernetes via Helm

How to keep the data persistent for the dashy deployed in the kubernetes via Helm #6081

Triggered via issue October 1, 2024 06:32
Status Success
Total duration 25s
Artifacts

lgtm-comment.yml

on: issue_comment
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
post
The following actions uses node12 which is deprecated and will be forced to run on node16: ddradar/choose-random-action@v1, ddradar/lgtm-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
post
The following actions use a deprecated Node.js version and will be forced to run on node20: ddradar/choose-random-action@v1, ddradar/lgtm-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
post
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/