kubernetes-ingress

问题 I've recently asked a question about how to structure multiple applications which should be bundled together and am thinking of going down a route of having each separate application have it's own Helm chart and own ingress controller. This would allow for CI/CD to update each component easily without affecting the rest. I was also thinking about using a "Umbrella" chart to specify versions of the other charts when it comes to actual releases and keep that in another repo. However, when using

问题 I am using this tutorial ingress on GCE. The tutorial works fine with docker image in it but with my docker image, I always get UNHEALTHY state of backend service. I added liveness and readiness TCP probes as my application does not respond to '/' with 200. The deployment yaml look like below apiVersion: apps/v1 kind: Deployment metadata: labels: run: neg-demo-app # Label for the Deployment name: neg-demo-app # Name of Deployment spec: # Deployment's specification selector: matchLabels: run:

问题 I have an application running on kubernetes and I am using minikube for developing and testing it. I set up the minikube, ingress and application and they are working locally as I described here "Traefik ingress does not work with cluster IP" but I don't know how to connect to my application from a remote machine. What I want to do is, I want to run some performance test and find the bottleneck in my application. The application and minikube are located on machine-A and I want to send some

问题 I am setting up 2 VPC on GCP, I setup kubeadm on each, let's call them kubemaster and kubenode1. So I ran kubeadm on kubemaster and kubenode1 which : kubeadm init on kubemaster kubeadm join on kubenode1 When I was trying to kubectl apply -f (a deployment which contains a pod with simple webapps inside) and kubectl apply -f (a NodePort type of Service which target the deployment port) After that I simply access the webapps from my browser (on my local machine not on GCP), it just does not work

问题 My ingress controller is working and I am able to access the service outside the cluster using http://(externalIP)/path using an HTTP GET request from a RestClient. However, I had to specify the "Host" header with value = "host" (value of my Ingress Resource) for this to work. Because of this, I am not able to hit http://(externalIP)/path from my web browser. Is there any way I can enable access from my external web browser without having to specify "Host" in the request header? Ingress

问题 I can not remove kubernetes-dashboard from minikube. I tried deleting the deployment "deployment.apps/kubernetes-dashboard" multiple times. But it gets recreated automatically in few seconds. I am using following command to delete the deployment: kubectl delete deployment.apps/kubernetes-dashboard -n kube-system I even tried to edit the deployment by setting replica count to zero. But even it gets reset automatically after few seconds. The same thing happens for nginx-ingress deployment in

问题 Facing this issue if I am connecting to ingress for web socket service failed: Error during WebSocket handshake: Unexpected response code: 400 Ingress YAML kind: Ingress apiVersion: extensions/v1beta1 metadata: name: websocket-producer-cdph spec: rules: host: some.domain.com http: paths: path: "/" backend: serviceName: websocket-producer-cdph servicePort: 8183 status: loadBalancer: ingress: {} Service YAML kind: Service apiVersion: v1 metadata: name: websocket-producer-cdph spec: ports: name:

问题 Kubernetes documentation example here shows how a network policy can be applied for a source specified by either a pod selector OR a namespace selector. Can I specify a source the fulfills both constraints at the same time. e.g. Can a source be a pod with label "tier=web" which is deployed in namespace "ingress". P.S. For now, I have it working by adding namespace name as pod-labels. 回答1: Yes, this is possible, but not immediately intuitive. If you look at the section below the chunk you

问题 I am deploying a number of docker containers of micro-services and angular frontend on Kubernetes. I have exposed the services using an ingress controller specifying each service using this, and specifying paths in backend. apiVersion: extensions/v1beta1 kind: Ingress For my frontend, I have created a service with type loadbalancer. apiVersion: v1 kind: Service metadata: annotations: service.beta.kubernetes.io/azure-load-balancer-resource-group: my-resource-group name: myapp-svc namespace: ui

问题 I am deploying a number of docker containers of micro-services and angular frontend on Kubernetes. I have exposed the services using an ingress controller specifying each service using this, and specifying paths in backend. apiVersion: extensions/v1beta1 kind: Ingress For my frontend, I have created a service with type loadbalancer. apiVersion: v1 kind: Service metadata: annotations: service.beta.kubernetes.io/azure-load-balancer-resource-group: my-resource-group name: myapp-svc namespace: ui