apisix-helm-chart
apisix-helm-chart copied to clipboard
Question: What is introduced by '2.x' helm chart ? Why the document are not mentioning anything about it ?
Hi Guys :vulcan_salute:
I'm a little lost about your chart versioning. Based on https://github.com/apache/apisix-helm-chart#compatibility-matrix, you seem supporting two helm chart versions
Chart v0.xChart v1.x
But I see another one from releases which is Chart v2.x and it have the same apisix, dashboard and ingress controller version than Chart v1.x
| APISIX | APISIX Ingress | APISIX Dashboard | |
|---|---|---|---|
| Chart v1.x | v3.x | v1.x | v3.x |
| Chart v2.x | v3.x | v1.x | v3.x |
So, I have some question for you :
- Why do you have another major chart version ?
- What is introduced in
Chart v2.x? - Could you generate chart changelog with new release ? It would be really helpful !
This isn't very clear indeed. The chart v2 is in the dev branch. Some features are supported in v1, and some are supported in v2. When installing the helm chart, the v2 chart is installed by default. From my regular user perspective it seems like v2 is newer, but then there are some weird dependencies:
- chart v1 uses ingress-apisix-controller chart 0.12.2
- chart v2 uses ingress-apisix-controller chart 0.11.4
I think v2 also had some pretty hefty config changes, we were running 1.x, I had to make a few changes to get to version 2.1.
If you are trying to upgrade, i would run a helm template and compare the rendered versions to your current production version, and make adjustments or choices from there.
I hadn't realized v2 was a dev branch @indrekj! They really should have made that more clear.
@AlinsRan Could you help answer this?
There are break changes in 2.x, so the dev branch has been introduced. In the future, when dev is merged into the master, we will only maintain apisix 2.x
Their main differences are as follows:
- The dev branch only maintains the apisix
2.xpackage. - The master branch maintains all packages, including apisix
1.x, apisix-ingress-controller0.x, etc.
@AlinsRan In order for more people to know this difference, should we pin this issue or add the difference to README?
@zll600 I think the latter is more suitable.