Summary
After successfully migrating to abctl method, user faced issues accessing login page remotely, unknown email requirement, and lack of migration wizard. User reverted to Docker due to perceived instability and lack of documentation.
Question
I have followed those instructions last night and while the migration succeeded, the login page is only acccessible from the localhost, but i run my server headless. So i had to run this command:
kubectl edit ingress -n airbyte-abctl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig
Then edit the hostname to my DNS name. Then after i saved, it worked.
However, now it asks for an email and password - but i dont know what the email is, i always used airbyte as the username. There is mention of a migration wizard appearing when you launch the first time, but it doesn’t show, so now i am completely stuck.
Edit: I gave up and went back to docker. Even with starting with the values.yaml override to remove login security and finding out what the email is and that i can use the password, i think the new abctl method is pre-alpha stage and not ready for production usage. The fact that i have to code up numerous yaml files just to connect to a DB on localhost, there is no documentation on how to automate stop/start of abctl with host reboots and numerous other issues, i’m going back to the docker version until this is all worked out.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.