## What
<!--
* Describe what the change is solving. Link all GitHub issues related to
this change.
-->
This pull request updates plan names across most of the Documentation so
they're consistent with our current plan names.
## How
<!--
* Describe how code changes achieve the solution.
-->
My original plan was to convert free text to MDX variables so we only
had to make future updates to names in one place. While broadly
successful, there were numerous edge cases that made rolling this out
almost impossible. There were too many ways and places you couldn't use
variables due to a variety of limitations in Docusaurus and Airbyte's
internal MarkDown processor. Explaining how to properly use them made me
realize how prohibitively insufficient this was. In the end, I opted to
return to using free text for plan names.
Scope is now broadly reduced. This PR:
- Converts remaining instances of old plan names to new plan names. In
most cases, I replaced old plan names with new plan names directly. In
some cases, sentences were rewritten to make a bit more sense or be more
maintainable in the future.
- Removes previously added preprocessor variables from Docusaurus
configuration.
- Update Vale styles or various artifacts of content based on linter
findings.
## Review guide
<!--
1. `x.py`
2. `y.py`
-->
Spot check updated pages to ensure plan names appear appropriately. It's
probably not necessary to check every single instance in detail.
For Platform docs, changes only apply to the Next/Cloud version. After
merging, I'll regenerate 2.0 docs based on this. 1.8 and before won't be
updated.
## User Impact
<!--
* What is the end result perceived by the user?
* If there are negative side effects, please list them.
-->
People can see correct plan names in docs content.
## Can this PR be safely reverted and rolled back?
<!--
* If unsure, leave it blank.
-->
- [x] YES 💚
- [ ] NO ❌
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
## 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>
