You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`imagePullSecrets`| Image pull secrets to be used for the Cryostat deployment |`[]`|
302
-
|`nameOverride`| Overrides the name of this Chart |`""`|
303
-
|`fullnameOverride`| Overrides the fully qualified application name of `[release name]-[chart name]`|`""`|
304
-
|`rbac.create`| Specifies whether RBAC resources should be created |`true`|
305
-
|`serviceAccount.create`| Specifies whether a service account should be created |`true`|
306
-
|`serviceAccount.annotations`| Annotations to add to the service account |`{}`|
307
-
|`serviceAccount.name`| The name of the service account to use. If not set and create is true, a name is generated using the fullname template |`""`|
308
-
|`podAnnotations`| Annotations to be applied to the various Pods |`{}`|
309
-
|`podSecurityContext`| Security Context for the Cryostat Pod. Defaults to meet "restricted" [Pod Security Standard](https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted). See: [PodSecurityContext](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context)|`{}`|
310
-
|`networkPolicy.ingress.enabled`| whether a NetworkPolicy for restricting Cryostat component Pods' traffic is installed. This prevents other Pods from sending unwanted traffic to Cryostat's Pods. Traffic should flow via the Service (or Route, or other Ingress) only, not by directly targeting Pods |`true`|
311
-
|`nodeSelector`| default Node Selector for the various Pods. Any Pod which does not have an individual nodeSelector setting will default to this. See: [NodeSelector](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#scheduling)|`{}`|
312
-
|`tolerations`| default Tolerations for the various Pods. See: [Tolerations](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#scheduling)|`[]`|
313
-
|`affinity`| default Affinity for the various Pods. See: [Affinity](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#scheduling)|`{}`|
|`imagePullSecrets`| Image pull secrets to be used for the Cryostat deployment |`[]`|
302
+
|`nameOverride`| Overrides the name of this Chart |`""`|
303
+
|`fullnameOverride`| Overrides the fully qualified application name of `[release name]-[chart name]`|`""`|
304
+
|`rbac.create`| Specifies whether RBAC resources should be created |`true`|
305
+
|`serviceAccount.create`| Specifies whether a service account should be created |`true`|
306
+
|`serviceAccount.annotations`| Annotations to add to the service account |`{}`|
307
+
|`serviceAccount.name`| The name of the service account to use. If not set and create is true, a name is generated using the fullname template |`""`|
308
+
|`podAnnotations`| Annotations to be applied to the various Pods |`{}`|
309
+
|`podSecurityContext`| Security Context for the Cryostat Pod. Defaults to meet "restricted" [Pod Security Standard](https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted). See: [PodSecurityContext](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context)|`{}`|
310
+
|`networkPolicy.ingress.enabled`| whether a NetworkPolicy for restricting Cryostat component Pods' inbound traffic is installed. This prevents other Pods from sending unwanted traffic to Cryostat's Pods. Traffic should flow via the Service (or Route, or other Ingress) only, not by directly targeting Pods. |`true`|
311
+
|`networkPolicy.egress.enabled`| whether a NetworkPolicy for restricting Cryostat component Pods' outbound traffic is installed. This prevents Cryostat's component Pods from opening connections to unexpected destinations. The policy will allow Cryostat's Pods to communicate with each other, to the cluster API server, and to any target namespaces (core.discovery.kubernetes.namespaces). This is off by default since some cluster network plugins cause JDBC connectivity issues between Cryostat and its database when this policy is activated. When enabled, Cryostat users will not be able to define Custom Targets that are located outside of the target namespaces defined at installation time. |`false`|
312
+
|`nodeSelector`| default Node Selector for the various Pods. Any Pod which does not have an individual nodeSelector setting will default to this. See: [NodeSelector](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#scheduling)|`{}`|
313
+
|`tolerations`| default Tolerations for the various Pods. See: [Tolerations](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#scheduling)|`[]`|
314
+
|`affinity`| default Affinity for the various Pods. See: [Affinity](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#scheduling)|`{}`|
0 commit comments