APISIX 3.x.x has changed the Admin API. To make APISIX Ingress compatible with these changes, you need to select the corresponding chart version. Please refer 1.5 to 1.6.
- CRD has been upgraded to the V2 version, and V2beta3 has been marked as deprecated.
app_namespaceis deprecated. you can use
- CRD unified upgrade to V2beta3, delete resource v2alpha1 and v1 versions
Before upgrading APISIX Ingress, you need to update the corresponding CRD resource first, k8s will automatically replace it with the default CRD resource version, incompatible items will be discarded, and its configuration needs to be updated to the current version.
It is recommended not to upgrade across versions.
- Update Helm repo
Before upgrading, you need to update the helm repo to ensure that the resources in the repo are up to date.
helm repo update
- Upgrade CRDs
When the CRD exists, Helm Chart will not automatically update the CRD when upgrading or installing, so you need to update the CRD resource yourself
- Using Helm (Helm version >= 3.7.0)
helm show crds apisix/apisix-ingress-controller | kubectl apply -f -
If the Helm version does not support it, you need to obtain it from the apisix-helm-chart repository. CRDs directory:
kubectl apply -f https://raw.githubusercontent.com/apache/apisix-helm-chart/apisix-1.1.0/charts/apisix-ingress-controller/crds/customresourcedefinitions.yaml
- Upgrade APISIX Ingress
Just as an example, the specific configuration needs to be modified by yourself. If you want to upgrade to a specific chart version, please add this flag
--version x.x.x, Please refer compatible-upgrade or incompatible-upgrade.
helm upgrade apisix apisix/apisix \
--set gateway.type=NodePort \
--set ingress-controller.enabled=true \
--namespace ingress-apisix \
Compatible upgrades can be made without changing any resources.
If you use the
apisix-ingress-controller chart, you need to focus on the configuration item adminAPIVersion.
You need to select the corresponding chart version according to the APISIX version as shown to install or upgrade:
|Chart version||APISIX version||Values|
apisix chart to upgrade:
helm upgrade apisix apisix/apisix --version 1.1.0 *** # omit some configuration
apisix-ingress-controller chart to upgrade:
helm upgrade apisix apisix/apisix-ingress-controller \
--version 0.11.3 \
--set config.apisix.adminAPIVersion=v3 # omit some configuration
The chart version corresponding to
helm upgrade apisix apisix/apisix --version 0.11.3 *** # omit some configuration
The chart version corresponding to
helm upgrade apisix apisix/apisix --version 0.10.2 *** # omit some configuration
Incompatible upgrade, need to change resources.
object(http.backend) has been removed in V2beta3 and needs to be converted to
array(http.backends). It is recommended not to upgrade across major versions.
Apache APISIX Ingress project is a continuously actively developed project. In order to make it better, some broken changes will be added when the new version is released. For users, how to upgrade safely becomes very important.
The policy directory of this project contains these compatibility check strategies,
you can use the
conftest tool to check the compatibility.
Here's a quick example.
- name: rule1
- serviceName: httpbin
It uses the
spec.http.backend field that has been removed.
Save as httpbin-route.yaml.
Use conftest for compatibility check.
$ conftest test httpbin-route.yaml
FAIL - httpbin-route.yaml - main - ApisixRoute/httpbin-route: rule1 field http.backend has been removed, use http.backends instead.
2 tests, 1 passed, 0 warnings, 1 failure, 0 exceptions
Incompatible parts will generate errors.