## What
Updates Airbyte's ingress documentation to acknowledge that ingress
support exists in both Helm chart V1 and V2, while maintaining focus on
the recommended V2 approach. This addresses the discovery that PR #17752
added unified ingress support to Helm V1 charts, making previous "V2
only" statements inaccurate.
Related to on-call issue #9393 and feature PRs #17787 (V2 ingress) and
#17752 (V1 ingress).
## How
- **Removed "V2 only" language** from ingress documentation sections
- **Added notes for V1 users** directing them to the [values.yaml
reference](/platform/deploying-airbyte/values) page for V1-specific
ingress configuration structure
- **Maintained V2 as primary focus** with comprehensive configuration
examples and guidance
- **Updated helm chart comparison table** to show ingress availability
in both versions
- **Restructured documentation** to clearly separate "Helm chart
ingress" vs "manual ingress" options
- **Combined and simplified examples** to focus on required backend
services (server + connector-builder-server)
## Review guide
1. **docs/platform/deploying-airbyte/integrations/ingress.md** - Main
ingress documentation restructuring
- Verify the V1 note and values.yaml link accuracy
- Check that V2 examples are technically correct (backend field usage)
- Ensure the two-option structure (Helm chart vs manual) is clear
2. **docs/platform/enterprise-setup/implementation-guide.md** -
Enterprise ingress documentation
- Verify enterprise-specific configuration (keycloak backend)
- Check V1 reference note consistency with main docs
- Ensure switching instructions are clear
3. **docusaurus/static/_helm-chart-2-syntax-changes.md** - Helm
comparison table update
- Verify ingress entry accurately represents V1 vs V2 differences
- Check link to ingress documentation works
## User Impact
- **Helm V1 users** now have clear guidance that ingress is available
(previously told it was V2-only)
- **Helm V2 users** get improved, comprehensive ingress configuration
guidance
- **All users** benefit from clearer separation between Helm-managed vs
manual ingress approaches
- **Documentation accuracy** improved to reflect actual product
capabilities
## Can this PR be safely reverted and rolled back?
- [x] YES 💚
This is documentation-only changes with no code modifications. Revert
would restore previous "V2 only" statements but wouldn't break
functionality.
---
**Link to Devin run**:
https://app.devin.ai/sessions/5f4a71d6776d486aa4ec93eec89bd643
**Requested by**: ian.alton@airbyte.io
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: ian.alton@airbyte.io <ian.alton@airbyte.io>
## What
Removes the redundant static `llms.txt` file from the Docusaurus static
directory. This file is no longer needed because the
`@signalwire/docusaurus-plugin-llms-txt` plugin automatically generates
the same content during the build process.
Requested by Ian Alton (ian.alton@airbyte.io) via Slack.
Link to Devin run:
https://app.devin.ai/sessions/7bfbeb068874484ca7987f541a0b89eb
## How
- Deleted `docusaurus/static/llms.txt` (100 lines of documentation
links)
- The `@signalwire/docusaurus-plugin-llms-txt` plugin configured in
`docusaurus.config.js` generates equivalent content at build time
## Review guide
1. Verify that `@signalwire/docusaurus-plugin-llms-txt` plugin is
properly configured in `docusaurus/docusaurus.config.js` (lines 207-218)
2. Confirm that the build process successfully generates
`build/llms.txt` during documentation builds
3. Check that no external systems or links specifically reference
`/static/llms.txt` path
## User Impact
- No user-facing impact - the `llms.txt` file will still be available at
the same URL path after build
- Content will now be automatically generated based on the actual
documentation structure rather than manually maintained
- Reduces maintenance burden by eliminating duplicate/redundant file
## Can this PR be safely reverted and rolled back?
- [x] YES 💚
This change only removes a redundant file. If the plugin fails to work
as expected, the static file can be easily restored from git history.
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: ian.alton@airbyte.io <ian.alton@airbyte.io>
