Summary
Best practices for implementing a user login system in Airbyte Community Edition on Kubernetes to restrict access within an organization without relying on IP addresses.
Question
Hi there! I’d like to add Airbyte Community Edition on Kubernetes to our tech stack. My problem is Airbyte Community Edition doesn’t come with a user login system. This would mean everyone in our organization would have access to the system potentially. What is a best practice to add a login system? I can’t block IP addresses since every user in our “office network” will get a random ip within a specific range. Any ideas??
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.