How to access mysql in kubernetes

Console

Create an instance with a public IP address

1. In the Google Cloud console, go to the Cloud SQL Instances page.

   Go to Cloud SQL Instances

2. Click Create Instance.
3. Click MySQL.
4. Enter quickstart-instance for Instance ID.
5. Enter a password for the root user. Save this password for future use.
6. Click the Single zone option for Choose region and zonal availability.
7. Click and expand the Show Configurations section.
8. In the Machine Type drop-down menu, select Lightweight.

9. Click Create Instance and wait until the instance initializes and starts.

gcloud

Create an instance with a public IP address

Before running the gcloud sql instances create command as follows, replace DB_ROOT_PASSWORD with the password of your database user.

Optionally, modify the values for the following parameters:

• --database_version: The database engine type and version. If left unspecified, the API default is used. See the gcloud database versions documentation to see the currently available versions.
• --cpu: The number of cores desired in the machine.
• --memory: Whole number value indicating how much memory is desired in the machine. A size unit should be provided (for example, 3072MB or 9GB). If no units are specified, GB is assumed.
• --region: Regional location of the instance (for example asia-east1, us-east1). If left unspecified, the default us-central is used. See the full list of regions.

Run the gcloud sql instances create command to create a Cloud SQL instance.

gcloud sql instances create quickstart-instance \
--database-version=MYSQL_8_0 \
--cpu=1 \
--memory=4GB \
--region=us-central1 \
--root-password=DB_ROOT_PASSWORD

Console

Create an instance with a private IP address and SSL enabled

1. In the Google Cloud console, go to the Cloud SQL Instances page.

   Go to Cloud SQL Instances

2. Click Create instance.
3. Click MySQL.
4. Enter quickstart-instance for Instance ID.
5. Enter a password for the root user. Save this password for future use.
6. Click the Single zone option for Choose region and zonal availability.
7. Click and expand Show configuration options.
8. For Machine Type, select Lightweight.
9. In Connections, select Private IP.
10. Select default in the Network drop-down menu.
11. If you see a dialog stating Private services access connection required, click the Set Up Connection button.
• In the Enable Service Networking API dialog, click the Enable API button.
• In the Allocate an IP range dialog, select Use an automatically allocated IP range and click Continue.
• In the Create a connection dialog, click Create Connection.
12. Clear the Public IP checkbox to create an instance only with a private IP.
13. Click Create instance and then wait for the instance to initialize and start.
14. Click Connections.
15. In the Security section, select Allow only SSL connections to enable SSL connections.
16. In the Enable SSL dialog, click Enable and restart and then wait for the instance to restart.

gcloud

Create an instance with a private IP address and SSL enabled

Creating an instance with a private IP address only requires configuring private services access to enable connections from other Google Cloud services, such as GKE.

1. Run the gcloud compute addresses create command to allocate an IP range for a private services access connection:

gcloud compute addresses create google-managed-services-default \
--global \
--purpose=VPC_PEERING \
--prefix-length=16 \
--description="peering range for Google" \
--network=default

2. Run the gcloud services vpc-peerings connect command to create the private services access connection:

gcloud services vpc-peerings connect \
--service=servicenetworking.googleapis.com \
--ranges=google-managed-services-default \
--network=default

3. Before running the gcloud sql instances create command to create an instance as follows, replace DB_ROOT_PASSWORD with the password of your database user.

Optionally, modify the values for the following parameters:

• --database_version: The database engine type and version. If left unspecified, the API default is used. See gcloud database versions for a list of currently available versions.
• --cpu: The number of cores in the machine.
• --memory: A whole number indicating how much memory to include in the machine. A size unit can be provided (for example, 3072MB or 9GB). If no units are specified, GB is assumed.
• --region: The regional location of the instance (for example asia-east1, us-east1). If left unspecified, the default us-central1 is used. See the full list of regions.

Run the gcloud sql instances create command to create a Cloud SQL instance with a private IP address.

 gcloud beta sql instances create quickstart-instance \
--database-version=MYSQL_8_0 \
--cpu=1 \
--memory=4GB \
--region=us-central1 \
--root-password=DB_ROOT_PASSWORD \
--no-assign-ip \
--network=default

4. Run the gcloud sql instances patch command to allow only SSL connections for the instance.

gcloud sql instances patch quickstart-instance --require-ssl

gcloud sql databases create quickstart_db --instance=quickstart-instance

gcloud sql users create quickstart-user \
--instance=quickstart-instance \
--password=DB_PASS

gcloud container clusters create-auto gke-cloud-sql-quickstart \
    --region us-central1

With the sample app configuration in place, you can now deploy the sample app.

Go

The deployed sample app connects to your Cloud SQL instance using the Cloud SQL proxy running in a Kubernetes sidecar pattern. The sidecar pattern is accomplished by deploying a workload with an additional container that shares the same Kubernetes pod as the sample app's container.

1. Get the Cloud SQL instance connection name by running the gcloud sql instances describe command:

   gcloud sql instances describe quickstart-instance --format='value(connectionName)'

2. Update the deployment.yaml file in Cloud Shell Editor. Make the following replacements and edits:
   • Replace <YOUR_KSA_NAME> with ksa-cloud-sql.
   • Replace <LOCATION> with us-central1.
   • Replace <YOUR_PROJECT_ID> with the project ID.
   • Replace <YOUR-DB-SECRET> with gke-cloud-sql-secrets.
   • Replace <INSTANCE_CONNECTION_NAME> with the Cloud SQL instance connection name retrieved from the gcloud command on the previous step. The format is project_id:region:instance_name. The instance connection name is also visible in the Cloud SQL instance Overview page.
   • Enable the Cloud SQL Auth proxy to connect to your Cloud SQL instance using its private IP address. Uncomment the "-ip_address_types=PRIVATE" flag by removing the # comment symbol and its trailing white space. The uncommented flag should look like this:

     - "-ip_address_types=PRIVATE"

3. Run the kubectl apply command as follows in Cloud Shell to deploy the sample app:

   kubectl apply -f deployment.yaml

4. Run the kubectl apply command as follows to add a load balancer in front of the deployment, so that you can access it through the internet:

   kubectl apply -f service.yaml

5. Run the kubectl get command as follows to get the service details:

   kubectl get services

6. Copy the External IP address once it becomes available in the service details, which may take a few minutes.
7. View the deployed sample app. Open a browser window and go to the service's External IP address.
   

Java

The deployed sample app connects to your Cloud SQL instance using the Cloud SQL Java connector.

1. Get the Cloud SQL instance connection name by running the gcloud sql instances describe command:

   gcloud sql instances describe quickstart-instance --format='value(connectionName)'

2. Update the deployment.yaml file in Cloud Shell Editor. Make the following replacements:
   • <YOUR_KSA_NAME> with ksa-cloud-sql.
   • <LOCATION> with us-central1.
   • <YOUR_PROJECT_ID> with the project ID.
   • <YOUR-DB-SECRET> with gke-cloud-sql-secrets.
   • <INSTANCE_CONNECTION_NAME> with the Cloud SQL instance connection name retrieved from the gcloud command on the previous step. The format is project_id:region:instance_name. The instance connection name is also visible in the Cloud SQL instance Overview page.
3. Run the kubectl apply command as follows in Cloud Shell to deploy the sample app:

   kubectl apply -f deployment.yaml

4. Run the kubectl apply command as follows to add a load balancer in front of the deployment, so that you can access it through the internet:

   kubectl apply -f service.yaml

5. Run the kubectl get command as follows to get the service details:

   kubectl get services

6. Copy the External IP address once it becomes available in the service details, which may take a few minutes.
7. View the deployed sample app. Open a browser window and go to the service's External IP address.
   

Node.js

The deployed sample app connects to your Cloud SQL instance using the Cloud SQL proxy running in a Kubernetes sidecar pattern. The sidecar pattern is accomplished by deploying a workload with an additional container that shares the same Kubernetes pod as the sample app's container.

1. Get the Cloud SQL instance connection name by running the gcloud sql instances describe command:

   gcloud sql instances describe quickstart-instance --format='value(connectionName)'

2. Update the deployment.yaml file in Cloud Shell Editor. Make the following replacements and edits:
   • Replace <YOUR_KSA_NAME> with ksa-cloud-sql.
   • Replace <LOCATION> with us-central1.
   • Replace <YOUR_PROJECT_ID> with the project ID.
   • Replace <YOUR-DB-SECRET> with gke-cloud-sql-secrets.
   • Replace <INSTANCE_CONNECTION_NAME> with the Cloud SQL instance connection name retrieved from the gcloud command on the previous step. The format is project_id:region:instance_name. The instance connection name is also visible in the Cloud SQL instance Overview page.
   • Enable the Cloud SQL Auth proxy to connect to your Cloud SQL instance using its private IP address. Uncomment the "-ip_address_types=PRIVATE" flag by removing the # comment symbol and its trailing white space. The uncommented flag should look like this:

     - "-ip_address_types=PRIVATE"

3. Run the kubectl apply command as follows in Cloud Shell to deploy the sample app:

   kubectl apply -f deployment.yaml

4. Run the kubectl apply command as follows to add a load balancer in front of the deployment, so that you can access it through the internet:

   kubectl apply -f service.yaml

5. Run the kubectl get command as follows to get the service details:

   kubectl get services

6. Copy the External IP address once it becomes available in the service details, which may take a few minutes.
7. View the deployed sample app. Open a browser window and go to the service's External IP address.
   

Python

The deployed sample app connects to your Cloud SQL instance using the Cloud SQL proxy running in a Kubernetes sidecar pattern. The sidecar pattern is accomplished by deploying a workload with an additional container that shares the same Kubernetes pod as the sample app's container.

1. Get the Cloud SQL instance connection name by running the gcloud sql instances describe command:

   gcloud sql instances describe quickstart-instance --format='value(connectionName)'

2. Update the deployment.yaml file in Cloud Shell Editor. Make the following replacements and edits:
   • Replace <YOUR_KSA_NAME> with ksa-cloud-sql.
   • Replace <LOCATION> with us-central1.
   • Replace <YOUR_PROJECT_ID> with the project ID.
   • Replace <YOUR-DB-SECRET> with gke-cloud-sql-secrets.
   • Replace <INSTANCE_CONNECTION_NAME> with the Cloud SQL instance connection name retrieved from the gcloud command on the previous step. The format is project_id:region:instance_name. The instance connection name is also visible in the Cloud SQL instance Overview page.
   • Enable the Cloud SQL Auth proxy to connect to your Cloud SQL instance using its private IP address. Uncomment the "-ip_address_types=PRIVATE" flag by removing the # comment symbol and its trailing white space. The uncommented flag should look like this:

     - "-ip_address_types=PRIVATE"

3. Run the kubectl apply command as follows in Cloud Shell to deploy the sample app:

   kubectl apply -f deployment.yaml

4. Run the kubectl apply command as follows to add a load balancer in front of the deployment, so that you can access it through the internet:

   kubectl apply -f service.yaml

5. Run the kubectl get command as follows to get the service details:

   kubectl get services

6. Copy the External IP address once it becomes available in the service details, which may take a few minutes.
7. View the deployed sample app. Open a browser window and go to the service's External IP address.