for the airbyte self deployment does it use

airbyte/source-declarative-manifest

and how is this image address updated?

Yes, Airbyte self-deployment does use the

airbyte/source-declarative-manifest

image for certain connectors. This image is particularly important for manifest-only connectors in Airbyte. According to the documentation, manifest-only connectors must use

airbyte/source-declarative-manifest

as their base image [Documentation > Contributing-to-airbyte > Resources > Airbyte connectors QA checks](https://docs.airbyte.com/contributing-to-airbyte/resources/qa-checks#manifest-only-connectors-must-use-source-declarative-manifest-as-their-base-image). As for how this image address is updated, Airbyte has a process in place to periodically check for and update to the latest versions of the

airbyte/source-declarative-manifest

image. This is evident from the logs of the Airbyte cron job, which shows:

INFO i.a.c.j.DeclarativeSourcesUpdater(updateDefinitions):44 - Getting latest CDK versions and updating declarative sources... INFO i.a.c.i.RemoteDeclarativeManifestImageVersionsProvider(getTagsAndShasForRepository):52 - Fetching image tags and SHAs for airbyte/source-declarative-manifest... INFO i.a.c.i.RemoteDeclarativeManifestImageVersionsProvider(getLatestDeclarativeManifestImageVersions):40 - Latest versions for airbyte/source-declarative-manifest: [5.4.0, 4.6.2, 3.13.0, 2.1.0, 1.7.0, 0.90.0]

[Github Issue (closed): [abctl] Failing to install Helm chart > Comments Part 8](https://github.com/airbytehq/airbyte/issues/44928) This process runs regularly to ensure that the declarative sources are using the most up-to-date versions of the

airbyte/source-declarative-manifest

image. It's worth noting that individual connectors may also receive updates to use newer versions of this image. For example, in the changelogs of various connectors, we can see entries like "Bump source-declarative-manifest version" [Documentation > Integrations > Sources > Opsgenie > Changelog Part 1](https://docs.airbyte.com/integrations/sources/opsgenie#changelog), indicating that the version of

airbyte/source-declarative-manifest

used by that connector has been updated.

@kapa.ai the airbyte/source-declarative-manifest image is used in all connector builder customer connectors correct?

Yes, that's correct. The

airbyte/source-declarative-manifest

image is used as the base image for manifest-only connectors created with the Connector Builder in Airbyte. This is explicitly stated in the Airbyte documentation [QA checks for Airbyte connectors](https://docs.airbyte.com/contributing-to-airbyte/resources/qa-checks#manifest-only-connectors-must-use-source-declarative-manifest-as-their-base-image): > Manifest-only connectors must use

airbyte/source-declarative-manifest

as their base image. This image contains the necessary components to run declarative connectors, which are defined by a manifest file (usually in YAML format) that specifies the connector's behavior without requiring custom code. The

airbyte/source-declarative-manifest

image is regularly updated with new versions of the Airbyte CDK (Connector Development Kit), as evidenced by the logs showing version checks and updates [in this GitHub issue comment](https://github.com/airbytehq/airbyte/issues/44928):

INFO i.a.c.i.RemoteDeclarativeManifestImageVersionsProvider(getLatestDeclarativeManifestImageVersions):40 - Latest versions for airbyte/source-declarative-manifest: [5.4.0, 4.6.2, 3.13.0, 2.1.0, 1.7.0, 0.90.0]

This ensures that connectors built with the Connector Builder can leverage the latest features and improvements in the Airbyte CDK.

@kapa.ai is there a

connectorBuildOptions

config or something similar for the helm chart values.yaml

A message from kapa.ai

Based on the provided knowledge sources, there is no explicit mention of a

connectorBuildOptions

configuration for the Helm chart

values.yaml

file in Airbyte. The

values.yaml

file is used to customize your Airbyte deployment on Kubernetes. It typically includes configurations for global settings, service accounts, and specific Airbyte components, among other things. You can find more details about this in the [Airbyte documentation](https://docs.airbyte.com/enterprise-setup/implementation-guide#customizing-your-deployment) and [this GitHub issue](https://github.com/airbytehq/airbyte/issues/21692). However, it's important to note that the

values.yaml

file can be extended with additional configurations as needed, provided they are supported by the Airbyte Helm chart and the underlying Kubernetes resources. If

connectorBuildOptions

is a valid configuration for the Airbyte Helm chart or the Kubernetes resources it manages, you should be able to add it to your

values.yaml

file. For the most accurate and up-to-date information, I recommend checking the [official Airbyte Helm chart repository](https://github.com/airbytehq/airbyte/tree/master/charts/airbyte) or reaching out to the Airbyte community for assistance.