You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context:
In our Spark infrastructure chart, which powers the Spark History Server, we create both an Ingress and a Service. The default configuration shows that the Ingress is set to target a Service called "spark-history." However, in the service.yaml template, the reference is hard-coded to "spark-infrastructure," which is incorrect for the Spark History Server.
If we test if ingress works by calling curl command curl spark-history.p.uip.sh, an error would pop up Could not resolve host: spark-history.p.uip.sh
when we check ingress by running kubectl describe ingress spark-infrastructure
we'll get spark-history:18080 (<error: endpoints "spark-history" not found>) error.
DOD
Reproduce the error:
Set up a pipeline containing a Spark application
Run tilt up and wait till spark-infrastructure successfully runs
Execute the command kubectl describe ingress spark-infrastructure
Rectify the problem by modifying the ingress.hosts.host.paths.backend.service.name from "spark-history" to "spark-infrastructure".
Test
Pull the latest baseline project
Run mvn clean install -f foundation/foundation-mda
Add the attached PysparkPipeline.json to -pipeline-models/src/main/resources/pipelines
Run the following: mvn clean install
Follow the manual action and then run till there's no more manual action updates popping up mvn clean generate-sources
Remove deployment.ingress.metadata.annotations in values.yaml. Add deployment.ingress.metadata.name with value ingress. Change value of deployment.ingress.hosts.host to spark-history.rancher.localhost
The deployment.ingress section should look like
PysparkPipeline.json
Context:
In our Spark infrastructure chart, which powers the Spark History Server, we create both an Ingress and a Service. The default configuration shows that the Ingress is set to target a Service called "spark-history." However, in the service.yaml template, the reference is hard-coded to "spark-infrastructure," which is incorrect for the Spark History Server.
If we test if ingress works by calling curl command
curl spark-history.p.uip.sh
, an error would pop upCould not resolve host: spark-history.p.uip.sh
when we check ingress by running
kubectl describe ingress spark-infrastructure
we'll get
spark-history:18080 (<error: endpoints "spark-history" not found>)
error.DOD
tilt up
and wait till spark-infrastructure successfully runskubectl describe ingress spark-infrastructure
ingress.hosts.host.paths.backend.service.name
from "spark-history" to "spark-infrastructure".Test
mvn clean install -f foundation/foundation-mda
mvn clean install
mvn clean generate-sources
deployment.ingress.metadata.annotations
invalues.yaml
. Adddeployment.ingress.metadata.name
with valueingress
. Change value of deployment.ingress.hosts.host tospark-history.rancher.localhost
The deployment.ingress section should look like
Run
Tilt up
and wait till spark-infrastructure pod successfully spinsEnter http://spark-history.rancher.localhost in the browser. (try chrome first, if not Firefox or safari)
Verify that it's error free (not 404)
The text was updated successfully, but these errors were encountered: