hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1412) Provide example k8s deployment files as part of the release package
Date Thu, 02 May 2019 09:18:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1412?focusedWorklogId=236181&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-236181

ASF GitHub Bot logged work on HDDS-1412:

                Author: ASF GitHub Bot
            Created on: 02/May/19 09:17
            Start Date: 02/May/19 09:17
    Worklog Time Spent: 10m 
      Work Description: elek commented on issue #719: HDDS-1412. Provide example k8s deployment
files as part of the release package
URL: https://github.com/apache/hadoop/pull/719#issuecomment-488606106
   This is reviewed as part of https://github.com/apache/hadoop/pull/783 by @anuengineer (that
patch based on this commit the PR contained both the commits). Merging it right now.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 236181)
    Time Spent: 1h 40m  (was: 1.5h)

> 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
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
> 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message