Enhance Cryostat to support strict Kubernetes security contexts

[Prasunamadasu]

Describe the feature

We are using cryostat-v3.0, and it currently faces compatibility issues with strict Kubernetes security policies, specifically:

1. readOnlyRootFilesystem: true
2. Custom runAsGroup values

This makes it difficult to use Cryostat in environments that require strong security measures.

Feature Requests:

1. Support readOnlyRootFilesystem: true

• Identify all writable paths required by Cryostat components.
• Provide configuration options to mount these paths as writable volumes.

2. Enable Compatibility with Custom runAsGroup Values

• Ensure all Cryostat processes can run with non-default group IDs.
• Document any specific group ID requirements, if necessary.

Use Case

This feature will allow Cryostat to be deployed in high-security Kubernetes environments that enforce strict security contexts.

Anything other information?

No response