[LIVY-979][Dev] A helm-based integration environment for Livy #454
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nileshrathi345
approved these changes
Aug 12, 2024
|
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.