Comments (7)
This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from ingress-nginx.
not tested or supported. check the https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/ information
from ingress-nginx.
not tested or supported. check the https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/ information
Ok but it is a simple redirect in my opinion.
My ingress address is : https://app1.kube-dev.example.com/
My Haproxy/F5 adress is : https://app1-dev.example.com/
So when user enter in web browser https://app1-dev.example.com/ shoud be redirected thru haproxy/f5 to address
https://app1.kube-dev.example.com/ and be able to see application page but we got 503.
from ingress-nginx.
from ingress-nginx.
Are you using this project ingress-nginx controller for the redirects or F5 nginx controller?
@longwuyuan can you follow up with a close if this is not needed
/triage needs-information
from ingress-nginx.
Are you using this project ingress-nginx controller for the redirects or F5 nginx controller?
@longwuyuan can you follow up with a close if this is not needed
/triage needs-information
I have a Tanzu Cluster and installed Nginx Ingress Controller on it. F5 or Haproxy are external.
The trafic look like:
User-> Address on F5/Haproxy -> Ingress Address from Nginx Controller.-> Service - > App in Pod
After few experiments I was able to run this with haproxy ingress controller and I think the problem is with ports which are used in service and haproxy configuration:
http Listening port is 80 and Target is 8080
https Listening port 443 and Target port is 8443
Haproxy backend is set to port 443.
I don't tell anything about rest of the setup.
Configuration:
Tanzu Kubernetes Cluster - TKGs with NSX Load Balancer.
EDIT:
Additional info which can help:
I'm using Nginx with specific IP for exampler 10.1.1.10 and when try to rewrite address
https://app1.kube-dev.example.com to https://app1-dev.example.com it always point me to page which is displayed by kubernetes internal proxy : https:ingress-nginx-controller:443/proxy/
So I think I need some rule or DNS entry. I use wildcard certificate kube-dev.example.com pointing IP. 10.1.1.10 maybe this is a problem.
from ingress-nginx.
Can you put in a rewrite or a redirect at the haproxy level?
from ingress-nginx.
Related Issues (20)
- CVE-2023-44487 - is the patch for this CVE included in controller-v1.8.4 HOT 4
- no tcp: {} option - instead spec.listeners{} in the last helm chart values HOT 3
- service/ingress-nginx-controller annotation HOT 7
- Controller failed to renew lease (leader election) due to timeout until pod restart HOT 6
- Modsecurity log dosent use $request_id from nginx when modsec blocks (403) HOT 16
- registry.k8s.io/ingress-nginx/controller:v1.10.0 has no s390x arch in the image manifest HOT 3
- helm-chart 4.10.1 seems to be missing in the repo despite being recommended in the `README.md` HOT 5
- 400 Bad Request is getting changed to 500 Internal Server Error while using custom nginx error HOT 4
- Add ppc64le support for registry.k8s.io/ingress-nginx/controller HOT 3
- certificate resource has no owner. refusing to update non-owned certificate resource for object HOT 3
- ACME challenge fails with `nginx.ingress.kubernetes.io/permanent-redirect` HOT 12
- Annotation whitelist-source-range not using client real IP HOT 8
- geoip2 enabling causes crash of controller v1.10 HOT 17
- Custom error_page redirects not working HOT 1
- The ingress-nginx controller crashes due to `unknown directive "alias"` when using global snippets. HOT 5
- Custom error_page redirects not working HOT 3
- Not able to install ingress-nginx helm chart in private AKS clusters HOT 6
- Ingress Test Fails to Route Traffic to a Deployment in Browser HOT 3
- Removing NET_BIND_SERVICE cap from ingres-nginx as part of nonroot, ingress pod in crashlooopbackoff HOT 3
- 499 reflect on service HOT 14
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ingress-nginx.