[HDDS-1381] Support cloud native Ozone deployment (Phase II)

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Target Version/s: 2.0.0
• Assignee: Marton Elek
• Reporter: Marton Elek
• Created: 04/Apr/19 12:29
• Updated: 16/Dec/23 23:43

Description

See the original HDDS-829 issue for the description why is it useful.

After the next phase we can run ozone in kubernetes but we have some additional tasks to do:

1. Implement customized CSI server instead of using the csi-s3 external server.
2. Provide example k8s deployment files as part of the release.
3. Provide example k8s deployment files for csi/monitoring/performance test, etc.
4. Add documentation how ozone can be started in k8s.

Issue Links

• is a clone of: HDDS-829 Support cloud native Ozone deployment

Sub-Tasks

• Create customized CSI server for Ozone: Resolved
• Provide example k8s deployment files as part of the release package: Resolved
• Provide k8s resources files for prometheus and performance tests: Resolved
• Ozone Manager can't be started with existing reverse dns: Open
• Provide example k8s deployment files for secure ozone setup: In Progress
• Provide example k8s deployment files for the new CSI server: Resolved
• Add liveness probe to the example k8s resources files: Resolved
• Support real persistence in the k8s example files: Resolved
• Add csi interface documents to show how to use ozone csi: Resolved
• Replace the imagePullPolicy from always to IfNotPresent: Resolved
• Update the apiVersion to the newer one: Resolved
• Remove podAntiAffinity from datanode-statefulset: Resolved
• Make CSI command configurable.: Resolved
• Add a readme documents for kubernetes/examples: Open