Open raravena80 opened 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.
v1.18.2
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:
kubectl version
kubectl version Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.5", GitCommit:"e6503f8d8f769ace2f338794c914a96fc335df0f", GitTreeState:"clean", BuildDate:"2020-07-04T15:01:15Z", GoVersion:"go1.14.4", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-30T20:19:45Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
kubeless version
kubeless version Kubeless version: v1.0.7
Server is running v1.0.5
v1.0.5
KinD (locally)
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
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.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
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:
Environment:
kubectl version
):kubeless version
):Server is running
v1.0.5
KinD (locally)