This message was deleted.
# replication-troubleshootings
Slackbot
10/27/2022, 7:59 PMThis message was deleted.
d
Dusty Shapiro
10/27/2022, 8:10 PMWe don’t use localhost, but rather the service name of the web-app container. What do you see what you run
kubectl get svcDusty Shapiro
10/27/2022, 8:13 PMThis is my Airbyte URL:
Copy code
<http://airbyte-airbyte-webapp-svc:80>Dusty Shapiro
10/27/2022, 8:13 PMso I would try passing in
<http://airbyte-webapp:80>Dusty Shapiro
10/27/2022, 8:16 PMSorry - I’m not an employee just a fellow Helm user. My issue was I was trying to connect locally to Airbyte deployed in a dev/prod environment. I had to circumvent this by depoying a Docker container containing Octavia to each environment to connect. Wish I could help more!
✅ 1
h
Hrvoje Piasevoli
10/28/2022, 6:24 AMHi, your health check works because you are requesting it from a different environment context. From a docker container (Octavia) your localhost is reachable using host.docker.internal, so you need to use :
octavia --airbyte-url http://host.docker.internal:8000
Octavia is implemented as an alias to a command that actually starts a docker container on your host.
(From Docker docs):
I want to connect from a container to a service on the host
🔗
The host has a changing IP address (or none if you have no network access). We recommend that you connect to the special DNS name host.docker.internal which resolves to the internal IP address used by the host.
u
user
10/28/2022, 2:40 PMThanks for your input Dusty and Hrvoje! Fabiano, let me know if the latest comment helps!
f
Francisco Viera
10/29/2022, 11:43 PMits is ok?
Francisco Viera
10/30/2022, 1:10 AM@Nataly Merezhuk (Airbyte) i test this is ok
u
user
11/01/2022, 11:37 AMGreat to hear!
9 Views