[LIVY-979][Dev] A helm-based integration environment for Livy
This helps deploy Livy on Kubernetes on a local machine. For debugging Livy on Kubernetes as a standalone setup, we need Apache Spark and Apache Livy deployed within the Kubernetes environment.
What changes were proposed in this pull request?
JIRA: LIVY-979
How was this patch tested?
Tested by deploying the Helm chart on a standalone machine.
Thank you for the submission and reviews! However some of the newly added files are missing the Apache license headers and I am not sure if this is OK to be merged in its current form. The policy I am referring to is https://apache.org/legal/src-headers.html
A year has gone by are we gonna let the headers be the blocker?
I just packaged up livy here: https://hub.docker.com/r/ecapriolo/livy
Do you wall want to merge this or should I fork it off and maintain on my own?
@edwardcapriolo I think the missing license headers are an issue that blocks merging (somebody who is more familiar with ASF policies or licensing please let me know if this is incorrect). If the PR could be updated and testing is successful, it would be possible to merge this and I think it would be a very useful addition.