google-kubernetes-engine

问题 I'm hitting 429 error in Google Container Registry, too many images are pulled simultaneously Error: Status 429 trying to pull repository [...] "Quota Exceeded." There is a Kubernetes cluster with multiple nodes and pods implement Kubeflow steps. In the Google guide they suggest the following: To avoid hitting the fixed quota limit, you can: - Increase the number of IP addresses talking to Container Registry. Quotas are per IP address. - Add retries that introduce a delay. For example, you

问题 I have a volume PersistentVolumeClaim that I want to run snapshots for. I know there is VolumeSnapshot docs. I think the best way to run periodic snapshots is to create a CronJob for that. So I've created a docker image with python k8s client and my custom script. This way I'm able to run it whenever I want and I can access kube config and all resources directly from the pod. FROM python:3.8-slim-buster RUN apt-get -qq update && apt-get -qq install -y git COPY . . RUN pip install --upgrade

问题 We have a below code for Ingress and "/demo" app is running fine with REST API Get call response. However "/um" is not opening and its giving 404 error. UM is a front-end app built in Angular 6 and it should open an index page. When we expose this application as a External IP i.e. Type:LoadBalancer, then application is working fine. The same is encountering 404 when try from Ingress setup. Not sure what commits this issue. The below is our sample Ingress deployment file. Kindly through some

问题 I am creating a deployment in GKE with a following (standard) deployment apiVersion: apps/v1 kind: Deployment metadata: name: api-deployment spec: replicas: 1 selector: matchLabels: component: api template: metadata: labels: component: api spec: containers: - name: api image: eu.gcr.io/xxxx-xxx/api:latest imagePullPolicy: Always resources: requests: memory: "320Mi" cpu: "100m" limits: memory: "450Mi" cpu: "150m" ports: - containerPort: 5010 However, for some reason GKE complains about a

问题 I have deployed a gRPC server using Google Cloud Endpoints / ESP, following the instructions here: https://cloud.google.com/endpoints/docs/grpc/get-started-kubernetes-engine In my proto file, my fields are named in snake_case, following the Protocol Buffers naming conventions (https://developers.google.com/protocol-buffers/docs/style#message-and-field-names), as below: message MyMessage { string my_field = 1; } When deploying to Cloud Endpoints, the field names are converted to camelCase. So

问题 Recently I did an upgrade on my cluster that's running multiple containers for microservices written in Java (using default Spring Boot's log4j2 default configuration). Since then, the container log is not being updated anymore. The kubectl logs command is working fine, all the recent logs can be seen using this command, but the logs that should be appearing in the GKE dashboard is simply not working anymore. I checked the Google's Loggin API and it's enabled. Does anyone know what's the

问题 Recently I did an upgrade on my cluster that's running multiple containers for microservices written in Java (using default Spring Boot's log4j2 default configuration). Since then, the container log is not being updated anymore. The kubectl logs command is working fine, all the recent logs can be seen using this command, but the logs that should be appearing in the GKE dashboard is simply not working anymore. I checked the Google's Loggin API and it's enabled. Does anyone know what's the

问题 I am dealing with CRDs and creating Custom resources. I need to keep lots of information about my application in the Custom resource. As per the official doc, etcd works with request up to 1.5MB. I am hitting errors something like "error": "Request entity too large: limit is 3145728" I believe the specified limit in the error is 3MB. Any thoughts around this? Any way out for this problem? 回答1: The "error": "Request entity too large: limit is 3145728" is probably the default response from

问题 I updated a GKE cluster from 1.13 to 1.15.9-gke.12. In the process I switched from legacy logging to Stackdriver Kubernetes Engine Monitoring. Now I have the problem that the stackdriver-metadata-agent-cluster-level pod keeps restarting because it gets OOMKilled . The memory seems to be just fine though. The logs also look just fine (same as the logs of a newly created cluster): I0305 08:32:33.436613 1 log_spam.go:42] Command line arguments: I0305 08:32:33.436726 1 log_spam.go:44] argv[0]: '

问题 I have a simple Python app running in a container on Google Kubernetes Engine. I am trying to connect the standard Python logging to Google Stackdriver logging using this guide. I have almost succeeded, but I am getting duplicate log entries with one always at the 'error' level... Screenshot of Stackdriver logs showing duplicate entries This is my python code that set's up the logging according to the above guide: import webapp2 from paste import httpserver import rpc # Imports the Google