Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Hey, question about the helm charts: in many places the `fullname` var is being used to which includes a `trunc 63`  to prevent creating anything with names that are longer than allowed by k8s, though this is not being used for service names, in this case `{{ .Release.Name }}-airbyte-connector-builder-server-svc` (which is already really long without the release name :sweat_smile:) I only really see it being used in the env-configmap and would like to know if and how we could possibly work on a solution. More context to follow in thread:

We have automated release names depending on scopes and environments we deploy to which are quite long as is, combine that with the really long name for the server builder service then reaching 64 is a piece of cake. The last thing we want to do is fork the charts so was hoping to come here for some direction. Happy to help with the implementation (to be fair could be a fairly small change) but would like to obv discuss this first as this is somewhat setting a new standard for shortening service names, a PR I don’t imagine would get too far without some discussion.

Hello jan-hendrik Hoon, it's been a while without an update from us. Are you still having problems or did you find a solution?