DevOps/truecharts
2
0
Fork 0
Code Issues Pull Requests Actions 27 Packages Projects Releases 1 Wiki Activity

Commit daily changes

Browse Source 
Signed-off-by: TrueCharts-Bot <bot@truecharts.org>
This commit is contained in:
TrueCharts-Bot
2025-05-11 00:19:57 +00:00
parent ad1c77f769
commit 0c7f4b78d7
3 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
charts/library/common-test/Chart.yaml
+1
View File
@@ -35,3 +35,4 @@ sources:
- https://github.com/truecharts/charts/tree/master/charts/library/common-test
type: application
version: 1.0.0
charts/stable/neko/Chart.yaml
+1
View File
@@ -46,3 +46,4 @@ sources:
- https://github.com/truecharts/charts/tree/master/charts/stable/neko
type: application
version: 9.0.7
website/src/content/docs/guides/fluxcd/deploychart.md
+5 -5
View File
@@ -8,15 +8,15 @@ This guide will explain briefly how to deploy a chart on your brand new Clustert
## Create the files
- Your charts can be placed in the folder `clusters/main/kubernetes/apps/`.
- Your charts can be placed in the folder `clusters/main/kubernetes/apps/`.
- There will make a folder for your `chart` and inside that folder an `app` folder.
- In this guide we will use as example `librespeed`
- So it will be like: `clusters/main/kubernetes/apps/librespeed/app/`
- In this folder we will create two files, `helm-release.yaml` and `namespace.yaml`.
- In this folder we will create two files, `helm-release.yaml` and `namespace.yaml`.
:::note[Folder Structure]
You are not limited to only use the `clusters/main/kubernetes/apps` folder. You can make any folder with subfolders in `clusters/main/kubernetes/` to organize your charts.
You are not limited to only use the `clusters/main/kubernetes/apps` folder. You can make any folder with subfolders in `clusters/main/kubernetes/` to organize your charts.
:::
@@ -28,13 +28,13 @@ kind: Namespace
metadata:
name: librespeed
## Add this part when you need a privileged namespace
# labels:
# labels:
# pod-security.kubernetes.io/enforce: privileged
```
:::warning[Privileged Namespace]
Add the label for pod-security only when it is really needed. After deploying the chart and this part will be needed you will see this in your event logs.
Add the label for pod-security only when it is really needed. After deploying the chart and this part will be needed you will see this in your event logs.
:::