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 2022/08/08 09:53:00 UTC
[GitHub] [apisix-ingress-controller] wolgod opened a new issue, #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
wolgod opened a new issue, #1233:
URL: https://github.com/apache/apisix-ingress-controller/issues/1233
### Issue description
When I use ApisixV2beta3Client to create apisixUpstream
```
apisixUpstream := client.ApisixUpstreams(namespace)
_, err = apisixUpstream.Create(cont, ing, metav1.CreateOptions{})
```
The following error will be reported
```
ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream: unmarshalerDecoder: Object 'Kind' is missing in '{"metadata":{"name":"ttt-test1","namespace":"ns-2424","creationTimestamp":null},"spec":{"scheme":"grpc"},"status":{}}', error found in #10 byte of ...|tatus":{}}
|..., bigger context ...|stamp":null},"spec":{"scheme":"grpc"},"status":{}}
|...
```
除非我在构建apisixUpstream的显示指定typeMeta
```
au := apisixv2beta3.ApisixUpstreamConfig{
Scheme: SchemeGRPC,
}
typeMeta := metav1.TypeMeta{
Kind: "ApisixUpstream",
APIVersion: ApisixVersion,
}
apisixUpstream := &apisixv2beta3.ApisixUpstream{
TypeMeta: typeMeta,
ObjectMeta: metav1.ObjectMeta{
Name: entityService.RIngress.IngressName,
Namespace: namespace,
},
Spec: &apisixv2beta3.ApisixUpstreamSpec{
ApisixUpstreamConfig: au,
},
}
```
### Environment
- your apisix-ingress-controller version (output of apisix-ingress-controller version --long):1.4.1
- your Kubernetes cluster version (output of kubectl version):1.20
- if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):centos7.4
### Minimal test code / Steps to reproduce
When I use ApisixV2beta3Client to create apisixUpstream
```
apisixUpstream := client.ApisixUpstreams(namespace)
_, err = apisixUpstream.Create(cont, ing, metav1.CreateOptions{})
```
The following error will be reported
```
ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream: unmarshalerDecoder: Object 'Kind' is missing in '{"metadata":{"name":"ttt-test1","namespace":"ns-2424","creationTimestamp":null},"spec":{"scheme":"grpc"},"status":{}}', error found in #10 byte of ...|tatus":{}}
|..., bigger context ...|stamp":null},"spec":{"scheme":"grpc"},"status":{}}
|...
```
除非我在构建apisixUpstream的显示指定typeMeta
```
au := apisixv2beta3.ApisixUpstreamConfig{
Scheme: SchemeGRPC,
}
typeMeta := metav1.TypeMeta{
Kind: "ApisixUpstream",
APIVersion: ApisixVersion,
}
apisixUpstream := &apisixv2beta3.ApisixUpstream{
TypeMeta: typeMeta,
ObjectMeta: metav1.ObjectMeta{
Name: entityService.RIngress.IngressName,
Namespace: namespace,
},
Spec: &apisixv2beta3.ApisixUpstreamSpec{
ApisixUpstreamConfig: au,
},
}
```
### Actual result
不需要显示指定typeMeta
### Error log
ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream: unmarshalerDecoder: Object 'Kind' is missing in '{"metadata":{"name":"ttt-test1","namespace":"ns-2424","creationTimestamp":null},"spec":{"scheme":"grpc"},"status":{}}', error found in #10 byte of ...|tatus":{}}
|..., bigger context ...|stamp":null},"spec":{"scheme":"grpc"},"status":{}}
|...
### Expected result
_No response_
--
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.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-ingress-controller] github-actions[bot] commented on issue #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #1233:
URL: https://github.com/apache/apisix-ingress-controller/issues/1233#issuecomment-1316145075
This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions.
--
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 #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1233:
URL: https://github.com/apache/apisix-ingress-controller/issues/1233#issuecomment-1210075450
what's your CRD version?
--
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] wolgod commented on issue #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
Posted by GitBox <gi...@apache.org>.
wolgod commented on issue #1233:
URL: https://github.com/apache/apisix-ingress-controller/issues/1233#issuecomment-1212755730
> I mean, how did you install the CRD via Helm chart or some other way?
i use helm chart install
--
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] wolgod commented on issue #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
Posted by GitBox <gi...@apache.org>.
wolgod commented on issue #1233:
URL: https://github.com/apache/apisix-ingress-controller/issues/1233#issuecomment-1210192765
> what's your CRD version?
apisix.apache.org/v2beta3
--
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] github-actions[bot] closed issue #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
Posted by GitBox <gi...@apache.org>.
github-actions[bot] closed issue #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
URL: https://github.com/apache/apisix-ingress-controller/issues/1233
--
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 #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1233:
URL: https://github.com/apache/apisix-ingress-controller/issues/1233#issuecomment-1210198153
I mean, how did you install the CRD via Helm chart or some other way?
--
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] wolgod commented on issue #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
Posted by GitBox <gi...@apache.org>.
wolgod commented on issue #1233:
URL: https://github.com/apache/apisix-ingress-controller/issues/1233#issuecomment-1212754942
> I mean, how did you install the CRD via Helm chart or some other way?
helm chart
--
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] github-actions[bot] commented on issue #1233: bug: ApisixUpstream in version "v2beta3" cannot be handled as a ApisixUpstream
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #1233:
URL: https://github.com/apache/apisix-ingress-controller/issues/1233#issuecomment-1355926796
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.
--
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