Use correct service name in livy ingress #60
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
andreas-eberle
force-pushed
the
fix-livy-ingress-service-name
branch
from
fe84a73 to
d39c314
Compare
|
Awesome catch @andreas-eberle . Thx for the contribution! |
jahstreet
approved these changes
Jan 14, 2021
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.
When I deployed the spark-cluster helm chart, I noticed the ingress config does not work. This is because the spark cluster helm chart changes the livy service name. However, in the ingress template of the livy chart, the configured value is not used. I fixed it by using the same function that is used in the service to generate the name there.