We’re consistently on the lookout for methods to simplify the developer expertise on Google Cloud.
Google Kubernetes Engine (GKE) is an easy method to robotically deploy, scale, and handle Kubernetes. Cloud SQL is a totally managed relational database service for MySQL, PostgreSQL, and SQL Server. Builders usually deploy their purposes to GKE and retailer their information in Cloud SQL, so connecting GKE to Cloud SQL is usually one of many first large steps in deploying a full stack utility. The Kubernetes operator simplifies that course of.
The right way to join from GKE to Cloud SQL
Typically, the simplest approach to connect with Cloud SQL is with a language-specific Cloud SQL connector. There are Cloud SQL connectors for Java, Python, and Go — with extra to return sooner or later. In case your utility is written in a kind of languages, we advocate beginning with a connector. In any other case, the Cloud SQL Auth proxy is probably going the proper selection in your purposes operating on Google Kubernetes Engine. Should you’re keen to affix us on the forefront, the Kubernetes operator is now in Public Preview.
Switching to the Cloud SQL Auth Proxy Kubernetes Operator
The Cloud SQL Proxy Operator is presently in Public Preview. Listed below are a couple of thrilling advantages for these able to make the change:
Configure a Cloud SQL Auth Proxy in eight traces of YAML — saving you about 40 traces of YAML configuration (or hundreds for giant clusters)
Easy configuration of a single Cloud SQL Proxy particular useful resource — permitting a number of Kubernetes purposes to share the identical proxy
Finest practices by default — we preserve the operator and replace it to the most recent suggestions
Computerized deployment when the proxy configuration adjustments (coming within the GA launch)
Right here’s an instance of what configuration may seem like earlier than the operator. Word how a lot easier and extra elegant the brand new operator makes deployment.