Deploying Airbyte on VM through abctl with self-signed TLS Certificate #53157
Unanswered
baronvonbeck
asked this question in
Deployment
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Attempting to install a self-signed TLS certificate on a VM-hosted installation of Airbyte, as I'd prefer not to use the --insecure-cookies option. No issues running abctl, configuring basic auth, pointing to an external Postgres database, getting in and building connectors with that option enabled, etc. But trying to get a self-signed cert installed has been just about impossible. I've searched and made various attempts at combinations of the below settings for several hours:
--secret tls_secret.yaml
parameter during abctl local installabctl local install
and without host parameter in the install command, i.e.abctl local install --host "myairbyte.local"
abctl local install --values values.yaml
(see below)Example section in values.yaml:
The farthest I get is that I see a 308 permanent redirect to the custom host when curling it with http on port 8000, but if I go to it with https on either 443 or 8000 I get connection refused. Not doing anything custom with ports otherwise, and I opened up NSGs on the VM to allow everything inbound on 443 and 8000 to rule anything out.
Haven't been able to find any documentation or examples of getting a cert installed - the end of Airbyte's youtube video https://www.youtube.com/watch?v=1yBBkzJizKk hinted that they were going to release another video showing how, but I don't see it on their channel. Not able to find anything on Google that's worked either, with abctl specifically or with kubectl + nginx in general. If anyone has an example of a working configuration, or something else to try, I'd be extremely grateful.
Beta Was this translation helpful? Give feedback.
All reactions