Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 31 additions & 1 deletion hadoop-hdds/docs/content/start/Kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,6 @@ weight: 22
* kubectl
{{< /requirements >}}


As the _apache/ozone_ docker images are available from the dockerhub the deployment process is very similar to Minikube deployment. The only big difference is that we have dedicated set of k8s files for hosted clusters (for example we can use one datanode per host)
Deploy to kubernetes

Expand All @@ -51,3 +50,34 @@ Now you can access any of the services. By default the services are not publishe
kubectl port-forward s3g-0 9878:9878
kubectl port-forward scm-0 9876:9876
```

## Apache Ozone Helm Chart

For a streamlined and production-ready deployment of Apache Ozone on Kubernetes, consider using the [Apache Ozone Helm Chart](https://apache.github.io/ozone-helm-charts/). This Helm Chart simplifies the installation and management of an Ozone cluster by packaging best practices into a set of configurable Kubernetes resources.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would omit production-ready, implementation of HA is still in progress: apache/ozone-helm-charts#10

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. I just thought because all subtasks under HDDS-11027 except this documentation are done, the whole work is near completion.
Just now I see there are a couple other follow-on jiras still pending.

What's our plan here? Do we say the initial helm chart is done, we announce it; or do we wait for follow-on work before announce a release?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Version 0.1.0 was the initial release (HDDS-11039).


1. **Add the Ozone Helm Repository**

First, add the Apache Ozone Helm repository and update your local Helm repo cache:

```bash
helm repo add ozone-helm https://apache.github.io/ozone-helm-charts/
helm repo update
```

2. Install the Chart

Install the Ozone Helm Chart using the following command. This command deploys a default Ozone cluster:

```bash
helm install my-ozone-cluster ozone-helm/ozone
```

3. Customize Your Deployment

To customize the configuration, create or modify a values.yaml file with your desired settings and install the chart as follows:

```bash
helm install my-ozone-cluster -f values.yaml ozone-helm/ozone
```

For more detailed documentation and advanced configuration options, please refer to the [Apache Ozone Helm Chart](https://apache.github.io/ozone-helm-charts/) documentation.