Skip to content

docs: add a section on resource usage and running over http to the quickstart. #44190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 16, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 14 additions & 13 deletions docs/using-airbyte/getting-started/oss-quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -294,24 +294,25 @@ Ensure the security group configured for the EC2 Instance allows traffic in on t
abctl local install --host [HOSTNAME]
```

### Editing the Ingress
### Suggested Resources

:::note
The latest versions of `abctl` support a `--host` flag replacing the need to manually modify the ingress rules.
For the best performance, we suggest you run on a machine with 4 or more CPU's and at least 8 GB of memory. Currently
`abctl` does support running on 2 cpus and 8 gb of ram with the `--low-resource-mode` flag. You can pass the low
resource mode flag when install Airbyte with `abctl`:

For example, if you are hosting Airbyte on the FDQN of `airbyte.company.example`, you would execute the following command:
`abctl local install --host airbyte.company.example`
:::
```shell
abctl local install --low-resource-mode
```

By default `abctl` will install and Nginx Ingress and set the host name to `localhost`. You will need to edit this to
match the host name that you have deployed Airbyte to. To do this you will need to have the `kubectl` command installed
on your EC2 Instance and available on your path.
### Running over HTTP

If you do not already have the CLI tool kubectl installed, please [follow these instructions to install](https://kubernetes.io/docs/tasks/tools/).
Airbyte suggest that you secure your instance of Airbyte using TLS. Running over plain HTTP allows attackers to see your
password over clear text. If you understand the risk and would still like to run Airbyte over HTTP, you must set
Secure Cookies to false. You can do this with `abctl` by passing the `--insecure-cookies` flag to `abctl`:

Then you can run `kubectl edit ingress -n airbyte-abctl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig` and edit the `host`
key under the spec.rules section of the Ingress definition. The host should match the FQDN name that you are trying to
host Airbyte at, for example: `airbyte.company.example`.
```shell
abctl local install --host [HOSTNAME] --insecure-cookies
```

## Uninstalling

Expand Down
Loading