From 75fb8a0272b281982ea172f1d80e41bee7394a8d Mon Sep 17 00:00:00 2001
From: Viktor Barzin <viktorbarzin@meta.com>
Date: Sat, 7 Feb 2026 13:41:41 +0000
Subject: [PATCH] [ci skip] update claude knowledge: always run terraform
 locally

---
 .claude/CLAUDE.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md
index 9a6f49dc..c2156e28 100755
--- a/.claude/CLAUDE.md
+++ b/.claude/CLAUDE.md
@@ -10,14 +10,14 @@
 - **CRITICAL: All infrastructure changes must go through Terraform**. NEVER modify cluster resources directly (e.g., via kubectl apply/edit/patch, helm install, docker run). Always make changes in the Terraform `.tf` files and apply with `terraform apply`.
 
 ## Execution Environment
-
-### Local Commands (macOS)
 - **File operations**: Read, Edit, Write, Glob, Grep tools
 - **Git commands**: git status, git log, git diff, git add, git commit, git reset, etc.
-- **Basic shell**: ls, cat, head, tail, find, grep, etc.
-
-### Remote Commands
-For commands that need cluster access (terraform, kubectl, helm, docker, python), run them directly. These tools are available in the local environment.
+- **Shell commands**: All tools (terraform, kubectl, helm, python, etc.) are available locally
+- **CRITICAL: Always run terraform locally**, never on the remote server via SSH. Use `-var="kube_config_path=$(pwd)/config"` when applying:
+  ```bash
+  terraform apply -target=module.kubernetes_cluster.module.<service> -var="kube_config_path=$(pwd)/config" -auto-approve
+  ```
+- **kubectl**: Use `kubectl --kubeconfig $(pwd)/config` for cluster access
 
 ---