@kapa.ai avoid update-ca-trust in airbyte platform images

Based on the provided knowledge sources, there isn't specific information about avoiding

update-ca-trust

in Airbyte platform images. However, I can provide some relevant information about SSL and certificate handling in Airbyte: 1. Airbyte supports using custom CA certificates for certain connectors. For example, the Postgres source connector allows specifying a custom CA certificate file when using SSL in verify-ca mode [Github Issue #22660](https://github.com/airbytehq/airbyte/issues/22660). 2. Airbyte is working on migrating connectors to run as non-root users for security best practices [Airbyte 1.0 Release Notes](https://docs.airbyte.com/release_notes/v-1.0#announcements). This change might affect how certificates are managed within containers. 3. For custom deployments, Airbyte allows configuring a custom image registry, which could potentially be used to host modified platform images with specific certificate configurations [Implementation Guide](https://docs.airbyte.com/enterprise-setup/implementation-guide#configure-a-custom-image-registry). If you need to avoid

update-ca-trust

specifically, you might need to create custom Docker images based on the Airbyte platform images. However, the knowledge sources don't provide direct guidance on this particular issue. It's recommended to consult Airbyte's documentation or reach out to their support for more specific instructions on modifying platform images for certificate management.