Helm Deployment

Deploy the Yuki Proxy to your Kubernetes cluster using Helm. The proxy can be deployed in your data workload's VPC or in a separate VPC.

Steps

1. Add the Helm Repository

helm repo add proxy https://yukitechnologies.github.io/yuki-proxy-chart
helm repo update

2. Create the Configuration File

Create a yuki-values.yaml file with the required parameters:

app:
  container:
    env:
      REDIS_HOST: <REDIS_HOST>
      PROXY_HOST: <PROXY_HOST>
      COMPANY_GUID: <COMPANY_GUID>
      ORG_GUID: <ORG_GUID>
      ACCOUNT_GUID: <ACCOUNT_GUID>

hpa:
  enabled: true
  minReplicas: 5
  maxReplicas: 15
  targetCPUUtilizationPercentage: 40
  targetMemoryUtilizationPercentage: 40

affinity: {}
tolerations: []

Parameter	Description
`REDIS_HOST`	Redis/ElastiCache endpoint
`PROXY_HOST`	Yuki endpoint generated during onboarding
`COMPANY_GUID`	Your company identifier from onboarding
`ORG_GUID`	Your organization identifier from onboarding
`ACCOUNT_GUID`	Your account identifier from onboarding

3. Deploy

helm install yuki-proxy yuki/proxy -f yuki-values.yaml

Verify the deployment:

kubectl get pods -l app=yuki-proxy

4. Configure DNS (Route 53)

Retrieve the Load Balancer DNS from the EC2 console
Create a Route 53 record: snowflake-locator.your-domain.com
- Use an A (Alias) record for ALB/NLB
- Use a CNAME record for ELB

Next Step

Proceed to Update Connection Strings to route your tools through the proxy.

Steps​

1. Add the Helm Repository​

2. Create the Configuration File​

3. Deploy​

4. Configure DNS (Route 53)​

Next Step​