You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@livy.apache.org by "Nilesh Rathi (Jira)" <ji...@apache.org> on 2026/08/10 08:50:00 UTC

[jira] [Commented] (LIVY-979) Create a helm-based integration environment for debugging Livy on Kubernetes

    [ https://issues.apache.org/jira/browse/LIVY-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18103315#comment-18103315 ] 

Nilesh Rathi commented on LIVY-979:
-----------------------------------

PR available at https://github.com/apache/livy/pull/537

> Create a helm-based integration environment for debugging Livy on Kubernetes
> ----------------------------------------------------------------------------
>
>                 Key: LIVY-979
>                 URL: https://issues.apache.org/jira/browse/LIVY-979
>             Project: Livy
>          Issue Type: Task
>          Components: Docs
>    Affects Versions: 0.7.0
>            Reporter: Asif Khatri
>            Assignee: Asif Khatri
>            Priority: Major
>             Fix For: 1.0.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Once Apache Livy gets Kubernetes support as part of LIVY-701, helm chart can be created to deploy Apache Livy on a Docker desktop with Kubernetes enabled.
> This helps deploy Livy on Kubernetes without relying on cloud services like AWS, GCP, Azure, etc. It can save development time/cost and help us debug it using an IDE. For debugging Livy on Kubernetes as a standalone machine, we need Apache Spark and Apache Livy deployed in Kubernetes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)