nginx-ingress

问题 I'm trying to set up a simple HTTP to HTTPS redirect for traffic going to a Kubernetes cluster. The SSL termination is happening on the ELB. When I try to use the nginx.ingress.kubernetes.io/ssl-redirect = true it results in an infinite redirect which led me to setting up a config map to handle this (nginx-ingress: Too many redirects when force-ssl is enabled). Now there seems to be no redirection happening at all. My ingress service is defined as: apiVersion: v1 kind: Service metadata:

问题 I'm trying to set up a simple HTTP to HTTPS redirect for traffic going to a Kubernetes cluster. The SSL termination is happening on the ELB. When I try to use the nginx.ingress.kubernetes.io/ssl-redirect = true it results in an infinite redirect which led me to setting up a config map to handle this (nginx-ingress: Too many redirects when force-ssl is enabled). Now there seems to be no redirection happening at all. My ingress service is defined as: apiVersion: v1 kind: Service metadata:

问题 Unable to install ingress-nginx for kubernetes on Docker desktop I was using the following in cmd line to install ingress nginx so far: $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml as shown in the web page: https://che.eclipse.org/running-eclipse-che-on-kubernetes-using-docker-desktop-for-mac-5d972ed511e1 I seems

问题 I have setup Custom Nginx ingress controller with Ingress resource in Kubernetes and instead of "default-http-backend service", I used custom application as the default backend service to be served for default requests. I have also used custom SSL which is set as kubernetes secret, for my service. The issue is that when I request the hostnames which are mentioned in the rules, the https redirection works. But when the requests other than the hosts mentioned in the rules are made, it serves

问题 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 want to setup a k8s cluster, but I despair with the nginx-ingress controller and some special settings I need to set: especially proxy_pass. I tried to achieve that already with the "server-snippet"-snippet, but it didn't work. apiVersion: networking.k8s.io/v1beta1 # for versions before 1.14 use extensions/v1beta1 kind: Ingress metadata: name: ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 nginx.ingress.kubernetes.io/affinity: "cookie" nginx.ingress.kubernetes.io

问题 I have kubernetes Cluster v1.10 over centos 7 , bare-metal helm version Client: &version.Version{SemVer:"v2.11.0-rc.3", GitCommit:"28d295be2a94115b786ee277dffcc2b5483bde47", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.11.0-rc.3", GitCommit:"28d295be2a94115b786ee277dffcc2b5483bde47", GitTreeState:"clean"} I am trying to install nginx using helm helm install stable/nginx-ingress --name nginx It returns Error: release nginx failed: clusterroles.rbac.authorization.k8s.io "nginx

问题 Environment: Ubuntu 18.06 bare metal, set up the cluster with kubeadm (single node) I want to access the cluster via port 80. Currently I am able to access it via the nodePort: domain.com:31668/ but not via port 80. I am using metallb Do I need something else to handle incoming traffic? So the current topology would be: LoadBalancer > Ingress Controller > Ingress > Service kubectl -n ingress-nginx describe service/ingress-nginx: Name: ingress-nginx Namespace: ingress-nginx Labels: app

问题 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