Airbyte on AWS EKS installed via helm chart. I'm a...
# replication-ask-ai
r
Airbyte on AWS EKS installed via helm chart. I'm a n00b with Kubernetes. Is there an example of what to put into
values.yaml
in the
ingress
section to trigger the AWS ALB controller (already installed in the EKS cluster)?
k
A message from kapa.ai
Hmm, I don't know enough to give you a confident answer yet. The information extracts provided do not contain specific details on how to configure the
ingress
section of the
values.yaml
file for triggering the AWS ALB controller in an EKS cluster. However, you can refer to the
values.yaml
example located in the [charts/airbyte](https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/values.yaml) folder of the Airbyte repository for general configuration. For more specific details on configuring ingress with AWS ALB, you might want to refer to the AWS ALB Ingress Controller documentation or the Kubernetes Ingress documentation. For more information on deploying Airbyte on Kubernetes using Helm, you can refer to the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm).
h
Copy code
annotations:
   <http://kubernetes.io/ingress.global-static-ip-name|kubernetes.io/ingress.global-static-ip-name>: YOUR_STATIC_IP_NAME
   <http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: YOUR_INGRESS_CLASS
   <http://networking.gke.io/managed-certificates|networking.gke.io/managed-certificates>: CERTIFICATE_IF_YOU_HAVE
for instance: in my case ingress class is gce since we are on GCP
this should networking.gke.io/managed-certificates have an EKS equivalent
r
thank you for the info I will try that
s
If you haven't gotten this, I can send you something. Though I've found another problem right after :(.
r
We changed tack and are running airbyte on Docker on EC2; no need for a whole dedicated Kubernetes cluster for it and we don't have a "one big cluster for all containerized applications" type model