<@U01RW78A2LE> Thanks for the talk the other day. ...
# kubernetes
s
@abhi Thanks for the talk the other day. I have been using plural for months now and i’m a fan Question - Is the airbyte API publicly accessible when deployed via Plural? I see there is an additional subdomain setup within the
context.yaml
. If I setup my instance at
airbyte.my-org.onplural.sh
, and setup the api at
airbyte-api.my-org.onplural.sh
How do I interact with API? I tried to replicate the network calls that I see in Chrome dev tools (~~`api/v1/worspace-id/get-destinations` ) with postman. I keep getting redirects to the ‘sign in with plural’ page i assume I need to use the other api-specific hostname? and how do i handle authentication - service token from app.plural.com or something else?
If somebody can help me start using the Airbyte API (better yet, Octavia) via plural, I will write up a guide and make a pull request to the plural docs.
a
There's two ways you can do this! 1. Configure basic auth with the public endpoint manually, then just use your username/password you configured 2. Plural has two ingress controllers, a private and a public one. If you use the private network, you can hit the endpoint directly!
@Sawyer Waugh that would be amazing if you made a PR to our docs, we should absolutely document setting up basic auth or accessing via private ingress
s
@abhi thanks for the response. questions 1. for the public, this is the same username/password that I use to login to app.plural.sh? It’s http basic auth and not oauth2 (client credentials etc) 2. For direct access via the private ingress endpoint, can you give some more detail? a. am I using an access token created at
<https://app.plural.sh/me/edit/tokens>
or something else? b. What type of Authentication ? c. Does this token get attached as a header, query param or in the body?
an example (as curl or an OpenAPI example or whatever) would be a huge help. I will take that and adapt the airbyte api docs and include those in a guide
a
I’m gonna cc @Michael Guarino to let him respond here to make sure we can cover everything!
m
for basic auth, it can be any username, password pair. We use
api
as the username to make it explicit that it's used for the api, and you can generate a random password with
plural crypto random
. To actually set these add a users key in your context.yaml file like:
Copy code
users:
  <uname>: <password>
then run
plural build --only airbyte && plural deploy --commit "adding airbyte basic auth"
You might need to also delete the airbyte webserver pods to make it take effect, the rotation isn't always automatic for airbyte
s
Thank you @Michael Guarino. will try this out today.