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
I'm not sure if I missed an updated values change somewhere between the versions, or if this is a bug?
Relevant log output
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking forshell scriptsin /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
/docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2024/05/10 16:33:43 [emerg] 1#1: host not found in upstream "$INTERNAL_API_HOST"in /etc/nginx/conf.d/default.conf:2
nginx: [emerg] host not found in upstream "$INTERNAL_API_HOST"in /etc/nginx/conf.d/default.conf:2
The text was updated successfully, but these errors were encountered:
Helm Chart Version
3.14.4
What step the error happened?
Upgrading the Platform or Helm Chart
Relevant information
Upgraded Airbyte version with webapp version
airbyte/webapp:0.50.51
toairbyte/webapp:0.58.1
using the latest helm release0.59.0
On startup the webapp pod was producing this error.
I figured the envvar must be missing so edited the Deployment spec on the cluster and adding that reference to the
env:
section. This got it running.I'm not sure if I missed an updated values change somewhere between the versions, or if this is a bug?
Relevant log output
The text was updated successfully, but these errors were encountered: