google-kubernetes-engine

问题 I'm setting up a GKE cluster on Google Kubernetes Engine to run some heavy jobs. I have a render-pool of big machines that I want to autoscale from 0 to N (using the cluster autoscaler). My default-pool is a cheap g1-small to run the system pods (those never go away so the default pool can't autoscale to 0, too bad). My problem is that the render-pool doesn't want to scale down to 0. It has some system pods running on it; are those the problem? The default pool has plenty of resources to run

问题 I am unable to curl to the external IP of the service. My Kubernetes cluster is deployed on GKE. $ kubectl run kubia-container --image=australia/kubia_py --port=8080 --generator=run/v1 kubectl run --generator=run/v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead. replicationcontroller/kubia-container created $ kubectl get pods NAME READY STATUS RESTARTS AGE kubia-container-6b2cs 1/1 Running 0 25s $ kubectl expose rc

问题 getting this error from today evening in google cloud . Something happened wrong with gcloud. Same commands were working till yesterday. helm install --name nginx-ingress stable/nginx-ingress --set rbac.create=true --set controller.publishService.enabled=true i have followed steps: https://cloud.google.com/community/tutorials/nginx-ingress-gke enter image description here (mykubeproject1)$ helm install --name nginx-ingress stable/nginx-ingress --set rbac.create=true --set controller

问题 I am learning dask-kubernetes on GKE. I stumbled across an asyncio error (ERROR:asyncio:Task exception was never retrieved). See steps below for the issue. However, additional guidance on using deploying dask-kubernetes with a remote Kubernetes cluster is appreciated (note I used helm with good experience here but want to try the native approach as I can't scale the helm approach). Create the cluster: $ gcloud container clusters create --machine-type n1-standard-2 --num-nodes 2 --zone us

问题 I created GKE cluster using GKE API. Below is the payload and end point I used. API: https://container.googleapis.com/v1/{parent=projects/ /locations/ }/clusters Method: POST RequestBody: { "cluster": { "name": "test", "masterAuth": { "clientCertificateConfig": { "issueClientCertificate": true } }.... } ...... ..... } NOTE: I'am creating GKE cluster with masterAuth enabled by setting clientCertificate to true. After cluster creation, I created the kubeconfig in my local machine using the

问题 I created GKE cluster using GKE API. Below is the payload and end point I used. API: https://container.googleapis.com/v1/{parent=projects/ /locations/ }/clusters Method: POST RequestBody: { "cluster": { "name": "test", "masterAuth": { "clientCertificateConfig": { "issueClientCertificate": true } }.... } ...... ..... } NOTE: I'am creating GKE cluster with masterAuth enabled by setting clientCertificate to true. After cluster creation, I created the kubeconfig in my local machine using the

问题 I'm running a GitLab instance from the official jetstack helm chart on my GKE cluster within the Google Cloud. I would like to add a Windows VM to my VPC network that has only internal network access. Normally you have to register the GitLab runner against the https address of GitLab which is not possible with an internal network. Is there a way to register the GitLab runner against the GitLab instance via the internal network? The GitLab instance has its https resource published via an nginx

问题 Pretty simple question, how can I get the Pod where my current go code is running? I need it because for some reason, I need to ping directly the Pod's code instead of using my regular endpoint which would be the load balancer. My current config: apiVersion: v1 kind: Service metadata: name: web-socket-service-api spec: ports: # Port that accepts gRPC and JSON/HTTP2 requests over HTTP. - port: 8080 targetPort: 8080 protocol: TCP name: grpc # Port that accepts gRPC and JSON/HTTP2 requests over

问题 I am trying to use KubeVirt with GKE cluster. I found I am able to create a nested virtualization enabled GCP VM, but I didn't find a way to achieve the same thing for GKE cluster node. If I cannot enable nested virtualization for GKE cluster node, I can only use the kubevirt with debug.useEmulation which is not what I want. Thanks 回答1: Currently nested virtualization is available only on GCE as per this docs. There is already question regarding supporting Nested Virtualization on GKE and it

问题 I have been trying to create HTTPS endpoint in Google Cloud K8s environment. I have built a flask application in Python that serves on the waitress production environment via port 5000. serve(app, host='0.0.0.0', port=5000, ipv6=False, threads=30) I created a docker file and pushed this to the google cloud repository. Then, created a Kubernetes cluster with one workload containing this image. After, I exposed this via external IP by creating LoadBalancer. (After pushing the image to the