[Wordpress Setup] Trouble setting up persistent disks

[yeshwanthvshenoy]

I am trying to set up a Wordpress website using Kubernetes Engine. I am following the official documentation. When trying to do kubectl apply -f $WORKING_DIR/wordpress-volumeclaim.yaml, I get the following error:

error: unable to recognize "/home/username/kubernetes-engine-samples/wordpress-persistent-disks/wordpress-volumeclaim.yaml": Get https://34.68.148.241/api?timeout=32s: x509: certificate signed by unknown authority

I am not sure what is happening nor does the error make any sense. I am trying this on a fresh GCP account and hence not sure what this IP address is also. This is definitely not the cluster ip as I can check it in the GCP UI. The command I used to create the cluster is as below:

 gcloud beta container --project "test-project" clusters create "wordpress" --zone "us-central1-a" --no-enable-basic-auth --cluster-version "1.14.7-gke.14" --machine-type "f1-micro" --image-type "COS" --disk-type "pd-standard" --disk-size "30" --metadata disable-legacy-endpoints=true --scopes "https://www.googleapis.com/auth/devstorage.read_only","https://www.googleapis.com/auth/logging.write","https://www.googleapis.com/auth/monitoring","https://www.googleapis.com/auth/servicecontrol","https://www.googleapis.com/auth/service.management.readonly","https://www.googleapis.com/auth/trace.append" --num-nodes "3" --enable-stackdriver-kubernetes --enable-ip-alias --network "projects/savewiz-qa/global/networks/default" --subnetwork "projects/savewiz-qa/regions/us-central1/subnetworks/default" --default-max-pods-per-node "110" --addons HorizontalPodAutoscaling,HttpLoadBalancing --enable-autoupgrade --enable-autorepair

Any guidance or support documents to troubleshoot this as I am new to Kubernetes as well? I am not on paid support to answer my queries via tickets.

[yeshwanthvshenoy]

Figured out issue using this link