-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
self-managed docs rewrite #32605
self-managed docs rewrite #32605
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
342a16a
to
7e920bd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With some recommendations to address a few inconsistencies.
|
||
# Implementation Guide | ||
|
||
[Airbyte Self Managed](./README.md) is in an early access stage for select priority users. Once you [are qualified for an Airbyte Self Managed license key](https://airbyte.com/company/talk-to-sales), you can deploy Airbyte with the following instructions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing -
in Self-Managed
</Tabs> | ||
</details> | ||
|
||
## Deploy Airbyte Self Managed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing -
in Self-Managed
After specifying your own configuration, run the following command: | ||
|
||
```text | ||
./tools/bin/install_airbyte_pro_on_helm.sh --values path/to/values.yaml %release_name% airbyte/airbyte |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this was in the previous docs as well, but using %
here is incorrect. We should have $RELEASE_NAME
or simply leave it out.
Airbyte Enterprise supports Single Sign-On, allowing an organization to manage user access to their Airbyte Enterprise instance through the configuration of an Identity Provider (IdP). Airbyte Enterprise currently supports SSO via OIDC with [Okta](https://www.okta.com/) as an IdP. | ||
The following instructions walk you through: | ||
1. [Setting up the Okta OIDC App Integration to be used by your Airbyte instance](#setting-up-okta-for-sso) | ||
2. [Configuring Airbyte Self Managed to use SSO](#deploying-airbyte-enterprise-with-okta) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing -
in Self-Managed
|
||
_Example values_ | ||
|
||
`<your-airbyte-domain>` should point to where your Airbyte instance will be available, including the http/https protocol. | ||
|
||
|
||
## Deploying Airbyte Enterprise with Okta |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems we may be inconsistent with Airbyte Self-Managed
vs Airbyte Enterprise
. Do we use both names or should we pick one?
Changes: