kubernetes-ingress

问题 I am trying to make the websocket service work on Azure Kubernetes Cluster on our organization environment. My existing environment also have REST api and Angular application working on ingress with ssl. But when I added the websocket service on the ingress it is not working. So, I tried to use Azure Free Subscription to first implement the same WITHOUT SSL. For my applications I enabled Http Routing and using the annotation addon-http-application-routing. I am getting below error. 'ws://40

问题 I am trying to make the websocket service work on Azure Kubernetes Cluster on our organization environment. My existing environment also have REST api and Angular application working on ingress with ssl. But when I added the websocket service on the ingress it is not working. So, I tried to use Azure Free Subscription to first implement the same WITHOUT SSL. For my applications I enabled Http Routing and using the annotation addon-http-application-routing. I am getting below error. 'ws://40

问题 I am trying to make the websocket service work on Azure Kubernetes Cluster on our organization environment. My existing environment also have REST api and Angular application working on ingress with ssl. But when I added the websocket service on the ingress it is not working. So, I tried to use Azure Free Subscription to first implement the same WITHOUT SSL. For my applications I enabled Http Routing and using the annotation addon-http-application-routing. I am getting below error. 'ws://40

问题 I would like to be able to disable external authorization for a specific path of my App. Similiar to this SO: Kubernetes NGINX Ingress: Disable Basic Auth for specific path Only difference is using an external Auth provider (OAuth via Microsoft Azure) and there is a This is the path that should be reachable by the public /MyPublicPath My ingress.yaml: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: myIngressName annotations: nginx.ingress.kubernetes.io/auth-signin: https:/

问题 I have installed the following two different ingress controllers on my DigitalOcean managed K8S cluster: Nginx Istio and they have been assigned to two different IP addresses. My question is, if it is wrong to have two different ingress controllers on the same K8S cluster? The reason, why I have done it, because nginx is for tools like harbor, argocd, etc. and istio for microservices. I have also figured out, when both are installed alongside each other, sometimes during the deployment, the

问题 I have Kubernetes Cluster with Ingress/Traefik controller Also, I installed the dashboard using the standard config from here: https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml I'm trying to access the Dashboard through Ingress, but I get 404 error 404 page not found My ingress.yml file looks like this apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: kubernetes.io/ingress.class: "traefik" name: app-ingress-system

问题 I have the following that config that works when I try <NodeIP>:30080 apiVersion: extensions/v1beta1 kind: Deployment metadata: name: app-deployment spec: replicas: 3 template: metadata: labels: name: app-node spec: containers: - name: app image: myregistry.net/repo/app:latest imagePullPolicy: Always ports: - containerPort: 8080 env: - name: NODE_ENV value: production --- apiVersion: v1 kind: Service metadata: name: app-service spec: selector: name: app-node ports: - protocol: TCP port: 80

问题 I have an EC2 instance that I use for personal work & projects with very small amounts of traffic (portfolio, etc). I thought it'd be really cool (although obviously overkill) to set up a dev cluster running my various projects using Minikube and to connect a domain name to this instance. Setup I have an Ingress controller that points to my service, with an IP address that is different than the host machine. I think it's somehow the IP address of the VM, but only accessible from the host

问题 I set up a k8s cluster using kubeadm (v1.18) on an Ubuntu virtual machine. Now I need to add an Ingress Controller. I decided for nginx (but I'm open for other solutions). I installed it according to the docs, section "bare-metal": kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-0.31.1/deploy/static/provider/baremetal/deploy.yaml The installation seems fine to me: kubectl get all -n ingress-nginx NAME READY STATUS RESTARTS AGE pod/ingress-nginx-admission

问题 I'm having trouble setting up an ingress open only to some specific IPs, checked docs, tried a lot of stuff and an IP out of the source keep accessing. that's a Zabbix web interface on an alpine with nginx, set up a service on node-port 80 then used an ingress to set up a loadbalancer on GCP, it's all working, the web interface is working fine, but how can I make it accessible only to desired IPs? my firewall rules are ok and it's only accessible through load balancer IP Also, I have a