Skip to content

Commit 51ec837

Browse files
Merge pull request #74 from marklogic/feature/CLD-687
CLD-687: readme for CLD-595/596
2 parents c4e5736 + 5f1f6f2 commit 51ec837

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

README.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -390,6 +390,16 @@ kubectl port-forward svc/marklogic 8000:8000
390390

391391
This pod can now be accessed via http://localhost:8001.
392392

393+
## Security Context
394+
395+
Security context defines privilege and access control settings for a Pod or Container. By default security context for containers is enabled with runAsUser, runAsNonRoot, allowPrivilegeEscalation settings. To configure these values for containers, set the containerSecurityContext in the values.yaml file or using the `--set` flag. Additional security context settings can be added to containerSecurityContext configuration. Please refer [https://kubernetes.io/docs/tasks/configure-pod-container/security-context/](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/).
396+
397+
## Network Policy
398+
399+
Note: To use network policies, you must be using a networking solution that supports NetworkPolicy. Creating a NetworkPolicy resource without a controller that implements it will have no effect. Please refer [https://kubernetes.io/docs/concepts/services-networking/network-policies/#prerequisites](https://kubernetes.io/docs/concepts/services-networking/network-policies/#prerequisites).
400+
401+
Use NetworkPolicy to control network traffic flow for your applications, it allows you to specify how pods should communicate over the network. By default network policy is disabled in the values.yaml file. Set the networkPolicy.enabled to true to enable the use of network policy resource, default ports are provided in the settings, you can define custom rules for the sources of the traffic to the desired ports.
402+
393403
## Notice
394404

395405
To use transactional functionality with MarkLogic, you have to set up Ingress and configure cookie-based session affinity. This function will be supported in a future release.
@@ -477,6 +487,13 @@ This table describes the list of available parameters for Helm Chart.
477487
| `logCollection.files.requestLogs` | Enable this parameter to enable collection of Marklogics request logs when log collection is enabled | `true` |
478488
| `logCollection.files.crashLogs` | Enable this parameter to enable collection of Marklogics crash logs when log collection is enabled | `true` |
479489
| `logCollection.files.auditLogs` | Enable this parameter to enable collection of Marklogics audit logs when log collection is enabled | `true` |
490+
| `containerSecurityContext.enabled` | Enable this parameter to enable security context for containers | `true` |
491+
| `containerSecurityContext.runAsUser` | User ID to run the entrypoint of the container process | `1000` |
492+
| `containerSecurityContext.runAsNonRoot` | Indicates that the container must run as a non-root user | `true` |
493+
| `containerSecurityContext.allowPrivilegeEscalation` | Controls whether a process can gain more privileges than its parent process | `true` |
494+
| `networkPolicy.enabled` | Enable this parameter to enable network policy | `false` |
495+
| `networkPolicy.customRules` | Placeholder to specify selectors | `{}` |
496+
| `networkPolicy.ports` | Ports to which traffic is allowed | `[8000, 8001, 8002]` |
480497

481498
# Known Issues and Limitations
482499

0 commit comments

Comments
 (0)