This fixes the communication of the Web UI component with Marquez AP… #2430
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.
…I service in the Helm Chart
Problem
Deploying the current Helm Chart in main results in a broken Marquez Web Component because of a misconfiguration in the Helm Chart. In the container spec in the Web deployment.yaml file two environment variables are set, i.e. MARQUEZ_HOST and MARQUEZ_PORT, for the instance to be able to communicate with the Marquez API service in the K8s cluster.
The MARQUEZ_PORT is erroneously set to 5000, .Values.marquez.port, the port number used internally in the container for the API, but the Marquez API service is exposed via port number 80, .Values.service.port, within the K8s cluster
Solution
Small fix: define the value for MARQUEZ_PORT as .Values.service.port, i.e. 80. That way Marquez Web component can communicate via http://marquez:80 with the API backend.
Checklist
CHANGELOG.md
with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary).sql
database schema migration according to Flyway's naming convention (if relevant)