Deploying Airbyte on EKS via ArgoCD with values.yaml not respected

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

When deploying Airbyte on EKS via ArgoCD, adjustments in values.yaml file for resources.limits and resources.requests are not respected in the configuration, affecting monitoring. Is it possible to modify Airbyte components using this file?


Question

Hey, got a question about deploying Airbyte on EKS (Kubernetes) via ArgoCD. It seems that no matter how we adjust values.yaml file - it doesn’t seem to be respected, like any of the *.resources.limits or *.resources.requests - they’re just blank inside the ArgoCD configuration, and this can be seen from monitoring side too. Is it possible to actually use this file and modify any of the Airbyte components?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["deploying-airbyte", "eks", "argocd", "values.yaml", "resources-limits", "resources-requests", "monitoring", "modify-components"]