docs(abctl): expand docs with troubleshooting, flag reference, and scope limitations#74094
docs(abctl): expand docs with troubleshooting, flag reference, and scope limitations#74094Ian Alton (ian-at-airbyte) wants to merge 2 commits intomasterfrom
Conversation
…ope limitations - Add installer script troubleshooting section (Is a directory error, permission denied) - Document installer env vars (DIR_INSTALL, RELEASE_TAG, DEBUG) - Add customize install location subsection with DIR_INSTALL example - Expand --chart and --chart-version flag descriptions with usage examples - Add explicit scope limitation: abctl only manages its own kind cluster - Add FAQ entry about existing Kubernetes cluster support Co-Authored-By: ian.alton@airbyte.io <ian.alton@airbyte.io>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit d23cc50. |
| You use abctl to run Airbyte on a machine that isn't running a Kubernetes cluster, but is running Docker. Normally, you don't use abctl to manage enterprise deployments, because they use dedicated Kubernetes infrastructure. However, it's possible to use abctl this way if you want to. | ||
|
|
||
| :::warning | ||
| abctl only manages its own kind cluster. It cannot install Airbyte on an existing Kubernetes cluster. If you already have a Kubernetes cluster, use the [Helm chart deployment guide](../chart-v2-community.mdx) instead. | ||
| ::: | ||
|
|
There was a problem hiding this comment.
Let's combine these ideas into one. No need for a warning.
"You use abctl to run Airbyte on a machine that isn't running a Kubernetes cluster, but is running Docker. abctl only manages its own kind cluster. It can't install Airbyte on an existing Kubernetes cluster. If you already have a Kubernetes cluster, use the Helm chart deployment guide instead."
There was a problem hiding this comment.
Done — merged the scope limitation into the paragraph and removed the :::warning box, as suggested.
| | `DEBUG` | unset | Set to any value to enable verbose installer output. | | ||
|
|
||
| :::note | ||
| `DIR_INSTALL` controls only where the **abctl binary** lives. Airbyte state data (kubeconfig, cluster data) is stored separately at `~/.airbyte/abctl/` and is not affected by this setting. There is currently no flag to relocate the data directory. |
There was a problem hiding this comment.
| `DIR_INSTALL` controls only where the **abctl binary** lives. Airbyte state data (kubeconfig, cluster data) is stored separately at `~/.airbyte/abctl/` and is not affected by this setting. There is currently no flag to relocate the data directory. | |
| `DIR_INSTALL` controls only where the **abctl binary** lives. Airbyte state data (kubeconfig, cluster data) is stored separately at `~/.airbyte/abctl/. It's not affected by this setting and you can't relocate it. |
There was a problem hiding this comment.
| abctl local install --chart-version 0.422.2 --values values.yaml --secret secret.yaml --port 8000 | ||
| ``` | ||
| The `--chart-version` value is the Helm chart version, not the Airbyte platform version. To find available versions, see the [Airbyte Helm chart releases](https://github.com/airbytehq/airbyte-platform/releases). |
There was a problem hiding this comment.
I don't think this URL shows helm chart versions. Do we not have a centralized list of them?
There was a problem hiding this comment.
Good catch — that URL shows platform releases, not Helm chart versions. Updated to link to the ArtifactHub page which has the full list of chart versions: https://artifacthub.io/packages/helm/airbyte/airbyte
…art versions URL, update wording Co-Authored-By: ian.alton@airbyte.io <ian.alton@airbyte.io>
What
Addresses gaps in abctl documentation identified through Kapa.ai chatbot conversations where users could not find answers to common questions:
Is a directoryerror)--chartand--chart-versionflagsHow
docs/platform/deploying-airbyte/abctl/index.md:DIR_INSTALL,RELEASE_TAG, andDEBUGenv vars from the installer script--chartand--chart-versiondescriptions in the reference table with fuller explanations and a link to ArtifactHub for finding chart versionsdocs/platform/deploying-airbyte/troubleshoot-deploy.md:abctl local installruntime errors, not the installer script itself)DIR_INSTALLworkaroundReview guide
docs/platform/deploying-airbyte/abctl/index.md— scope limitation (inline in paragraph), install customization section, chart version examples, expanded flag descriptionsdocs/platform/deploying-airbyte/troubleshoot-deploy.md— new installer errors section and existing-cluster FAQHuman review checklist:
--chart-versionis ignored when--chartis set (inferred from abctl README and typical Helm behavior — worth confirming against the Go source)DIR_INSTALL,RELEASE_TAG,DEBUG) still match the currentabctl_install.shUser Impact
Users and the Kapa.ai chatbot will have documentation to answer four previously unanswerable question categories. No runtime changes.
Can this PR be safely reverted and rolled back?
Link to Devin run: https://app.devin.ai/sessions/5c0047049398462797605f1fd644996d
Requested by: Ian Alton (@ian-at-airbyte)