Hello! I'll try to answer your questions based on the information available in the extracts. 1. Airbyte does offer a form of multi-tenancy through the use of workspaces. However, in the open-source version, there is no UI for workspaces, so you need to manage them using the API. You can create a workspace through this endpoint: [https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html#post-/v1/workspaces/create](https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html#post-/v1/workspaces/create). Then you can switch to different workspaces by editing the URL, changing the workspace id that comes right after

/workspaces/

. However, it's important to note that Airbyte doesn't have any permissions structure to support a multi-tenant environment naturally. [Source](https://discuss.airbyte.io/t/2492) 2. For deploying Airbyte on Kubernetes for high availability, the extracts don't provide specific details on best practices such as replicas/affinity etc. However, it's mentioned that you can configure a Kubernetes cluster to deploy Airbyte with high availability. [Source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1667868261969919) 3. The extracts don't provide specific information on using spot instances with Airbyte. However, it's worth noting that the ability to handle interruptions and continue working without issue would depend on the specific components and workloads of your Airbyte deployment. For more detailed information and best practices, I would recommend checking out the official Airbyte documentation and community forums.