Merge pull request #99 from stefanprodan/pod-security-profile

Allow setting the pod security labels on the Flux namespace

Author: stefanprodan

README.md

@@ -46,7 +46,7 @@ see [timoni.sh](https://timoni.sh/install/).
 ### Install Flux on self-managed clusters
 
 To deploy Flux AIO on a cluster without a CNI, create a Timoni Bundle file
-named `flux-aio.cue` with the following content: 
+named `flux-aio.cue` with the following content:
 
 ```cue
 bundle: {
@@ -85,6 +85,16 @@ values: env: {
 }
 ```
 
+Note that on [Talos](https://github.com/siderolabs/talos) clusters, you'll have to set the pod security profile to
+`privileged`:
+
+```cue
+values: {
+	hostNetwork:     true
+	podSecurityProfile: "privileged"
+}
+```
+
 You can fine tune the Flux installation using various options, for more information see
 the [installation guide](https://timoni.sh/flux-aio/#flux-installation).
 

modules/flux-aio/README.md

@@ -88,6 +88,7 @@ flux -n flux-system uninstall
 | `imagePullSecret: username:` | `string`                           | `null`                        | Registry username for the generated image pull secret                                                                                                                                    |
 | `imagePullSecret: password:` | `string`                           | `null`                        | Registry password for the generated image pull secret                                                                                                                                    |
 | `compatibility:`             | `string`                           | `kubernetes`                  | Can be set to `openshift` to make the security context compatible with RedHat OpenShift                                                                                                  |                                                                                                 |
+| `podSecurityProfile:`        | `string`                           | `""`                          | Can be `privileged` or `restricted`, used for setting the `pod-security.kubernetes.io` labels on the namespace                                                                           |
 
 ### Controllers
 

modules/flux-aio/debug_values.cue

@@ -63,8 +63,9 @@ values: {
 		identity: "arn:aws:iam::111122223333:role/my-role"
 		provider: "aws"
 	}
-	hostNetwork:     true
-	securityProfile: "privileged"
+	hostNetwork:        true
+	podSecurityProfile: "privileged"
+	securityProfile:    "privileged"
 	resources: {
 		requests: {
 			cpu:    "250m"

modules/flux-aio/templates/config.cue

@@ -64,6 +64,8 @@ import (
 
 	securityProfile: "restricted" | "privileged"
 
+	podSecurityProfile: *"" | "restricted" | "privileged"
+
 	logLevel: *"info" | string
 
 	hostNetwork: *true | bool

modules/flux-aio/templates/namespace.cue

@@ -10,7 +10,14 @@ import (
 	kind:       "Namespace"
 	metadata: {
 		name:        #config.metadata.namespace
-		labels:      #config.metadata.labels
 		annotations: #config.metadata.annotations
+		labels:      #config.metadata.labels
+		if #config.podSecurityProfile != "" {
+			labels: {
+				"pod-security.kubernetes.io/enforce": #config.podSecurityProfile
+				"pod-security.kubernetes.io/warn":    #config.podSecurityProfile
+				"pod-security.kubernetes.io/audit":   #config.podSecurityProfile
+			}
+		}
 	}
 }