Install and configure a self-hosted Primary Site.
To deploy your Primary Site, you will first need an account with one of the supported cloud providers (AWS, Azure, GCP).
You will need to provision storage buckets, a Kubernetes cluster, and cloud credentials before installing the Primary Site.
Foxglove provides a set of Terraform examples to help with these initial provisioning steps.
Create storage buckets
Create two storage buckets for your Primary Site:
inbox– For all file uploads
lake– For processed and indexed versions of all files added to
Create Kubernetes cluster
Create a Kubernetes cluster to run your site workloads (e.g. processing inbox data, servicing data access requests from the lake) – we recommend doing this in the same region as your storage buckets, to reduce access latency and cost.
foxglove namespace in your cluster:
$ kubectl create namespace foxglove
Configure cloud credentials
Create a service account with read and write access to the storage buckets. The Kubernetes workloads will use this service account.
See Configure cloud credentials for details on how to provide this credential to the deployment.
Create secret with site token
Find your Primary Site token on the "Sites" settings page.
Install a Secret named
foxglove-site-token into the
foxglove namespace containing your site token:
$ kubectl create secret generic foxglove-site-token --from-literal=FOXGLOVE_SITE_TOKEN='fox_sk_...' --namespace foxglove
There are multiple other ways to create secrets that may be preferable. See Create a Secret for more info.
Install the release
Install your Primary Site using Helm.
Prepare a values file
values.yaml file to configure the installation. You'll need to include a
google_cloud) and the names of your
Be sure to include any additional values required by your storage provider:
- AWS – Configure a region for requests:
- Azure - Configure your storage service:
Helm will install the Primary Site deployment to your current Kubernetes context.
$ helm repo add foxglove https://helm-charts.foxglove.dev
$ helm repo update
$ helm upgrade --install foxglove-primary-site foxglove/primary-site \
--values ./values.yaml \
--namespace foxglove \
View info about the deployment:
$ helm list -n foxglove
Ingress for data access
The deployment installs an Ingress which exposes a REST API endpoint for accessing available data.
To reach the ingress from outside the cluster you'll need to assign a DNS name and HTTPS endpoint. This HTTP endpoint must be reachable from your organization's network or any network you want to have access to the site data.
How to assign a DNS name and HTTPS endpoint to the ingress is specific to your organization and cloud environment.
You can configure the ingress using your values file. Below are the default values.
To completely disable the Ingress, set
ingress.enabled to false. However, you must provide an Ingress for the site to function.
Some cloud providers require configuring annotations for HTTPS certificates. Here's an example values file for AWS.
Once the site's ingress public URL is known, you can configure it on a Site page, linked from the "Sites" settings page.
Under Site URL, enter the HTTPS URL you've assigned to the Ingress.
Bucket push notification
The site inbox processor needs to know when new files are uploaded to the inbox bucket. To notify of new uploads, configure a push notification to the foxglove data platform inbox-notifications endpoint.
Configuring a push notification for new file uploads is specific to your cloud provider.
The Foxglove AWS Terraform examples, configure these resources for you. For manual setup, or for more information, see the cloud provider documentation below.
- Azure: https://learn.microsoft.com/en-us/azure/event-grid/blob-event-quickstart-portal#create-a-message-endpoint
- GCP: https://cloud.google.com/storage/docs/pubsub-notifications
- AWS: If you are using the Foxglove AWS Terraform example, this setup is done for you. You should see an SNS topic with an https subscription attached to the inbox bucket's
Org admins can find the inbox notification endpoint on the Sites settings page.