kubernetes-ingress

问题 I have three services running in my backend and the Ingress routing is defined like this: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: myapp-ingress annotations: kubernetes.io/ingress.class: nginx certmanager.k8s.io/cluster-issuer: letsencrypt-prod nginx.ingress.kubernetes.io/rewrite-target: / spec: tls: - hosts: - myapp.westeurope.cloudapp.azure.com secretName: acme-crt-secret rules: - host: myapp.westeurope.cloudapp.azure.com http: paths: - path: / backend: serviceName:

问题 I'm new to istio. I have a simple ingress gateway yaml file, and the listenling port is 26931, but after I applied the yaml, the port 26931 does not appear in the set of ports which ingress gateway expose. So am I lack of some necessary step or something else? apiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: batman-gateway spec: selector: istio: ingressgateway servers: - port: number: 26931 name: http protocol: HTTP hosts: - "*" 回答1: You are exposing ports not with

问题 I'm new to istio. I have a simple ingress gateway yaml file, and the listenling port is 26931, but after I applied the yaml, the port 26931 does not appear in the set of ports which ingress gateway expose. So am I lack of some necessary step or something else? apiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: batman-gateway spec: selector: istio: ingressgateway servers: - port: number: 26931 name: http protocol: HTTP hosts: - "*" 回答1: You are exposing ports not with

问题 I am trying to expose an application in my cluster by creating a service type as load balancer. The reason for this is that I want this app to have a separate channel for communication. I have a KOPS cluster. I want to use AWS's network load balancer so that it gets a static IP. When I create the Service with port 80 mapped to the port that the app is running on everything works but when I try to add port 443 it just times out. Here is the configuration that works - apiVersion: v1 metadata:

问题 I am learning about microk8s and how ingress works. I have a single node microk8s (v1.18.4) with the following add-ons: DNS, ingress, RBAC, storage I am trying to get it working with the microbot example. I've read (and reread) through the tutorial but, the address, once the ingress manifest is applied results with the microbot service, routed to 127.0.0.1 (and not the internal pod IP). I am attempting to access the app: http://192.168.91.166/microbot via web external to the vm that it's

问题 I am learning about microk8s and how ingress works. I have a single node microk8s (v1.18.4) with the following add-ons: DNS, ingress, RBAC, storage I am trying to get it working with the microbot example. I've read (and reread) through the tutorial but, the address, once the ingress manifest is applied results with the microbot service, routed to 127.0.0.1 (and not the internal pod IP). I am attempting to access the app: http://192.168.91.166/microbot via web external to the vm that it's

问题 I'm trying to redirect http://www... and https://www... to https://... using ingress-nginx. How can I do that? I've tried adding the following custom configuration using the annotation nginx.ingress.kubernetes.io/server-snippet and nginx.ingress.kubernetes.io/configuration-snippet : # 1 if($host = "www.example.com") { return 308 https://example.com$request_uri; } # 2 server { server_name www.example.com; return 308 https://example.com$request_uri; } # 3 server_name www.example.com; return 308

问题 I am using Helm kubernetes deployment and I want to run the postman test cases before a final deployment, and if any test case fails then rollback (or retain the current deployment like Blue-Green deployment). How to achieve this? 回答1: I achieved the expected behavior with Helm Chart Tests and the postman/newman Docker image. My Helm template for the test execution: apiVersion: v1 kind: Pod metadata: name: API Test annotations: "helm.sh/hook": test-success spec: containers: - name:

问题 I have a requirement for a multitenant application where each tenant should be separated by sub domains like below t1.example.com t2.example.com t3.example.com . . . tn.example.com So there could be any number of tenants in this case. I have a Kubernetes Backend Service named myservice responsible for handling all those requests and they need to be identified based on their subdomain. e.g. if the request comes from tn.example.com then it needs to be redirected to the -> myservice/tn . t2

问题 Need some serious help here ! Thanks in advance. I am trying to deploy a microservice based Java application. I am able to get to the frontend service(webapp) on my browser, but I am unable to connect it with the backend (auth service) and hence it shows authentication failure. HTML LOGIN FORM form points to "/login?referrerURL=" I checked the ingress nginx logs : Service "default/auth-srv" does not have any active Endpoint. Service "default/voice-srv" does not have any active Endpoint.