Docs for custom image registries

[ian-at-airbyte]

What

Deployment docs for custom image registries.

How

Adds a new topic to the OSS deployment guide, and a new section to the enterprise deployment guide. These sections are mostly the same, and provide guidance on how to modify your values.yaml file and push images to your registry.

Review guide

1. https://airbyte-docs-git-10298-docs-private-regis-ac8abb-airbyte-growth.vercel.app/deploying-airbyte/integrations/custom-image-registries (whole page)
2. https://airbyte-docs-git-10298-docs-private-regis-ac8abb-airbyte-growth.vercel.app/enterprise-setup/implementation-guide#configure-a-custom-image-registry (just this section)

User Impact

People now have instructions to set up custom registries for their images.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 23, 2024 6:36pm

[ian-at-airbyte]

In a separate task I'm reviewing the deployment docs and may end of merging/repurposing OSS and enterprise. For now this information appears twice. It's not meant to be this way permanently.

[ian-at-airbyte]

Thanks Alex. This feedback was really good.

I mostly used the structure you proposed, but I realized I could tuck the auth portion within the first heading reasonably well, so I did that and kept the process to two main steps. Hopefully that makes sense to people.

I tested the overall flow and have the images in my GitHub account (thanks for the command you provided).

It's also possible to override specific platform images in the helm charts, such as webapp.image.registry = docker.io/foo.

I don't consider this a blocker, but I was never able to get this part to work. I'm probably doing it wrong though.

[Hesperide]

These docs are awesome. Left a couple nits, then good to merge.