google-kubernetes-engine

I've created a cluster on Google Kubernetes Engine (previously Google Container Engine) and installed the Google Cloud SDK and the Kubernetes tools with it on my Windows machine. It worked well for some time, and, out of nowhere, it stopped working. Every command I'm issuing with kubectl provokes the following: Unable to connect to the server: net/http: TLS handshake timeout I've searched Google, the Kubernetes Github Issues, Stack Overflow, Server Fault ... without success. I've tried the following: Restart my computer Change wifi connection Check that I'm not somehow using a proxy Delete and

I provisioned a managed GKE cluster (Kubernetes version 1.9.4-gke.1) with basic authentication disabled . When i try to create RBAC configuration (for running my ingress controller) I get a following error: Error from server (Forbidden): clusterrolebindings.rbac.authorization.k8s.io is forbidden: User "XXX@gmail.com" cannot create clusterrolebindings.rbac.authorization.k8s.io at the cluster scope: Required "container.clusterRoleBindings.create" permission. I found two related questions: GKE clusterrolebinding for cluster-admin fails with permission error User "xxx" cannot create

From the developer console, I want to disable Google Cloud Deployment Manager API, Google Compute Engine Autoscaler API, Google Compute Engine Instance Group Manager API, Google Compute Engine Instance Groups API, Google Container Engine API. However, those API cannot be disabled. When I disable the service, it show message to me that the api is disabled. However, after some time, they will be turned on again! I don't use compute engine or container engine. How can I disable those APIs? We have received some reports about this behavior and it's being investigated. I will update this answer

I Have a pod that needs to connect to a Database located on GCE Vm's with the same subnet as the GKE nodes. I currently have a k8 Service and k8 Endpoint that the pod successfully connects to but the 10.128.0.2 cannot be routed. Im sure this pertains to a GCP firewall rule/route but I havn't had much luck. subnet -> 10.128.0.0/9 cbr0 -> 10.8.15.0/20 eth0 -> 10.128.0.1 k8 services -> 10.11.224/14 Master Version: 1.9.7-gke.3 kind: Endpoints apiVersion: v1 metadata: name: externalDB namespace: default subsets: - addresses: - ip: 10.128.0.2 ports: - port: 7199 name: interface " At this point in

Is there any advantage if I use Cloud Run instead of deploying a normal service/container in GKE? I will try to add my perspective. This answer does not cover running containers in Google Cloud Run Kubernetes. The reason is that we wanted an almost zero cost solution for a legacy PHP website. Cloud Run fit perfectly and we had an easy time both porting the code and learning Cloud Run. We needed to do something with a legacy PHP website. This website was running on Windows Server 2012, IIS and PHP 7.0x. The cost was over $100.00 per month - mostly for Windows licensing fees for a VM in the

I'm setting up a CI/CD using Google's cloud tools, and was expecting to have a trigger condition "when new image is uploaded to Container Registry". The use case is separating deployment from source (repo). Source would push Docker images and deployment would deploy them to a test stage. But Cloud Build only provides me a trigger choice between three source repos. link What would you use for test, QA and production deployment of Docker images, in a GKE context? Meanwhile, there is a solution but it's a lillte cumbersome. As most of you probably know, GCR stores its images into a Bucket, it is

I created a StatefulSet on GKE, and it provisioned a bunch of GCE disks that are attached to the pods that belong to that StatefulSet. Suppose I scale the StatefulSet to 0: the constituent pods are destroyed and the disks are released. When I scale back up, the disks are reattached and mounted inside the correct pods. My questions are: How does Kubernetes keep track of which GCE disk to reconnect to which StatefulSet pod? Suppose I want to restore a StatefulSet Pod's PV from a snapshot. How can I get Kubernetes to use the disk that was created from the snapshot, instead of old disk? When you

I want to enable Stackdriver logging with my Kubernetes cluster on GKE. It's stated here: https://kubernetes.io/docs/user-guide/logging/stackdriver/ This article assumes that you have created a Kubernetes cluster with cluster-level logging support for sending logs to Stackdriver Logging. You can do this either by selecting the Enable Stackdriver Logging checkbox in the create cluster dialogue in GKE, or by setting the KUBE_LOGGING_DESTINATION flag to gcp when manually starting a cluster using kube-up.sh . But my cluster was created without this option enabled. How do I change the environment