Privacy Dynamics Self-hosted
Kubernetes Cluster
Deploy a Kubernetes cluster
We recommend that you follow your cloud provider's Kubernetes cluster creation guide. Privacy Dynamics supports Kubernetes versions 1.24, 1.25, 1.26, and 1.27.
Tip
Our installation guides assume Privacy Dynamics will be running in a dedicated cluster.
Tip
A connection to the public Internet from the cluster is required. Communication with Auth0, the Identity Provider (IdP) used to handle authentication, is necessary to use Privacy Dynamics.
We recommend the cluster specifications below.
AWS installation
Node Requirements
Depending on the size of your data you may need to provision instances with more vCPUs and RAM. This is a minimum requirement.
- An EKS cluster with a Node Group containing at least two
t3.2xlarge
EC2 instances. Each EC2 instance should have 8 vCPUs and 32 GB RAM. - 100 GB of storage is sufficient.
Create an IAM OIDC identity provider
We recommend using AWS IAM Roles for Service Accounts (IRSA) to allow service accounts on your cluster to perform actions in AWS. To do so, an IAM OpenID Connect (OIDC) provider must exist for your cluster. Create an IAM OIDC identity provider for your cluster with the command below.
$ eksctl utils associate-iam-oidc-provider \
--region=AWS_REGION --cluster=CLUSTER_NAME \
--approve
Tip
Replace CLUSTER_NAME
with your cluster's name, AWS_REGION
with the region like us-west-2
.
EKS Add-ons
- We recommend installing EKS add-ons where possible (see general instructions for managing EKS add-ons), including the following