kubernetes-ingress

问题 I am trying to startup a .NET k8s cluster running inside the Docker for Windows client. I setup an ingress controller like so: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: ingress-service annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/rewrite-target: / spec: rules: - http: paths: - path: /identity/ backend: serviceName: identity-cluster-ip-service servicePort: 5050 With example identity service configured like so: apiVersion: v1 kind: Service

问题 Kubernetes Version: 1.10 Running on Barematel No. of masters: 3 We are running our multiple microservices inside a Kubernetes cluster. Currently, we are exposing these services outside of the cluster using NodePort . Each microservice has it's own NodePort so we have to maintain a list with the corresponding microservices. Since we are running on Barematel we don't have features like LodeBalancer while exposing a microservice. Problem: - Since we have multiple masters and workers inside the

问题 I have two spring boot container, I want to setup ingress service. As document here says, ingress has two parts, one is controller, the other is resources. My two resources are two containers: gearbox-rack-eureka-server and gearbox-rack-config-server. The difference is port so that ingress could route traffic by different ports. My yaml files are listed below: eureka_pod.yaml apiVersion: v1 kind: Pod metadata: name: gearbox-rack-eureka-server labels: app: gearbox-rack-eureka-server purpose:

问题 I want setup Traefik backend health check via Kubernetes annotation, but looks like Kubernetes Ingress does not support that functionality according to official documentation. Is any particular reason why Traefik does not support that functionality for Kubernetes Ingress? I'm wondering because Mesos support health checks for a backend. I know that in Kubernetes you can configure readiness/liveness probe for the pods, but I have leader/follower fashion service, so Traefik should route the

问题 I deployed a spring boot app in kubernetes pod. But normally I access any app in this way of proxy port forwarding - http://192.64.125.29:8001/api/v1/namespaces/kube-system/services/https:hello-app:/proxy/ But my spring boot app is running in this below url - http://192.64.125.29:8001/api/v1/namespaces/kube-system/services/https:myspringbootapp:/proxy/ But I have no idea how to invoke my controller end point /visitid 回答1: If you are just trying to do a quick check then you can port-forward to

问题 I followed exactly like this_tutorial to deploy nginx ingress contoller. The yaml files used for deploying the ingress controller and describe output are copied to repo. After creating the ingress-controller, pod is running but seeing the below error in the ingress-controller log. The error says serviceaccount "nginx" have no permission to create resource "configmaps" in namespace "ingress". Question I have, what verbs are required in the ClusterRole to allow service account "nginx" to create

问题 We are having a Kubernetes service whose pods take some time to warm up with first requests. Basically first incoming requests will read some cached values from Redis and these requests might take a bit longer to process. When these newly created pods become ready and receive full traffic, they might become not very responsive for up to 30 seconds, before everything is correctly loaded from Redis and cached. I know, we should definitely restructure the application to prevent this,

问题 I am using minikube for developing an application on Kubernetes and I am using Traefik as the ingress controller. I am able to connect and use my application services when I use the url of the host which I defined in the ingress ("streambridge.local") and I set up in the linux hosts ("/etc/hosts"). But when I use the exact same ip address that I used for the dns I am not able to connect to any of the services and I receive "404 page not found". I have to mention that I am using the IP address

问题 I deploy traefik ingress controller pod and then two services, one of them a LoadBalancer type for reverse-proxy and the other a ClusterIP for dashboard. Also I create ingress for redirect all <elb-address>/dashboard to my traefik dashboard. but for some reason I get 404 error code when I trying to request my dashboard at aws-ip/dashboard That is the manifest yamls that I use to set up traefik --- apiVersion: v1 kind: ServiceAccount metadata: name: traefik-ingress-controller namespace: kube

问题 I have kubeadm and Kubernetes v1.12 without AWS or Google Cloud. I want to know if the Kubernetes cluster installed already has an ingress controller and if it has two what is the default. Thanks :) 回答1: You can check for pods implementing ingress controllers (actually with ingress in the name) with: kubectl get pods --all-namespaces | grep ingress And services exposing them with: kubectl get service --all-namespaces | grep ingress As @Prafull Ladha says, you won't have an ingress controller