Helm Deployment

Use this option to deploy the Yuki Proxy in an existing Kubernetes cluster using Helm. The Helm chart installs Yuki directly into your environment and connects securely to Snowflake over HTTPS.

It can run in clusters located in either the same VPC as your data workloads or in a separate VPC depending on your network setup.

💡 Note: You don’t need to run these steps manually - our onboarding wizard will walk you through each step.

Same Cluster:

Dedicated VPC:

→ For the full request/response flow and protocols, see Secure Data Flow.

---

1. Add the Yuki Helm Repository

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

---

2. Create Configuration File

Save the following content as yuki-values.yaml. This file defines the runtime configuration for your Yuki Proxy.

💡 The onboarding wizard provides these values automatically - you can copy them directly from the Helm Chart screen.

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 Reference

Parameter	Description	Example
REDIS_HOST	Redis or ElastiCache endpoint used by Yuki Proxy	redis-cluster.prod.internal:6379
PROXY_HOST	Yuki Proxy endpoint generated in onboarding	snowflake-locator.company-domain.com
COMPANY_GUID	Unique identifier for your Yuki company	7a1899e2-39c9-4ac4-9277-854f3dfc2a8e
ORG_GUID	Identifier for your Yuki organization	f1d6543a-215a-4df5-a892-6f7416e24b01
ACCOUNT_GUID	Snowflake account identifier	9crfd23e-8b2c-4fa8-96f2-1a89df4c16b7
minReplicas	Minimum number of proxy pods	5
maxReplicas	Maximum number of proxy pods	15
targetCPUUtilizationPercentage	CPU threshold for autoscaling	40
targetMemoryUtilizationPercentage	Memory threshold for autoscaling	40
ingress.enabled	Enable if proxy must be exposed externally	true

---

3. Deploy the Proxy

Run the following command to install the Proxy:

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

This command will:

• Deploy the Yuki Proxy pods in your cluster

• Create Kubernetes services for internal communication

• Start routing Snowflake metadata securely to Yuki

✅ Once deployed, you can verify the status using:

kubectl get pods -l app=yuki-proxy

---

Create a DNS Record in Route 53

After the Yuki Proxy pods are up, expose them through a DNS name that your users and Snowflake will connect to.

1. Get the Load Balancer DNS name

   • Go to EC2 → Load Balancers

   • Copy the DNS name (for example: my-lb-123456.us-east-1.elb.amazonaws.com)

2. Navigate to Route 53

   • Open the Route 53 Console

   • Go to Hosted Zones → select your domain (e.g. company-domain.com)

3. Create a Record

   • Click Create Record

   • Record name: snowflake-locator

   • Type:

     • A – Alias (for ALB/NLB)

     • CNAME (for subdomains pointing to ELB)

   • Alias Target: Select the Load Balancer or paste its DNS name

   • Click Create records

Your host address for the Yuki Proxy will be: snowflake-locator.company-domain.com

This is the connection string you’ll use later when enabling optimization for your warehouses.

That’s it - no Kubernetes, no Terraform, no infrastructure to manage.

💡 For Business Critical accounts, see AWS PrivateLink Setup to ensure all Yuki–Snowflake traffic remains private.

---

---

Next Step

Proceed to security configuration: → Configure Security