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/06/20 15:15:02 UTC
[GitHub] [apisix-ingress-controller] caibirdme opened a new issue, #1091: bug: invalid ApisixUpstream kind
caibirdme opened a new issue, #1091:
URL: https://github.com/apache/apisix-ingress-controller/issues/1091
### Issue description
```yaml
# vector-upstream.yaml
apiVersion: apisix.apache.org/v1
kind: ApisixUpstream
metadata:
name: vector
spec:
scheme: grpc
```
kubectl apply -f vector-upstream.yaml -n vector
```
error: unable to recognize "vector-upstream.yaml": no matches for kind "ApisixUpstream" in version "apisix.apache.org/v1"
```
### 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.4
- if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a): centos7
### Minimal test code / Steps to reproduce
```yaml
# vector-upstream.yaml
apiVersion: apisix.apache.org/v1
kind: ApisixUpstream
metadata:
name: vector
spec:
scheme: grpc
```
kubectl apply -f vector-upstream.yaml -n vector
### Actual result
error: unable to recognize "vector-upstream.yaml": no matches for kind "ApisixUpstream" in version "apisix.apache.org/v1"
### Error log
error: unable to recognize "vector-upstream.yaml": no matches for kind "ApisixUpstream" in version "apisix.apache.org/v1"
### Expected result
xxx created
--
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] tao12345666333 commented on issue #1091: bug: invalid ApisixUpstream kind
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1091:
URL: https://github.com/apache/apisix-ingress-controller/issues/1091#issuecomment-1162687006
@caibirdme can we close this issue?
--
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] caibirdme commented on issue #1091: bug: invalid ApisixUpstream kind
Posted by GitBox <gi...@apache.org>.
caibirdme commented on issue #1091:
URL: https://github.com/apache/apisix-ingress-controller/issues/1091#issuecomment-1162699867
Yes
--
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 #1091: bug: invalid ApisixUpstream kind
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #1091:
URL: https://github.com/apache/apisix-ingress-controller/issues/1091#issuecomment-1161195112
@caibirdme By the way, could you try the `v2beta3` version of ApisixRoute? And use `backends` instead of `backend`.
--
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] caibirdme commented on issue #1091: bug: invalid ApisixUpstream kind
Posted by GitBox <gi...@apache.org>.
caibirdme commented on issue #1091:
URL: https://github.com/apache/apisix-ingress-controller/issues/1091#issuecomment-1161200758
> @caibirdme By the way, could you try the `v2beta3` version of ApisixRoute? And use `backends` instead of `backend`.
Ok, but I want to know how to delete the route I created before? Or do I need to do that?
--
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] caibirdme commented on issue #1091: bug: invalid ApisixUpstream kind
Posted by GitBox <gi...@apache.org>.
caibirdme commented on issue #1091:
URL: https://github.com/apache/apisix-ingress-controller/issues/1091#issuecomment-1160602371
After changing to v2beta3, I succed to create uptream, but it didn't work.
I want to proxy grpc and use plaintext(no tls):
This is my svc:
```
kubectl get svc -n vector
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
vector ClusterIP a.b.c.d <none> 9598/TCP,6788/TCP 6d8h
vector-headless ClusterIP None <none> 9598/TCP,6788/TCP 6d8h
```
This is my route.yaml
```yaml
apiVersion: "apisix.apache.org/v2beta1"
kind: ApisixRoute
metadata:
namespace: vector
name: otel-log-route
spec:
http:
- name: otel-log-ingester
match:
paths:
- "/opentelemetry.proto.collector.logs.v1.LogsService/Export"
hosts:
- camp.apisix.woa.com
backend:
serviceName: vector
servicePort: 6788
```
and this is upstream.yaml
```yaml
apiVersion: apisix.apache.org/v2beta3
kind: ApisixUpstream
metadata:
namespace: vector
name: vector
spec:
scheme: grpc
```
When I curl domain/opentelemetry.proto.collector.logs.v1.LogsService/Export, ingress-controller panic
```
panic: runtime error: index out of range [0] with length 0
goroutine 137 [running]:
github.com/apache/apisix-ingress-controller/pkg/kube/translation.(*translator).translateHTTPRouteV2beta3NotStrictly(0xc00031a2c0, 0xc000d97280, 0xc0007a22c0, 0x160, 0x1bf6b80)
/build/controller/pkg/kube/translation/apisix_route.go:648 +0xad5
github.com/apache/apisix-ingress-controller/pkg/kube/translation.(*translator).TranslateRouteV2beta3NotStrictly(0xc00031a2c0, 0xc0007a22c0, 0xc00061a1c0, 0x0, 0x0)
/build/controller/pkg/kube/translation/apisix_route.go:209 +0x85
github.com/apache/apisix-ingress-controller/pkg/ingress.(*Controller).CompareResources.func1.1(0xc0006169d0, 0xc000250000, 0x1fdcb10, 0xc00061a1c0, 0xc000908390, 0xc0009083c0, 0xc0009083f0, 0xc000908420, 0xc000908480, 0xc000908450, ...)
/build/controller/pkg/ingress/compare.go:78 +0x67a
created by github.com/apache/apisix-ingress-controller/pkg/ingress.(*Controller).CompareResources.func1
/build/controller/pkg/ingress/compare.go:68 +0x178
```
and the log from apisix deployment:
```
[20/Jun/2022:23:42:20 +0800] camp.apisix.woa.com:8081 "POST /opentelemetry.proto.collector.logs.v1.LogsService/Export HTTP/2.0" 404 36 0.000 "-" "grpc-go/1.47.0" - - - "http://camp.apisix.woa.com:8081"
```
--
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] caibirdme commented on issue #1091: bug: invalid ApisixUpstream kind
Posted by GitBox <gi...@apache.org>.
caibirdme commented on issue #1091:
URL: https://github.com/apache/apisix-ingress-controller/issues/1091#issuecomment-1161333623
when route change to v2beta3, it works
--
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 #1091: bug: invalid ApisixUpstream kind
Posted by GitBox <gi...@apache.org>.
tao12345666333 closed issue #1091: bug: invalid ApisixUpstream kind
URL: https://github.com/apache/apisix-ingress-controller/issues/1091
--
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 #1091: bug: invalid ApisixUpstream kind
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #1091:
URL: https://github.com/apache/apisix-ingress-controller/issues/1091#issuecomment-1161193683
It looks like a bug of APISIX Ingress Controller, cc @tao12345666333 .
--
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 #1091: bug: invalid ApisixUpstream kind
Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #1091:
URL: https://github.com/apache/apisix-ingress-controller/issues/1091#issuecomment-1161208575
v2beta1 has been removed in latest code. And for 1.4.1 version, it has been marked as deprecated.
You can just run
kubectl delete -f <your apisix route.yaml>
After change the apiversion to v
2beta3, then re-create it.
--
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