kubernetes-ingress

问题 I have a Kubernetes cluster(Azure) with nginx-ingress, certmanager and one application, and I was wondering if there's a way of making the whole system as one single package so if there's any problem with the cluster it'd be easier to spin up another one. My main idea is to make the manual configuration of nginx-ingress and certmanager automatic, but I'm not sure how it'd included in a helm chart, if possible. If not possible, is there a way(or tool) for minimising the manual configuration of

问题 I have Kubernetes setup on 3 nodes. 3 Kafka brokers are running successfully on the cluster. There is a third-party application outside the cluster that is using this Kafka. The third-party application(tool) can only use 1 broker list in its config. The tool is unable to add 3 broker list. All good, but sometimes tool got notleaderforpartitionexception . the tool is not able to switch on another broker. is it possible to add a proxy layer in Kubernetes which can give HA to the Kafka cluster?

问题 I'm trying to get letsencrypt/cert-manager running via this Helm chart. The K8s cluster is on Digital Ocean. I successfully verified the installation as recommended and have created a ClusterIssuer for staging, and 1 for production. ( letsencrypt-staging , letsencrypt-prod ) Problem: The acme challenge returns a 404 error. $ k get challenge -o wide NAME STATE DOMAIN REASON AGE myapp-cert-2315925673-2905389610-1118496475 pending myapp.example.com Waiting for http-01 challenge propagation:

问题 A backend service happens to be returning Status 404 on the health check path of the Load Balancer. When I browse to the Load Balancer's domain name, I get "Error: Server Error/ The server encountered a temporary error", and the logs show "type.googleapis.com/google.cloud.loadbalancing.type.LoadBalancerLogEntry" statusDetails: "failed_to_pick_backend" , which makes sense. When I browse to the Load Balancer's Static IP, my browser shows the 404 Error Message which the underlying Kubernetes Pod

问题 I create a ingress to expose my internal service. apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: app-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: / spec: rules: - host: example.com http: paths: - path: /app backend: serviceName: my-app servicePort: 80 But when I try to get this ingress, it show it has not ip address. NAME HOSTS ADDRESS PORTS AGE app-ingress example.com 80 10h The service show under below. apiVersion: v1 kind: Service metadata: name: my

问题 I am using the Istio sidecar injection. I have two namespaces in my cluster with istio-enabled. Below mentioned are two namespaces i.e bk and abhi. Also, I have a separate gateway for each namespace. The following is for bk namespace. I want to Access service by Ingress for bk namespace. bk.localhost.cluster Below is Gateway for bk namespace : apiVersion: networking.istio.io/v1alpha3 kind: Gateway metadata: name: abhijeet namespace: bk spec: selector: istio: ingressgateway servers: - hosts: -

问题 Im trying to limit the number of concurrent connection to servers in my Nginx ingress. is max_conns supported in Ngnix ingress? how can i edit or add it? max_conns=number limits the maximum number of simultaneous active connections to the proxied server (1.11.5). Default value is zero, meaning there is no limit. If the server group does not reside in the shared memory, the limitation works per each worker process. http://nginx.org/en/docs/http/ngx_http_upstream_module.html#upstream exmple of

问题 I want to increase size of post body of each request in Ingress. So I add the nginx.ingress.kubernetes.io/proxy-body-size: 8m in yaml file ingress(in view/edit yaml file of rancher) but it doesn’t work. When I get the describe of ingress with kubectl I dont see the added annotation but i see the new added mapping. Hereis the configs: YAML file: apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/configuration-snippet: |- set $test_host "testdms.test.com"

问题 I want to increase size of post body of each request in Ingress. So I add the nginx.ingress.kubernetes.io/proxy-body-size: 8m in yaml file ingress(in view/edit yaml file of rancher) but it doesn’t work. When I get the describe of ingress with kubectl I dont see the added annotation but i see the new added mapping. Hereis the configs: YAML file: apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: ingress.kubernetes.io/configuration-snippet: |- set $test_host "testdms.test.com"

问题 I'm currently porting a PHP monolith into Kubernetes, and I'm having some trouble with the URL rewriting in nginx-ingress . The system uses phroute and that's working all fine. The problem is setting up the nginx ingress to play nice. The old system had the following rewrite rules: try_files $uri $uri/ @rewrite; location @rewrite { rewrite ^/(.*)$ /index.php?_url=/$1; } location / { try_files $uri $uri/ =404; } location ~ \.php$ { try_files $uri =404; fastcgi_split_path_info ^(.+\.php)(/.+)$;