kubernetes-ingress

问题 Ingress apiVersion: extensions/v1beta1 kind: Ingress metadata: name: assortment-ingress annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/rewrite-target: / spec: tls: - hosts: - myapp.centralus.cloudapp.azure.com secretName: aks-ingress-tls rules: - host: myapp.centralus.cloudapp.azure.com http: paths: - path: /my-service backend: serviceName: my-backend servicePort: 80 deployment & service apiVersion: apps/v1beta1 kind: Deployment metadata: name: my-deployment spec:

问题 I have a centos7 deployment with kubernetes on bare metal. Everything works great. However, i would like to get an Ingress working. so in brief what i want to do is to terminate the SSL from within the Ingress and have plain http between the ingress and my service. this is what i did: 1) i hack weave to allow hostNetwork 2) i have an ingress controller set up as per: apiVersion: extensions/v1beta1 kind: DaemonSet metadata: name: nginx-ingress-controller namespace: ingress-nginx labels: k8s

问题 I'm trying to create an Ingress resource that fans out to two services that are running healthily. This is my very simple config: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: my-ingress namespace: default spec: rules: - http: paths: - path: /* backend: serviceName: service1 servicePort: 8080 - path: /service2/* backend: serviceName: service2 servicePort: 9090 Only requests to the root ( / ) path seem to work. I've been trying to trouble shoot this using similar posts online,

问题 I have an EKS cluster. We want - One LB that will redirect to multiple namespace inside the cluster, - Ingress to avoid the "one load balancer for one service". I want to cut it by namespace. I have been reading a bit of documentation but I can't seem to wrap my head around it. I have this yaml, which I understood would create a LB and the ingress rules. apiVersion: extensions/v1beta1 kind: Ingress metadata: name: simple-fanout-example namespace : default annotations: kubernetes.io/ingress

问题 I've a Kubernetes cluster on GKE that has a nginx ingress controller sitting on top to mapping the RStudio Server endpoint under /rstudio/. This works quite well. Unfortunately, one of my deployments (RStudio Server) doensn't work properly because it uses client-side redirects during the login/logout which end ups in 404 error when trying to access /auth-login (it should be /rstudio/auth-login) In the past, when using a non-containerized install of RStudio Server, I used to sit an Apache

问题 Hello kubernetes experts, I've a kubernetes cluster running on 4 raspberry pis with docker 18.04ce and kubernetes 1.9.7. I deployed a service and this service can be accessed from within the cluster via the cluster IP. I also deployed an ingress as described in https://docs.traefik.io/user-guide/kubernetes/ and in How to get Kubernetes Ingress Port 80 working on baremetal single node cluster as a DaemonSet based on an ingress-controller-service. The DaemonSet also has NET_BIND_SERVICE set

问题 I'm trying to secure Nifi in a Kubernetes cluster, behind a Traefik proxy. Both are running as services in K8S. Traefik is secured with a public certificate. I want it to redirect calls to nifi, while securing the communication between Traefik (as an Ingress Controller) and the backend pods : Nifi. Looks like the secure confiuration should lire in my Ingress YAML descriptor. Looks like I should issue a CA root to generate Nifi self signed certificate and load this CA Root in Traefik so it can

问题 I've created a global static IP Address using terraform in GCP. However, when I try to assign it to an ingress controller inside a GKE cluster, it gets ignored: Here's my kubernetes configuration: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: homefully-ingress annotations: kubernetes.io/ingress.global-static-ip-name: "homefully-ingress-root" labels: app: homefully-ingress spec: # ... the IP address referenced here looks like this: NAME REGION ADDRESS STATUS homefully-ingress

问题 I have a kubernetes cluster on a private network(private server, not aws or google cloud) and I created a Service to be able to access, however, I need to be able to access from outside the cluster and for this I created an Ingress and added ingress-nginx in the cluster. This is the YAML I'm using after making several attempts: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: demo-ingress annotations: kubernetes.io/ingress.class: "nginx" nginx.ingress.kubernetes.io/ssl-redirect:

问题 I'm running through what looks like a configuration issue! I am using traefik as ingress controller within kubernetes and I have an ingress to route some URLs to route some frontends to various backends. Let's say I have something like this: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: test annotations: kubernetes.io/ingress.class: traefik traefik.frontend.rule.type: ReplacePathRegex spec: rules: - host: foo.io http: paths: - path: /api/authservice/(.*) /$1 backend: