Failed to create ingress rule get-python corresponding to http trigger Obj

[wirelessr]

Is this a BUG REPORT or FEATURE REQUEST?: BUG

What happened: I followed the SOP to create the HTTP trigger; however, the Ingress cannot be created successfully. The log is as follows:

$ kubectl logs -n kubeless -l kubeless=controller -c http-trigger-controller 
time="2021-01-05T08:43:37Z" level=info msg="Processing update to HTTPTrigger: default/get-python" controller=http-trigger-controller
time="2021-01-05T08:43:37Z" level=info msg="Processing update to HTTPTrigger: default/get-python" controller=http-trigger-controller
time="2021-01-05T08:43:37Z" level=info msg="Adding ingress resource for http trigger Obj: default/get-python " controller=http-trigger-controller
time="2021-01-05T08:43:37Z" level=error msg="Failed to create ingress rule get-python corresponding to http trigger Obj: default/get-python due to: Unable to find the function internal service: &Service{ObjectMeta:k8s_io_apimachinery_pkg_apis_meta_v1.ObjectMeta{Name:get-python,GenerateName:,Namespace:default,SelfLink:/api/v1/namespaces/default/services/get-python,UID:2e51b57a-e1d2-40bc-90b4-d6000c46f1a3,ResourceVersion:1555,Generation:0,CreationTimestamp:2021-01-05 08:43:13 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{created-by: kubeless,function: get-python,},Annotations:map[string]string{},OwnerReferences:[{kubeless.io/v1beta1 Function get-python f8622c76-5838-4f99-b6cb-d98abbd3e1e8 <nil> <nil>}],Finalizers:[],ClusterName:,Initializers:nil,},Spec:ServiceSpec{Ports:[],Selector:map[string]string{},ClusterIP:,Type:,ExternalIPs:[],SessionAffinity:,LoadBalancerIP:,LoadBalancerSourceRanges:[],ExternalName:,ExternalTrafficPolicy:,HealthCheckNodePort:0,PublishNotReadyAddresses:false,SessionAffinityConfig:nil,},Status:ServiceStatus{LoadBalancer:LoadBalancerStatus{Ingress:[],},},}: " controller=http-trigger-controller

What you expected to happen: I believe if everything is fine, I can see the result in kubectl get ing

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

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:43:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

• Kubeless version (use kubeless version): v1.0.7
• Cloud provider or physical cluster: minikube v1.16.0 and minikube start --kubernetes-version='v1.18.3' --vm=true

[andresmgot]

Yes, this is a known issue. Triggers don't work with Kubernetes +1.18 (https://github.com/kubeless/kubeless/issues/1130)

[andresmgot]

Closing this as a duplicate, you can add more comments in that issue.