-
Notifications
You must be signed in to change notification settings - Fork 604
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubernetes ingress and needed port to use vespa #4511
Comments
I think it is due to the config server addr is not fully resolved with the hostname at boot time so i cant reach it outside of the container/pod. exec into it and curl -s --head localhost:19071/ApplicationStatus gets 200 OK.
wget -qO- 10.40.7.3:19071 But the logs kubectl logs vespa-1454932670-48t5x
|
Can anyone from vespa see if they can find any wrong with this log? mydomain/ApplicationStatus works (200 OK). But i fail to create a tenant with the rest API (http://docs.vespa.ai/documentation/cloudconfig/tenant-rest-api.html) and thus using the deploy API. The config server seems not be started (same as the previous thread opened) but this time i can see that the file Is it due to out of memory ? It is on a VM 3.75 GB
netstat
|
Closing. Configserver is working if exec into the container and using gce ingress rules with default backend. |
Hi!
I looked into this issue:
#3640
But could not make every part of vespa work to for example deploy apps and start using it.
Did you ever managed to created a ingress (i am on GKE) and manage it to work with vespa tools and endpoints ?
I can reach the config endpoint mydomain.com/ApplicationStatus due to the mapping in the ingress pointing to the config port (nodeport service).
But now i am trying to use the deploy API with the endpoints in:
http://docs.vespa.ai/documentation/cloudconfig/deploy-rest-api-v2.html#use-cases
It seems that i need to have multiple (at least two ports 80(80) and 19071 on the same domain open) and ingress does not support that without specify different paths
kubernetes/ingress-nginx#1655
POSTING to
http://mydomain.com/application/v2/tenant/mytenant/session
just return 404 -default backend
and specify
http://mydomain.com:19701/application/v2/tenant/mytenant/session
hangs.
Anyone has a suggestion how i can create the ingress exposing needed ports ? Mabey one can create multiple services maped to different hosts (vespaapi.mydomain.com using 19071 and mydomain.com using 80)
Service:
Ingress:
The text was updated successfully, but these errors were encountered: