vmware-archive / kafka-trigger

Kubernetes CRD controller for Kafka topic as event source for Kubeless functions
Apache License 2.0
28 stars 34 forks source link

Unable to elaborate request: Unable to find the service for function "function-name" #30

Open raravena80 opened 4 years ago

raravena80 commented 4 years ago

Is this a BUG REPORT or FEATURE REQUEST?:

But

What happened:

Getting the following with K8s v1.18.2 when trying to trigger a function.

time="2020-07-14T22:00:15Z" level=error msg="Unable to elaborate request: Unable to find the service for function my-handler"

My guess is that it can't find the service because there is an API version mismatch.

The service is there in the cluster on the same namespace as the controller

kubectl get svc my-handler
NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
my-handler   ClusterIP   10.105.218.61   <none>        8080/TCP   50m

What you expected to happen:

The function should be trigger by publishing a message to a Kafka topic

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Pods running in KinD:

 kubectl get pods
NAME                                          READY   STATUS    RESTARTS   AGE
hello-5c8f5f47cc-fnkl4                        1/1     Running   0          45m
kafka-0                                       1/1     Running   3          67m
kafka-trigger-controller-f6f7c699f-g8jm6      1/1     Running   0          16m
kubeless-controller-manager-cdd969c6d-hmx5q   3/3     Running   0          46m
my-handler-d5dd7744-qn8br                     1/1     Running   0          45m
test1-5bfd86df-68gnn                          1/1     Running   0          38m
zoo-0

Environment:

kubeless version
Kubeless version: v1.0.7

Server is running v1.0.5

KinD (locally)

andresmgot commented 4 years ago

Hi @raravena80. Indeed this is a known issue. Kubeless is not compatible with Kubernetes 1.18 at the moment. See more info here: https://github.com/kubeless/kubeless/issues/1130