You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/09/07 09:59:24 UTC
[GitHub] [apisix-ingress-controller] suninuni opened a new issue #672: request help: get deprecated warning after upgrade to 1.2.0
suninuni opened a new issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672
### Issue description
```shell
kubectl get apisixroute -n kube-system
Warning: apisix.apache.org/v1 ApisixRoute is deprecated
NAME HOSTS URIS TARGET SERVICE INGRESS SERVER PORT TARGET SERVICE AGE
apisix-dashboard ["staging-apisix.quncrm.com"] ["/*"]
```
Is that mean the stored version is v1? But the stored version is v2beta1 in crd.
```shell
kubectl get crd apisixroutes.apisix.apache.org -o jsonpath='{.spec.versions[*].name }' -A
v1 v2alpha1 v2beta1%
kubectl get crd apisixroutes.apisix.apache.org -o jsonpath='{.spec.versions[*].storage }' -A
false false true%
```
How can I eliminated this warning and show v2beta1 when edit by kubectl?
### Environment
* your apisix-ingress-controller version (output of `apisix-ingress-controller version --long`); 1.2.0
* your Kubernetes cluster version (output of `kubectl version`); 1.21.0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 edited a comment on issue #672: request help: get deprecated warning after upgrade to 1.2.0
Posted by GitBox <gi...@apache.org>.
tao12345666333 edited a comment on issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672#issuecomment-915690808
We plan to release the v2 version of the API in the last two versions (about 2 months).
I will initiate a discussion on the mailing list and GitHub in a while, and I will update the link here later.
update: #707
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #672: request help: get deprecated warning after upgrade to 1.2.0
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672#issuecomment-915139484
> To handled what？I don't feel any difference between v2alpha1 and v2beta1. Actually in version 1.1.0, when I set kubernetes.apisix_route_version as apisix.apache.org/v2alpha1, I can't create route throw v2beta1. But after upgraded to 1.2.0, they all work well. And I find the reason in changelog.
`v2beta1` has some broken changes from `v1alpha1`, for instance, the `tcp` field was changed to `stream`.
As for the `v1` version, this is decided by Kubernetes API design, as `v1` is a stable version (it's a mistake to use `v1` when we designed it in the past) while `v2alpha1` and `v2beta1` are not.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #672: request help: get deprecated warning after upgrade to 1.2.0
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672#issuecomment-973047308
In version 1.3, we have adjusted the configuration of CRD resources, and you will no longer see this information.
I will close this issue. Feel free to reopen it, if you have any question.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] suninuni commented on issue #672: request help: get deprecated warning after upgrade to 1.2.0
Posted by GitBox <gi...@apache.org>.
suninuni commented on issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672#issuecomment-914168730
Another question, what is the meaning of `kubernetes.apisix_route_version` in config.yaml? I set it to `apisix.apache.org/v2beta1`, but I still can create route by v2alpha1 and v2beta1.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #672: request help: get deprecated warning after upgrade to 1.2.0
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672#issuecomment-915690808
We plan to release the v2 version of the API in the last two versions (about 2 months).
I will initiate a discussion on the mailing list and GitHub in a while, and I will update the link here later.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tao12345666333 closed issue #672: request help: get deprecated warning after upgrade to 1.2.0
Posted by GitBox <gi...@apache.org>.
tao12345666333 closed issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] tokers commented on issue #672: request help: get deprecated warning after upgrade to 1.2.0
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672#issuecomment-914319542
> kubernetes.apisix_route_version
It means which version of `ApisixRoute` resources will be watched and handled by APISIX Ingress Controller? It doesn't prevent you from creating these objects.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] suninuni commented on issue #672: request help: get deprecated warning after upgrade to 1.2.0
Posted by GitBox <gi...@apache.org>.
suninuni commented on issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672#issuecomment-914775043
> > kubernetes.apisix_route_version
>
> It means which version of `ApisixRoute` resources will be watched and handled by APISIX Ingress Controller? It doesn't prevent you from creating these objects.
To handled what？I don't feel any difference between v2alpha1 and v2beta1. Actually in version 1.1.0, when I set `kubernetes.apisix_route_version` as `apisix.apache.org/v2alpha1`, I can't create route throw v2beta1. But after upgraded to 1.2.0, they all work well. And I find the reason in changelog.
[`f78248a`](https://github.com/apache/apisix-ingress-controller/commit/f78248a6aca0ac4754fd4d5d410c28f1cdd3d9c7) fix: sync apisix failed when use v2beta1 ApisixRoute (#620)
Maybe the reason is they all stored as v1?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] suninuni commented on issue #672: request help: get deprecated warning after upgrade to 1.2.0
Posted by GitBox <gi...@apache.org>.
suninuni commented on issue #672:
URL: https://github.com/apache/apisix-ingress-controller/issues/672#issuecomment-915680655
> As for the v1 version, this is decided by Kubernetes API design, as v1 is a stable version (it's a mistake to use v1 when we designed it in the past) while v2alpha1 and v2beta1 are not.
So this problem will still exist until the v2 version is released？In this way, I can only temporarily modify crd and delete deprecated field.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org