https://linen.dev logo
Join Slack
Powered by
Hello Team, I am trying to install airbyte on our ...
# replication-ask-ai
a
Hello Team, I am trying to install airbyte on our K8s environment by passing the custom values file. I am getting the below error 
Error: INSTALLATION FAILED: template: airbyte/charts/worker/templates/deployment.yaml:139:17: executing "airbyte/charts/worker/templates/deployment.yaml" at <$.Values.global.jobs.kube.annotations>: nil pointer evaluating interface {}.kube
k
I'm sorry, but without the specific error message, it's difficult to provide a solution. However, I can guide you through the general process of deploying Airbyte on Kubernetes using a custom 
values.yaml
file. 1. Create a 
values.yaml
file in your local folder and populate it with your custom configuration override values. An example of 
values.yaml
can be found in the [Airbyte repository](https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/values.yaml). 2. After specifying your own configuration, run the following command:
Copy code
bash helm install --values path/to/values.yaml %release_name% airbyte/airbyte
If you're still encountering issues, please provide the specific error message you're seeing. This will help in diagnosing the problem and providing a more accurate solution.
a
This is the error 
Error: INSTALLATION FAILED: template: airbyte/charts/worker/templates/deployment.yaml:139:17: executing "airbyte/charts/worker/templates/deployment.yaml" at <$.Values.global.jobs.kube.annotations>: nil pointer evaluating interface {}.kube
c
what version of airbyte are you using? What does your custom values file look like, in particular the yaml that references that area (or lack thereof)? What command are you running?
a
My bad I have something wrong with my values.yaml and that was sorted out and airbyteBootLoader pod is starting. I am encountering 
Connection to airbyte-db-svc:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
in the Kubernetes pod logs
c
ensure the pod is up and with no errors using kubectl get pods
a
k get all NAME READY STATUS RESTARTS AGE pod/airbyte-service-airbyte-bootloader 1/1 Running 0 45s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/airbyte-db-svc ClusterIP 10.43.61.102 <none> 5432/TCP 54s service/airbyte-minio-svc ClusterIP 10.43.93.114 <none> 9000/TCP 51s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/cef-kafka-connect-service 2/2 2 2 3h7m NAME DESIRED CURRENT READY AGE replicaset.apps/cef-kafka-connect-service-5b7749d76 2 2 2 3h7m NAME READY AGE statefulset.apps/airbyte-db 0/1 56s statefulset.apps/airbyte-minio 0/1 53s
I could see only airbyte-bootloaded
dont see any db pod starting
c
statefulset.apps/airbyte-db 0/1 56s that implies airbyte-db not starting
Copy code
kubectl get pods 
kubectl describe pod nameofairbyte-db-pod
a
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 24m default-scheduler 0/9 nodes are available: 9 pod has unbound immediate PersistentVolumeClaims. Warning FailedScheduling 22m (x1 over 23m) default-scheduler 0/9 nodes are available: 9 pod has unbound immediate PersistentVolumeClaims.
k get pods -l app.kubernetes.io/instance=airbyte-service NAME READY STATUS RESTARTS AGE airbyte-db-0 0/1 Pending 0 25m airbyte-minio-0 0/1 Pending 0 25m airbyte-service-airbyte-bootloader 0/1 Error 0 25m
Copy code
volumeClaimTemplates:
- metadata:
    name: airbyte-volume-db
  spec:
    accessModes: [ "ReadWriteOnce" ]
    resources:
      requests:
        storage: {{ .Values.postgresql.storage.volumeClaimValue }}
Looks like this is mandatory and our environment doesnt have this Persistent volume.. can’t we create this airbyte service with out this ?
Open in Slack
PreviousNext
Powered by