Learn how to self-host Trieve on Azure
Things you need
Azure should be configured with your IAM credentials chosen. Run the following commands to create the AKS cluster
Set up your kubeconfig to point to the new cluster
Ingress-nginx + Cert manager is how we will expose the trieve services to the internet. Feel free to use whatever ingress controller you are comfortable with.
For full configuration options, the values.yaml contains comments and examples. More information can be found in the Trieve Helm Chart repository.
Install the helm chart. Ensure it is installed twice
You will need to install the helm chart twice to ensure the crds are installed and ConfigMap’s are updated properly.
After installing, kubectl get deployments
should look like this.
You will get an output like this:
Add A records to your domain registrar with the IP address of the ingress.
Ensure you run helm upgrade -i -f values.yaml trieve-local trieve/trieve
after making changes. to apply them.
Follow these steps to confirm your Trieve instance is working correctly:
Register Your First User
Navigate to dashboard.yourdomain.com
in your browser. You’ll be prompted to register a new user account since this is a fresh installation.
Create a Dataset and Add Sample Data
Once logged in, create your first dataset and populate it with some example data. This will help you test the core functionality of your Trieve instance.
Verify Data Processing
Check the admin event log to ensure that chunks are being created successfully from your uploaded data. This confirms that the ingestion pipeline is working properly.
Test Search Functionality
Navigate to search.yourdomain.com
and perform a test search query using the data you just uploaded. This verifies that the search engine is functioning correctly.
Review Search Analytics
Return to dashboard.yourdomain.com
and examine your search analytics to confirm that queries are being tracked and analyzed properly.
You now have a fully functional Trieve instance running on Azure. Your self-hosted search infrastructure is ready to handle production workloads. Want to find out what’s next?
Learn how to self-host Trieve on Azure
Things you need
Azure should be configured with your IAM credentials chosen. Run the following commands to create the AKS cluster
Set up your kubeconfig to point to the new cluster
Ingress-nginx + Cert manager is how we will expose the trieve services to the internet. Feel free to use whatever ingress controller you are comfortable with.
For full configuration options, the values.yaml contains comments and examples. More information can be found in the Trieve Helm Chart repository.
Install the helm chart. Ensure it is installed twice
You will need to install the helm chart twice to ensure the crds are installed and ConfigMap’s are updated properly.
After installing, kubectl get deployments
should look like this.
You will get an output like this:
Add A records to your domain registrar with the IP address of the ingress.
Ensure you run helm upgrade -i -f values.yaml trieve-local trieve/trieve
after making changes. to apply them.
Follow these steps to confirm your Trieve instance is working correctly:
Register Your First User
Navigate to dashboard.yourdomain.com
in your browser. You’ll be prompted to register a new user account since this is a fresh installation.
Create a Dataset and Add Sample Data
Once logged in, create your first dataset and populate it with some example data. This will help you test the core functionality of your Trieve instance.
Verify Data Processing
Check the admin event log to ensure that chunks are being created successfully from your uploaded data. This confirms that the ingestion pipeline is working properly.
Test Search Functionality
Navigate to search.yourdomain.com
and perform a test search query using the data you just uploaded. This verifies that the search engine is functioning correctly.
Review Search Analytics
Return to dashboard.yourdomain.com
and examine your search analytics to confirm that queries are being tracked and analyzed properly.
You now have a fully functional Trieve instance running on Azure. Your self-hosted search infrastructure is ready to handle production workloads. Want to find out what’s next?