[ 
https://issues.apache.org/jira/browse/HDDS-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-1412:
---------------------------------
    Labels: pull-request-available  (was: )

> Provide example k8s deployment files as part of the release package
> -------------------------------------------------------------------
>
>                 Key: HDDS-1412
>                 URL: https://issues.apache.org/jira/browse/HDDS-1412
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>
> In HDDS-872 we added Dockerfile and skaffold definition to run dev builds on 
> kubernetes. But it would be great to include example k8s resource definitions 
> helping the deployment of ozone to any kubernetes cluster.
> In this patch I will
> 1. Add k8s resources files to the release tar file to deploy basic ozone 
> cluster
> 2. Add Dockerfile to the release tar file to create custom ozone image any 
> time
> 3. Add additional maven profiles to build and push development docker images.
> 4. We don't need skaffold any more as the maven based approach is more 
> flexible (we can support multiple k8s definitions)
> To easily support multiple type of configuration (simple ozone, minikube, 
> csi) we need a basic set of k8s resources files and additional 
> transformations to generate the ready-to-use files for each specific 
> use-cases.
> The easiest way to do this is adopting the existing structure from 
> https://github.com/flokkr/k8s and use https://github.com/elek/flekszible 
> tool. But the tool itself is not required at runtime as we generate all the 
> required k8s resources files during the development and add the results to 
> the version control. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to