{"id":39193,"date":"2026-02-16T12:41:31","date_gmt":"2026-02-16T09:41:31","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=39193"},"modified":"2026-02-16T12:41:31","modified_gmt":"2026-02-16T09:41:31","slug":"cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/","title":{"rendered":"Cloud SQL Proxy Nedir ve Neden GKE’de Kullanmal\u0131y\u0131z?"},"content":{"rendered":"

<\/p>\n

Cloud SQL Proxy Nedir ve Neden GKE’de Kullanmal\u0131y\u0131z?<\/h2>\n

Google Cloud SQL Proxy, uygulamalar\u0131n\u0131z\u0131n Google Cloud SQL veritaban\u0131 \u00f6rnekleriyle g\u00fcvenli ve \u015fifreli bir \u015fekilde ba\u011flant\u0131 kurmas\u0131n\u0131 sa\u011flayan a\u00e7\u0131k kaynakl\u0131 bir ara\u00e7t\u0131r. \u00d6zellikle Kubernetes Engine (GKE) gibi kapsay\u0131c\u0131l\u0131 ortamlarda, veritaban\u0131 ba\u011flant\u0131lar\u0131n\u0131 basitle\u015ftirmek ve g\u00fcvenli\u011fi art\u0131rmak i\u00e7in vazge\u00e7ilmez bir bile\u015fendir.<\/p>\n

Neden Cloud SQL Proxy?<\/h3>\n

* G\u00fcvenlik:<\/strong> Proxy, t\u00fcm ileti\u015fimi TLS 1.2 \u015fifrelemesi ve otomatik sertifika rotasyonu ile g\u00fcvence alt\u0131na al\u0131r. Bu, veritaban\u0131 trafi\u011finizin internet \u00fczerinden g\u00fcvenli bir \u015fekilde aktar\u0131lmas\u0131n\u0131 sa\u011flar.
\n* Kimlik Do\u011frulama:<\/strong> Cloud SQL Proxy, Cloud IAM (Identity and Access Management) kullanarak kimlik do\u011frulamas\u0131 yapar. Bu, hassas veritaban\u0131 kimlik bilgilerini (kullan\u0131c\u0131 ad\u0131\/\u015fifre) do\u011frudan uygulaman\u0131zda depolama ihtiyac\u0131n\u0131 ortadan kald\u0131r\u0131r veya en aza indirir. GKE’de Workload Identity ile entegrasyonu sayesinde, Kubernetes Service Account’lar\u0131 arac\u0131l\u0131\u011f\u0131yla IAM yetkilendirmesi yap\u0131labilir.
\n* A\u011f Yap\u0131land\u0131rmas\u0131 Kolayl\u0131\u011f\u0131:<\/strong> Cloud SQL \u00f6rne\u011finizin genel IP adresini veya \u00f6zel IP’sini do\u011frudan uygulaman\u0131za a\u00e7mak yerine, proxy yerel bir TCP portu \u00fczerinden dinler. Uygulaman\u0131z bu yerel porta ba\u011flan\u0131r ve proxy, ba\u011flant\u0131y\u0131 Cloud SQL’e g\u00fcvenli bir \u015fekilde t\u00fcneller. Bu, a\u011f g\u00fcvenlik duvar\u0131 kurallar\u0131n\u0131 basitle\u015ftirir ve sald\u0131r\u0131 y\u00fczeyini azalt\u0131r.
\n* Dinamik IP Y\u00f6netimi:<\/strong> Cloud SQL \u00f6rneklerinin IP adresleri de\u011fi\u015febilir. Proxy, bu de\u011fi\u015fiklikleri otomatik olarak y\u00f6netir, b\u00f6ylece uygulaman\u0131z\u0131n IP adresi de\u011fi\u015fikliklerinden etkilenmesini \u00f6nler.<\/p>\n

GKE’de bir uygulama \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131zda, Cloud SQL Proxy’yi uygulaman\u0131zla ayn\u0131 pod i\u00e7inde bir “sidecar” kapsay\u0131c\u0131s\u0131 olarak \u00e7al\u0131\u015ft\u0131rmak, en yayg\u0131n ve \u00f6nerilen y\u00f6ntemdir. Bu, uygulaman\u0131z\u0131n veritaban\u0131na localhost<\/code> \u00fczerinden ba\u011flanmas\u0131n\u0131 sa\u011flar, b\u00f6ylece a\u011f karma\u015f\u0131kl\u0131\u011f\u0131n\u0131 en aza indirir.<\/p>\n

\u00d6n Gereksinimler ve Haz\u0131rl\u0131k<\/h2>\n

Cloud SQL Proxy’yi GKE’de ba\u015far\u0131yla kullanmak i\u00e7in baz\u0131 \u00f6n gereksinimleri kar\u015f\u0131laman\u0131z gerekir:<\/p>\n

1. GCP Projesi ve GKE K\u00fcmesi:<\/strong> \u00c7al\u0131\u015fan bir Google Cloud projeniz ve bir GKE k\u00fcmeniz olmal\u0131d\u0131r.
\n2. Cloud SQL Veritaban\u0131 \u00d6rne\u011fi:<\/strong> Ba\u011flanmak istedi\u011finiz bir Cloud SQL veritaban\u0131 \u00f6rne\u011fi (PostgreSQL, MySQL veya SQL Server) olu\u015fturulmu\u015f olmal\u0131d\u0131r. \u00d6rnek ba\u011flant\u0131 ad\u0131 (project-id:region:instance-name<\/code>) bu rehberde \u00f6nemli olacakt\u0131r.
\n3. IAM \u0130zinleri:<\/strong> Cloud SQL Proxy’nin Cloud SQL \u00f6rne\u011fine ba\u011flanabilmesi i\u00e7in yeterli IAM izinlerine sahip bir hizmet hesab\u0131na ihtiyac\u0131 vard\u0131r. En az\u0131ndan Cloud SQL \u0130stemcisi<\/code> (Cloud SQL Client) rol\u00fc gereklidir.
\n4. Workload Identity Etkinle\u015ftirme:<\/strong> En g\u00fcvenli ve \u00f6nerilen y\u00f6ntem Workload Identity kullanmakt\u0131r. Bu sayede Kubernetes Service Account’lar\u0131n\u0131za Google Cloud IAM Service Account’lar\u0131n\u0131n kimliklerini atayabilirsiniz. GKE k\u00fcmenizde Workload Identity’nin etkinle\u015ftirildi\u011finden emin olun:<\/p>\n

gcloud container clusters update YOUR_CLUSTER_NAME \\\n        --zone YOUR_CLUSTER_ZONE \\\n        --workload-pool=YOUR_PROJECT_ID.svc.id.goog<\/code><\/pre>\n
Workload Identity Yap\u0131land\u0131rmas\u0131<\/h3>\n
Workload Identity, GKE pod’lar\u0131n\u0131z\u0131n do\u011frudan bir Google Cloud IAM Service Account’\u0131 gibi davranmas\u0131n\u0131 sa\u011flar. Bu, hassas anahtar dosyalar\u0131n\u0131 pod’larda saklama ihtiyac\u0131n\u0131 ortadan kald\u0131r\u0131r.<\/p>\n
1.  Google Cloud IAM Hizmet Hesab\u0131 Olu\u015fturma:<\/strong> Proxy’nin Cloud SQL’e ba\u011flanmas\u0131 i\u00e7in kullan\u0131lacak bir IAM Hizmet Hesab\u0131 olu\u015fturun:<\/p>\n
gcloud iam service-accounts create cloudsql-proxy-sa \\\n        --display-name \"Cloud SQL Proxy Service Account\"<\/code><\/pre>\n
2.  Gerekli \u0130zinleri Verme:<\/strong> Bu hizmet hesab\u0131na Cloud SQL \u00f6rne\u011finize ba\u011flanma izni verin (Cloud SQL \u0130stemcisi<\/code> rol\u00fc):<\/p>\n
gcloud projects add-iam-policy-binding YOUR_PROJECT_ID \\\n        --member \"serviceAccount:cloudsql-proxy-sa@YOUR_PROJECT_ID.iam.gserviceaccount.com\" \\\n        --role \"roles\/cloudsql.client\"<\/code><\/pre>\n
3.  Kubernetes Hizmet Hesab\u0131 Olu\u015fturma ve \u0130li\u015fkilendirme:<\/strong> GKE k\u00fcmenizde bir Kubernetes Service Account olu\u015fturun ve bunu az \u00f6nce olu\u015fturdu\u011funuz IAM Hizmet Hesab\u0131yla ili\u015fkilendirin. Bu ili\u015fkilendirme, Kubernetes Service Account’\u0131n\u0131n IAM Hizmet Hesab\u0131’n\u0131n kimli\u011fini \u00fcstlenmesini sa\u011flar.<\/p>\n
# k8s-service-account.yaml\n    apiVersion: v1\n    kind: ServiceAccount\n    metadata:\n      name: myapp-service-account\n      annotations:\n        iam.gke.io\/gcp-service-account: cloudsql-proxy-sa@YOUR_PROJECT_ID.iam.gserviceaccount.com<\/code><\/pre>\n
    Uygulay\u0131n: kubectl apply -f k8s-service-account.yaml<\/code><\/p>\n
    Bu Kubernetes Service Account’\u0131, daha sonra Deployment YAML dosyan\u0131zda proxy kapsay\u0131c\u0131n\u0131z i\u00e7in kullan\u0131lacakt\u0131r.<\/p>\n
GKE’de Cloud SQL Proxy Uygulamas\u0131 (Sidecar Deseni)<\/h2>\n
Cloud SQL Proxy’yi GKE’de kullanman\u0131n en yayg\u0131n ve \u00f6nerilen yolu, uygulaman\u0131zla ayn\u0131 pod i\u00e7inde bir sidecar kapsay\u0131c\u0131s\u0131 olarak da\u011f\u0131tmakt\u0131r. Bu yap\u0131land\u0131rma, uygulaman\u0131z\u0131n proxy’ye localhost<\/code> \u00fczerinden eri\u015fmesini sa\u011flar.<\/p>\n
A\u015fa\u011f\u0131daki Deployment<\/code> YAML \u00f6rne\u011fi, bir uygulaman\u0131n (\u00f6rne\u011fin bir Node.js uygulamas\u0131) Cloud SQL Proxy ile nas\u0131l da\u011f\u0131t\u0131laca\u011f\u0131n\u0131 g\u00f6stermektedir.<\/p>\n
# myapp-deployment.yaml\napiVersion: apps\/v1\nkind: Deployment\nmetadata:\n  name: myapp-deployment\n  labels:\n    app: myapp\nspec:\n  replicas: 1\n  selector:\n    matchLabels:\n      app: myapp\n  template:\n    metadata:\n      labels:\n        app: myapp\n    spec:\n      serviceAccountName: myapp-service-account # Workload Identity i\u00e7in Kubernetes Service Account\n      containers:\n      - name: myapp-container\n        image: your-app-image:latest # Kendi uygulama imaj\u0131n\u0131z\n        ports:\n        - containerPort: 8080\n        env:\n        - name: DB_HOST\n          value: \"127.0.0.1\" # Proxy'nin dinledi\u011fi yerel IP\n        - name: DB_PORT\n          value: \"5432\" # PostgreSQL i\u00e7in varsay\u0131lan, MySQL i\u00e7in 3306\n        - name: DB_USER\n          valueFrom:\n            secretKeyRef:\n              name: cloudsql-db-credentials\n              key: username\n        - name: DB_PASSWORD\n          valueFrom:\n            secretKeyRef:\n              name: cloudsql-db-credentials\n              key: password\n        # ... di\u011fer uygulama de\u011fi\u015fkenleri\n      - name: cloudsql-proxy\n        image: gcr.io\/cloudsql-docker\/gce-proxy:1.33.0 # En son s\u00fcr\u00fcm\u00fc kullan\u0131n\n        command:\n        - \"\/cloud_sql_proxy\"\n        - \"-instances=YOUR_PROJECT_ID:YOUR_REGION:YOUR_INSTANCE_NAME=tcp:5432\" # Cloud SQL ba\u011flant\u0131 ad\u0131 ve yerel port\n        # E\u011fer birden fazla instance'a ba\u011flan\u0131lacaksa:\n        # - \"-instances=instance1_conn_name=tcp:5432,instance2_conn_name=tcp:3306\"\n        - \"-enable_iam_login\" # IAM tabanl\u0131 kimlik do\u011frulama i\u00e7in (\u00f6nerilir)\n        # - \"-ip_address_type=PRIVATE\" # \u00d6zel IP kullan\u0131yorsan\u0131z\n        securityContext:\n          runAsNonRoot: true\n        resources:\n          requests:\n            cpu: \"100m\"\n            memory: \"128Mi\"\n          limits:\n            cpu: \"200m\"\n            memory: \"256Mi\"<\/code><\/pre>\n
A\u00e7\u0131klamalar:<\/strong><\/p>\n
*   serviceAccountName: myapp-service-account<\/code>: Bu k\u0131s\u0131m, pod’un Workload Identity i\u00e7in yap\u0131land\u0131r\u0131lan Kubernetes Service Account’\u0131n\u0131 kullanmas\u0131n\u0131 sa\u011flar. Bu sayede proxy, belirtilen IAM Service Account’\u0131n\u0131n kimli\u011fiyle Cloud SQL’e ba\u011flan\u0131r.
\n*   myapp-container<\/code>: Ana uygulama kapsay\u0131c\u0131n\u0131zd\u0131r. DB_HOST<\/code> ve DB_PORT<\/code> ortam de\u011fi\u015fkenleri arac\u0131l\u0131\u011f\u0131yla proxy’ye ba\u011flan\u0131r.
\n*   cloudsql-proxy<\/code>: Cloud SQL Proxy kapsay\u0131c\u0131s\u0131d\u0131r.
\n    *   image<\/code>: Cloud SQL Proxy’nin Docker imaj\u0131n\u0131 belirtir. Her zaman en son kararl\u0131 s\u00fcr\u00fcm\u00fc kullanman\u0131z \u00f6nerilir.
\n    *   command<\/code>: Proxy’yi \u00e7al\u0131\u015ft\u0131ran komut ve parametreler.
\n        *   -instances=YOUR_PROJECT_ID:YOUR_REGION:YOUR_INSTANCE_NAME=tcp:5432<\/code>: Cloud SQL \u00f6rne\u011finizin tam ba\u011flant\u0131 ad\u0131n\u0131 ve proxy’nin bu \u00f6rnek i\u00e7in dinleyece\u011fi yerel TCP portunu belirtir. PostgreSQL i\u00e7in genellikle 5432, MySQL i\u00e7in 3306 kullan\u0131l\u0131r.
\n        *   -enable_iam_login<\/code>: Bu parametre, proxy’nin IAM tabanl\u0131 kimlik do\u011frulamay\u0131 etkinle\u015ftirmesini sa\u011flar. Uygulaman\u0131zda veritaban\u0131 kullan\u0131c\u0131 ad\u0131 olarak bir IAM Service Account’\u0131 kullanabilirsiniz.
\n        *   -ip_address_type=PRIVATE<\/code>: E\u011fer Cloud SQL \u00f6rne\u011finiz \u00f6zel IP adresi kullan\u0131yorsa ve GKE k\u00fcmeniz ayn\u0131 VPC a\u011f\u0131na ba\u011fl\u0131ysa bu parametreyi kullan\u0131n.
\n    *   resources<\/code>: Proxy kapsay\u0131c\u0131s\u0131 i\u00e7in CPU ve bellek kaynak isteklerini ve limitlerini tan\u0131mlamak \u00f6nemlidir. Proxy genellikle \u00e7ok fazla kaynak t\u00fcketmez, ancak uygun limitler, kaynak t\u00fckenmesini \u00f6nler.
\n    *   securityContext<\/code>: G\u00fcvenlik i\u00e7in runAsNonRoot: true<\/code> kullan\u0131lmas\u0131 \u00f6nerilir.<\/p>\n
Bu Deployment<\/code> dosyas\u0131n\u0131 uygulad\u0131ktan sonra (kubectl apply -f myapp-deployment.yaml<\/code>), pod’unuz Cloud SQL Proxy ile birlikte \u00e7al\u0131\u015facak ve uygulaman\u0131z 127.0.0.1:5432<\/code> (veya belirtilen port) \u00fczerinden veritaban\u0131na ba\u011flanabilecektir.<\/p>\n
Veritaban\u0131 Kimlik Bilgilerini Y\u00f6netme (Kubernetes Secrets)<\/h3>\n
Veritaban\u0131 kullan\u0131c\u0131 ad\u0131 ve \u015fifresi gibi hassas bilgileri do\u011frudan YAML dosyalar\u0131na yazmak yerine Kubernetes Secrets kullanmal\u0131s\u0131n\u0131z.<\/p>\n
1.  Secret Olu\u015fturma:<\/strong><\/p>\n
kubectl create secret generic cloudsql-db-credentials \\\n        --from-literal=username=your_db_username \\\n        --from-literal=password=your_db_password<\/code><\/pre>\n
    (Not: your_db_username<\/code> ve your_db_password<\/code> de\u011ferlerini kendi Cloud SQL veritaban\u0131 kullan\u0131c\u0131 ad\u0131n\u0131z ve \u015fifrenizle de\u011fi\u015ftirin.)<\/p>\n
2.  Deployment’ta Kullanma:<\/strong> Yukar\u0131daki myapp-deployment.yaml<\/code> dosyas\u0131nda env<\/code> b\u00f6l\u00fcm\u00fcndeki valueFrom<\/code> k\u0131sm\u0131nda bu Secret’\u0131n nas\u0131l kullan\u0131ld\u0131\u011f\u0131na dikkat edin.<\/p>\n
Uygulaman\u0131z\u0131 Cloud SQL Proxy’ye Ba\u011flama<\/h2>\n
Uygulaman\u0131z\u0131n Cloud SQL Proxy’ye ba\u011flanmas\u0131, sanki veritaban\u0131 ayn\u0131 makinede \u00e7al\u0131\u015f\u0131yormu\u015f gibi basittir. Ba\u011flant\u0131 dizenizde veritaban\u0131 ana bilgisayar\u0131 olarak 127.0.0.1<\/code> (veya localhost<\/code>) ve proxy’nin dinledi\u011fi yerel portu kullanman\u0131z yeterlidir.<\/p>\n
\u00d6rnek PostgreSQL Ba\u011flant\u0131 Dizesi (Node.js\/psql i\u00e7in):<\/strong><\/p>\n
const { Pool } = require('pg');\n\nconst pool = new Pool({\n  user: process.env.DB_USER,\n  host: process.env.DB_HOST, \/\/ 127.0.0.1\n  database: 'your_database_name',\n  password: process.env.DB_PASSWORD,\n  port: parseInt(process.env.DB_PORT, 10), \/\/ 5432\n});\n\npool.query('SELECT NOW()', (err, res) => {\n  if (err) {\n    console.error('Error executing query', err.stack);\n  } else {\n    console.log('Connected to Cloud SQL:', res.rows[0].now);\n  }\n});<\/code><\/pre>\n
\u00d6rnek MySQL Ba\u011flant\u0131 Dizesi (Python\/SQLAlchemy i\u00e7in):<\/strong><\/p>\n
import os\nfrom sqlalchemy import create_engine\n\nDB_USER = os.environ.get(\"DB_USER\")\nDB_PASSWORD = os.environ.get(\"DB_PASSWORD\")\nDB_HOST = os.environ.get(\"DB_HOST\") # 127.0.0.1\nDB_PORT = os.environ.get(\"DB_PORT\") # 3306\nDB_NAME = \"your_database_name\"\n\n
MySQL i\u00e7in ba\u011flant\u0131 dizesi<\/h2>\nDATABASE_URL = f\"mysql+pymysql:\/\/{DB_USER}:{DB_PASSWORD}@{DB_HOST}:{DB_PORT}\/{DB_NAME}\"\n\nengine = create_engine(DATABASE_URL)\n\ntry:\n    with engine.connect() as connection:\n        result = connection.execute(\"SELECT NOW()\")\n        print(\"Connected to Cloud SQL:\", result.scalar())\nexcept Exception as e:\n    print(\"Error connecting to Cloud SQL:\", e)<\/code><\/pre>\n
Uygulaman\u0131z, Cloud SQL Proxy’nin sundu\u011fu yerel ba\u011flant\u0131 noktas\u0131n\u0131 kullanarak veritaban\u0131na ba\u011flan\u0131r. Proxy, bu ba\u011flant\u0131y\u0131 al\u0131r, g\u00fcvenli bir \u015fekilde \u015fifreler ve Cloud SQL \u00f6rne\u011finize t\u00fcneller.<\/p>\n
En \u0130yi Uygulamalar ve Sorun Giderme<\/h2>\n
Cloud SQL Proxy’yi GKE’de kullan\u0131rken performans\u0131, g\u00fcvenli\u011fi ve kararl\u0131l\u0131\u011f\u0131 sa\u011flamak i\u00e7in baz\u0131 en iyi uygulamalar\u0131 g\u00f6z \u00f6n\u00fcnde bulundurmal\u0131s\u0131n\u0131z:<\/p>\n
En \u0130yi Uygulamalar<\/h3>\n
*   Workload Identity Kullan\u0131m\u0131:<\/strong> Daima Workload Identity’yi tercih edin. Bu, IAM Service Account anahtarlar\u0131n\u0131 Kapsay\u0131c\u0131n\u0131zda veya Secret’larda saklama riskini ortadan kald\u0131r\u0131r.
\n*   Kaynak Limitleri:<\/strong> Proxy kapsay\u0131c\u0131s\u0131 i\u00e7in CPU ve bellek kaynak istekleri ve limitleri tan\u0131mlay\u0131n. Bu, GKE’nin kaynaklar\u0131 verimli bir \u015fekilde planlamas\u0131na yard\u0131mc\u0131 olur ve proxy’nin a\u015f\u0131r\u0131 kaynak t\u00fcketmesini veya di\u011fer kapsay\u0131c\u0131lar\u0131 etkilemesini \u00f6nler.
\n*   Ba\u011flant\u0131 Havuzlama (Connection Pooling):<\/strong> Uygulaman\u0131zda veritaban\u0131 ba\u011flant\u0131 havuzlama kullan\u0131n. Her yeni veritaban\u0131 ba\u011flant\u0131s\u0131 a\u00e7mak yerine, mevcut ba\u011flant\u0131lar\u0131 yeniden kullanmak performans\u0131 art\u0131r\u0131r ve Cloud SQL \u00f6rne\u011fi \u00fczerindeki y\u00fck\u00fc azalt\u0131r. Proxy’nin kendisi bir ba\u011flant\u0131 havuzu de\u011fildir; bu, uygulama katman\u0131nda y\u00f6netilmelidir.
\n*   Liveness ve Readiness Probes:<\/strong> Uygulama kapsay\u0131c\u0131n\u0131z i\u00e7in liveness ve readiness probes tan\u0131mlad\u0131\u011f\u0131n\u0131zdan emin olun. Proxy’nin \u00e7al\u0131\u015f\u0131r durumda olup olmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in ayr\u0131 bir probe genellikle gerekli de\u011fildir, \u00e7\u00fcnk\u00fc proxy ba\u015far\u0131s\u0131z olursa uygulama da veritaban\u0131na ba\u011flanamaz.
\n*   Proxy S\u00fcr\u00fcm\u00fcn\u00fc G\u00fcncel Tutma:<\/strong> G\u00fcvenlik yamalar\u0131 ve performans iyile\u015ftirmeleri i\u00e7in Cloud SQL Proxy imaj\u0131n\u0131 d\u00fczenli olarak g\u00fcncelleyin.
\n*   \u00d6zel IP Kullan\u0131m\u0131:<\/strong> M\u00fcmk\u00fcnse, Cloud SQL \u00f6rne\u011finiz i\u00e7in \u00f6zel IP kullan\u0131n ve GKE k\u00fcmenizi ayn\u0131 VPC a\u011f\u0131na ba\u011flay\u0131n. Bu, a\u011f gecikmesini azalt\u0131r ve genel internet \u00fczerinden veri trafi\u011fi ihtiyac\u0131n\u0131 ortadan kald\u0131r\u0131r.<\/p>\n
Sorun Giderme \u0130pu\u00e7lar\u0131<\/h3>\n
*   Proxy Loglar\u0131n\u0131 Kontrol Edin:<\/strong> Proxy kapsay\u0131c\u0131s\u0131n\u0131n loglar\u0131n\u0131 kontrol ederek herhangi bir ba\u011flant\u0131 hatas\u0131 veya kimlik do\u011frulama sorunu olup olmad\u0131\u011f\u0131n\u0131 g\u00f6r\u00fcn:<\/p>\n
kubectl logs -f  -c cloudsql-proxy<\/code><\/pre>\n
*   IAM \u0130zinlerini Do\u011frulay\u0131n:<\/strong> Cloud SQL Proxy’nin kulland\u0131\u011f\u0131 IAM Hizmet Hesab\u0131n\u0131n (cloudsql-proxy-sa<\/code> veya benzeri) roles\/cloudsql.client<\/code> rol\u00fcne sahip oldu\u011fundan emin olun. Ayr\u0131ca, Kubernetes Service Account’\u0131n\u0131n do\u011fru IAM Service Account ile ili\u015fkilendirildi\u011fini kontrol edin.
\n*   Ba\u011flant\u0131 Ad\u0131n\u0131 Kontrol Edin:<\/strong> Proxy komutundaki Cloud SQL ba\u011flant\u0131 ad\u0131n\u0131n (YOUR_PROJECT_ID:YOUR_REGION:YOUR_INSTANCE_NAME<\/code>) do\u011fru oldu\u011fundan emin olun.
\n*   Yerel Portlar\u0131 Kontrol Edin:<\/strong> Uygulaman\u0131z\u0131n proxy’nin dinledi\u011fi do\u011fru yerel porta (127.0.0.1:5432<\/code> veya 127.0.0.1:3306<\/code>) ba\u011fland\u0131\u011f\u0131ndan emin olun.
\n*   A\u011f Ba\u011flant\u0131s\u0131n\u0131 Test Edin:<\/strong> GKE k\u00fcmenizden Cloud SQL \u00f6rne\u011fine temel a\u011f ba\u011flant\u0131s\u0131n\u0131n olup olmad\u0131\u011f\u0131n\u0131 kontrol edin (\u00f6zellikle \u00f6zel IP kullan\u0131yorsan\u0131z).<\/p>\n
Sonu\u00e7 ve S\u0131k\u00e7a Sorulan Sorular (SSS)<\/h2>\n
Cloud SQL Proxy’yi GKE’de kullanmak, uygulamalar\u0131n\u0131z\u0131n Google Cloud SQL veritabanlar\u0131yla g\u00fcvenli, verimli ve y\u00f6netimi kolay bir \u015fekilde etkile\u015fim kurmas\u0131n\u0131 sa\u011flayan g\u00fc\u00e7l\u00fc bir \u00e7\u00f6z\u00fcmd\u00fcr. Workload Identity ile entegrasyonu, g\u00fcvenlik duru\u015funuzu \u00f6nemli \u00f6l\u00e7\u00fcde g\u00fc\u00e7lendirirken, sidecar deseni da\u011f\u0131t\u0131m karma\u015f\u0131kl\u0131\u011f\u0131n\u0131 en aza indirir. Bu rehberdeki ad\u0131mlar\u0131 izleyerek, GKE ortam\u0131n\u0131zda Cloud SQL ba\u011flant\u0131lar\u0131n\u0131 g\u00fcvenle yap\u0131land\u0131rabilirsiniz.<\/p>\n
S\u0131k\u00e7a Sorulan Sorular (SSS)<\/h3>\n
S: Neden Cloud SQL Proxy kullanmal\u0131y\u0131z da do\u011frudan Cloud SQL’in IP adresine ba\u011flanm\u0131yoruz?<\/strong>
\nC: Do\u011frudan IP adresine ba\u011flanmak, ba\u011flant\u0131y\u0131 \u015fifresiz b\u0131rak\u0131r ve Cloud SQL \u00f6rne\u011finizin genel internete a\u00e7\u0131k olmas\u0131na neden olabilir. Proxy, t\u00fcm ileti\u015fimi TLS 1.2 ile \u015fifreler, otomatik olarak kimlik do\u011frular (IAM kullanarak) ve a\u011f g\u00fcvenlik duvar\u0131 yap\u0131land\u0131rmas\u0131n\u0131 basitle\u015ftirir.<\/p>\n
S: Cloud SQL Proxy’yi kullanmak gecikmeyi art\u0131r\u0131r m\u0131?<\/strong>
\nC: Proxy’nin kendisi \u00e7ok hafif bir ara\u00e7t\u0131r ve genellikle ihmal edilebilir bir gecikme ekler. \u00c7o\u011fu durumda, g\u00fcvenlik ve y\u00f6netim kolayl\u0131\u011f\u0131 faydalar\u0131, herhangi bir k\u00fc\u00e7\u00fck gecikme maliyetinden \u00e7ok daha a\u011f\u0131r basar. Performans i\u00e7in uygulama katman\u0131nda ba\u011flant\u0131 havuzlama kullanmak daha \u00f6nemlidir.<\/p>\n
S: Bir pod i\u00e7inde birden fazla Cloud SQL \u00f6rne\u011fine ba\u011flanabilir miyiz?<\/strong>
\nC: Evet, Cloud SQL Proxy’nin -instances<\/code> parametresine birden fazla ba\u011flant\u0131 ad\u0131 sa\u011flayarak veya her biri farkl\u0131 bir yerel portta dinleyen birden fazla proxy kapsay\u0131c\u0131s\u0131 \u00e7al\u0131\u015ft\u0131rarak birden fazla Cloud SQL \u00f6rne\u011fine ba\u011flanabilirsiniz.
\n\u00d6rnek: -instances=instance1_conn_name=tcp:5432,instance2_conn_name=tcp:3307<\/code><\/p>\n
S: Cloud SQL Proxy’nin dinledi\u011fi portu de\u011fi\u015ftirebilir miyim?<\/strong>
\nC: Evet, -instances<\/code> parametresindeki tcp:<\/code> k\u0131sm\u0131n\u0131 de\u011fi\u015ftirerek proxy’nin dinleyece\u011fi yerel portu belirleyebilirsiniz. \u00d6rne\u011fin, tcp:5000<\/code> kullanabilirsiniz. Uygulaman\u0131z\u0131n da bu porta ba\u011flanacak \u015fekilde yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131ndan emin olun.<\/p>\n
S: Cloud SQL Proxy’yi ayr\u0131 bir pod olarak \u00e7al\u0131\u015ft\u0131rmak m\u00fcmk\u00fcn m\u00fcd\u00fcr?<\/strong>
\nC: Evet, m\u00fcmk\u00fcnd\u00fcr. Ancak genellikle daha karma\u015f\u0131kt\u0131r \u00e7\u00fcnk\u00fc proxy’ye bir Kubernetes Service \u00fczerinden eri\u015filmesi ve a\u011f politikalar\u0131yla g\u00fcvenli\u011fin sa\u011flanmas\u0131 gerekir. Sidecar deseni genellikle daha basit ve daha g\u00fcvenlidir \u00e7\u00fcnk\u00fc uygulama ve proxy ayn\u0131 a\u011f ad alan\u0131n\u0131 payla\u015f\u0131r. Ayr\u0131 bir pod, \u00f6zellikle birden fazla uygulaman\u0131n tek bir proxy’yi payla\u015ft\u0131\u011f\u0131 veya legacy uygulamalar i\u00e7in d\u00fc\u015f\u00fcn\u00fclebilir.<\/p>\n
<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Cloud SQL Proxy Nedir ve Neden GKE’de Kullanmal\u0131y\u0131z?\nGoogle Cloud SQL Proxy, uygulamalar\u0131n\u0131z\u0131n Google Cloud SQL veritaban\u0131 \u00f6rnekleriyle g\u00fcv","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1341],"tags":[],"class_list":{"0":"post-39193","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-cloud","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nCloud SQL Proxy Nedir ve Neden GKE'de Kullanmal\u0131y\u0131z? - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cloud SQL Proxy Nedir ve Neden GKE'de Kullanmal\u0131y\u0131z?\" \/>\n<meta property=\"og:description\" content=\"Cloud SQL Proxy Nedir ve Neden GKE'de Kullanmal\u0131y\u0131z? Google Cloud SQL Proxy, uygulamalar\u0131n\u0131z\u0131n Google Cloud SQL veritaban\u0131 \u00f6rnekleriyle g\u00fcv\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-16T09:41:31+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Cloud SQL Proxy Nedir ve Neden GKE’de Kullanmal\u0131y\u0131z?\",\"datePublished\":\"2026-02-16T09:41:31+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/\"},\"wordCount\":1951,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Cloud\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/\",\"name\":\"Cloud SQL Proxy Nedir ve Neden GKE'de Kullanmal\u0131y\u0131z? - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-02-16T09:41:31+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Cloud SQL Proxy Nedir ve Neden GKE’de Kullanmal\u0131y\u0131z?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Cloud SQL Proxy Nedir ve Neden GKE'de Kullanmal\u0131y\u0131z? - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/","og_locale":"tr_TR","og_type":"article","og_title":"Cloud SQL Proxy Nedir ve Neden GKE'de Kullanmal\u0131y\u0131z?","og_description":"Cloud SQL Proxy Nedir ve Neden GKE'de Kullanmal\u0131y\u0131z? Google Cloud SQL Proxy, uygulamalar\u0131n\u0131z\u0131n Google Cloud SQL veritaban\u0131 \u00f6rnekleriyle g\u00fcv","og_url":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-02-16T09:41:31+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"12 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Cloud SQL Proxy Nedir ve Neden GKE’de Kullanmal\u0131y\u0131z?","datePublished":"2026-02-16T09:41:31+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/"},"wordCount":1951,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Cloud"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/","url":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/","name":"Cloud SQL Proxy Nedir ve Neden GKE'de Kullanmal\u0131y\u0131z? - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-02-16T09:41:31+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/cloud-sql-proxy-nedir-ve-neden-gkede-kullanmaliyiz\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Cloud SQL Proxy Nedir ve Neden GKE’de Kullanmal\u0131y\u0131z?"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/39193","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=39193"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/39193\/revisions"}],"predecessor-version":[{"id":39194,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/39193\/revisions\/39194"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=39193"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=39193"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=39193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}