Since our chart upgrades from

0.45.1

to

0.42.0

, I am seeing this error when attempting to deploy :

Error: template: airbyte/charts/webapp/templates/ingress.yaml:53:33: executing "airbyte/charts/webapp/templates/ingress.yaml" at <.Release.Name>: nil pointer evaluating interface {}.Name

Not just your ingress are causing the issue, the whole deployment is broken. Even using the default values you will not be able to deploy the airbyte

Curious why that is?

I really dont know the reason, but now Im getting this error at server pod:

INTERNAL_API_HOST environment cannot be null

How is Airbyte deployed for you @Luan Carvalho?

I'm deploying trough helm install

Agreed. I know this might sound like a terrible question, but can you set that environment variable to something?

Yep, I can. Do you have some recommendation?

Why not this value?

Now I'm far from the pc but asap I will test it

A new chart version?

Yep, check artifacthub

I’m a bit confused as to why the helm chart doesn’t work with all defaults values. I did as suggested and added:

server:
  extraEnv:
    - name: INTERNAL_API_HOST
      value: airbyte-server:8001

..which resolves the

INTERNAL_API_HOST environment cannot be null

error, but the airbyte-server pod never starts successfully and goes into a CrashLoopBackOff.

You did this test with the new version, right ? @Dominik Mall

I believe so

➜ helm search repo airbyte 
NAME                      	CHART VERSION	APP VERSION  	DESCRIPTION                             
airbyte/airbyte           	0.40.6       	0.40.6       	Helm chart to deploy airbyte            
airbyte/airbyte-bootloader	0.40.6       	0.40.5       	Helm chart to deploy airbyte-bootloader 
airbyte/metrics           	0.40.6       	0.40.3       	Helm chart to deploy airbyte-metrics    
airbyte/pod-sweeper       	0.40.6       	0.39.37-alpha	Helm chart to deploy airbyte-pod-sweeper
airbyte/server            	0.40.6       	0.40.5       	Helm chart to deploy airbyte-server     
airbyte/temporal          	0.40.6       	0.40.5       	Helm chart to deploy airbyte-temporal   
airbyte/webapp            	0.40.6       	0.40.5       	Helm chart to deploy airbyte-webapp     
airbyte/worker            	0.40.6       	0.40.5       	Helm chart to deploy airbyte-worker

I am using newest chart, but still getting above error

Yeah, same here

I’m curious @Dominik Mall, if you output the logs of the webserver pod when it tries to start, if it throws a useful error

Nope it doesn’t throw any errors in the logs - in describe it fails the liveness and ready probes:

Warning  Unhealthy         13m (x6 over 14m)    kubelet                                Liveness probe failed: Get "http://<ip>:8001/api/v1/health": dial tcp <ip>:8001: connect: connection refused
  Warning  Unhealthy         10m (x28 over 14m)   kubelet                                Readiness probe failed: Get "http://<ip>:8001/api/v1/health": dial tcp <ip>:8001: connect: connection refused

@Dominik Mall Changing the image you could deploy airbyte or you still getting some error ?

yes it now deploys and i can get to the UI - didn’t try setting up a connection yet, also submitted a PR with the fix: https://github.com/airbytehq/airbyte/pull/16806

Nice, I will test it, thank you !