google-kubernetes-engine

问题 My backend, in Rocket (Rust), does not have compression built in. So, it is dependent on the proxy to compress it. Though nginx ingress controller supports it, I thought whether the default one had it too as it has high availability. If it does not have, then how should I setup? 回答1: UPDATE(2018-01-31): It looks like Cloud HTTP(S) Load Balancer supports GZIP. You just have to serve compressed content from your backend and the load balancer will pass it on. However, NGINX is confused because

问题 My backend, in Rocket (Rust), does not have compression built in. So, it is dependent on the proxy to compress it. Though nginx ingress controller supports it, I thought whether the default one had it too as it has high availability. If it does not have, then how should I setup? 回答1: UPDATE(2018-01-31): It looks like Cloud HTTP(S) Load Balancer supports GZIP. You just have to serve compressed content from your backend and the load balancer will pass it on. However, NGINX is confused because

问题 Problem summary: New session ID is generated for each request in my application, but only within Google Cloud Container Engine infrastructure. Root cause: I found the root cause of the problem. The session affinity set for Ingress does not work as I expected. Here is how it's created: I'm creating deployment with 2 replicas (basic java application with servlets) I'm creating NodePort service as described here (but using YAML) I'm creating Ingress controler using YAML I'm adding a cookie based

问题 Is there a way to be able to provide ReadWriteMany storage without having to implement a storage cluster? I was able to provide storage with gcsfuse but it is really slow. I need something close to the speed of GlusterFS. I am currently using GlusterFS. 回答1: Another option: Google Cloud Platform recently started offering a hosted NFS service called Cloud Firestore. Note that as of this writing, Cloud Firestore is still in Beta. Here's the description: Use Cloud Filestore to create fully

问题 Is there a way to be able to provide ReadWriteMany storage without having to implement a storage cluster? I was able to provide storage with gcsfuse but it is really slow. I need something close to the speed of GlusterFS. I am currently using GlusterFS. 回答1: Another option: Google Cloud Platform recently started offering a hosted NFS service called Cloud Firestore. Note that as of this writing, Cloud Firestore is still in Beta. Here's the description: Use Cloud Filestore to create fully

问题 There is a helm chart for nexus: https://github.com/helm/charts/tree/master/stable/sonatype-nexus I installed it like using helm: helm install stable/sonatype-nexus --name=nexus But it didn't work because of nexus-proxy. There is logs for nexus-proxy container: [vert.x-eventloop-thread-0] [io.vertx.ext.web.impl.RoutingContextImplBase] Unexpected exception in route So, i started to google and found that post: https://github.com/travelaudience/nexus-proxy/issues/4 There we no answer except this

问题 There is a helm chart for nexus: https://github.com/helm/charts/tree/master/stable/sonatype-nexus I installed it like using helm: helm install stable/sonatype-nexus --name=nexus But it didn't work because of nexus-proxy. There is logs for nexus-proxy container: [vert.x-eventloop-thread-0] [io.vertx.ext.web.impl.RoutingContextImplBase] Unexpected exception in route So, i started to google and found that post: https://github.com/travelaudience/nexus-proxy/issues/4 There we no answer except this

问题 There is a helm chart for nexus: https://github.com/helm/charts/tree/master/stable/sonatype-nexus I installed it like using helm: helm install stable/sonatype-nexus --name=nexus But it didn't work because of nexus-proxy. There is logs for nexus-proxy container: [vert.x-eventloop-thread-0] [io.vertx.ext.web.impl.RoutingContextImplBase] Unexpected exception in route So, i started to google and found that post: https://github.com/travelaudience/nexus-proxy/issues/4 There we no answer except this

问题 I am on GKE using Istio version 1.0.3 . I try to get my express.js with socket.io (and uws engine) backend working with websockets and had this backend running before on a 'non kubernetes server' with websockets without problems. When I simply enter the external_gke_ip as url I get my backend html page, so http works. But when my client-app makes socketio authentication calls from my client-app I get 503 errors in the browser console: WebSocket connection to 'ws://external_gke_ip/socket.io/

问题 On GKE, kube-dns is running on my nodes, I can see the docker containers. I do have access to Services by name, which is great for all these applications where load balancing is a perfectly suitable solution, but how would I use the DNS to access individual pods? I know I can look up specific pods in the API, but I need to update the hosts file myself, and keep watching the pod list. DNS is supposed to do that for me so how is it meant to be used within a pod? The Kubernetes doc says the DNS