Comments (11)
The project supports controller with v1.25 and also another series with v1.21
from ingress-nginx.
The project supports controller with v1.25 and also another series with v1.21
Thank you for your response. I would like to know if there are any documents or records indicating that starting from v1.10.0, the project plans to support multiple Nginx versions. This information would be greatly helpful for understanding the new direction and adjusting our internal processes accordingly.
from ingress-nginx.
Its implied because project will support v1.9.x
from ingress-nginx.
Its implied because project will support v1.9.x
Just to clarify, do you mean that even after the release of v1.10.0, there will still be a v1.19.7 released that is based on Nginx 1.21.x? I'm trying to understand the versioning strategy and how these parallel releases align with each other.
from ingress-nginx.
Its driver by absolute practical requirement first.
And then the circumstances and feedback influence decisions.
For example all users can not be forced to move to v1.10.x so a future fix may well result into a v1.9.7.
For example, once a v1.11.X is out, the project will have option to evaluate stopping support for v1.9.X .
The already published bits will continue to be available for download though (just to state the obvious).
Relevance being your proposal could be feasible in future after v1.11 or v1.12 is out. (if it improves the project for tons of users)
from ingress-nginx.
Thank you for your explanation. While I understand the release strategy, I believe it might be more logical to maintain the same directory structure and use branches release-1.9 and release-1.10 to track the releases of different versions separately. This approach could potentially simplify the project structure and make it easier for users to follow and integrate with their existing workflows.
from ingress-nginx.
/assign @rikatz
I agree this should be cleaned up. We can bump it directly on the 1.9 branch if we need to rebuild nginx.
from ingress-nginx.
/priority backlog
/triage accepted
from ingress-nginx.
@strongjz Thank you for accepting the proposal. If it's possible, I would be glad to take the cleanup work.
from ingress-nginx.
While we support both 1.9 and 1.10, which use 1.21 and 1.25, we need to keep both directories for the time being. It will be cleaned up in the future.
/close
from ingress-nginx.
@strongjz: Closing this issue.
In response to this:
While we support both 1.9 and 1.10, which use 1.21 and 1.25, we need to keep both directories for the time being. It will be cleaned up in the future.
/close
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.
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 4
- 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 5
- 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 13
- 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.