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
Copy file name to clipboardExpand all lines: docs/CustomResources.md
+39Lines changed: 39 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -403,6 +403,45 @@ spec:
403
403
replicas: 1
404
404
```
405
405
406
+
#### admin-managed-pv Annotations
407
+
The admin-managed-pv annotation in the splunk-operator's Custom Resource allows the admin to control whether Persistent Volumes (PVs) are dynamically created for the StatefulSet associated with the CR. If set to `true`, no PVs will be created, and the Persistent Volume Claim templates in the StatefulSet manifest will include a selector block to match `app.kubernetes.io/instance` and `app.kubernetes.io/name` labels for pre-created PVs. This means that `/opt/splunk/etc` and `/opt/splunk/var` related PVCs will contain code block like below
When admin-managed-pv is set to `false`, PVs will be dynamically created as usual, providing dedicated persistent storage for the StatefulSet.
432
+
433
+
Here is an example of a Standalone with the admin-managed-pv annotation set. After
434
+
```
435
+
apiVersion: enterprise.splunk.com/v4
436
+
kind: Standalone
437
+
metadata:
438
+
name: single
439
+
finalizers:
440
+
- enterprise.splunk.com/delete-pvc
441
+
annotations:
442
+
enterprise.splunk.com/admin-managed-pv: "true"
443
+
```
444
+
406
445
#### Container Logs
407
446
The Splunk Enterprise CRDs deploy Splunkd in Kubernetes pods running [docker-splunk](https://github.com/splunk/docker-splunk) container images. Adding a couple of environment variables to the CR spec as follows produces `detailed container logs`:
0 commit comments