kubeless
kubeless copied to clipboard
Status Not Ready weather example
Is this a BUG REPORT or FEATURE REQUEST?: BUG
What happened:
NAME NAMESPACE HANDLER RUNTIME DEPENDENCIES STATUS
weather kubeless test.weather nodejs12 request: ^2.88.0 0/1 NOT READY
request-promise-native: ^1.0.8
I'm following the example provided below but am getting a status not ready when deploying the function. https://github.com/kubeless/functions/tree/master/incubator/weather
I also visited this comment and applied it but am still getting status not ready https://github.com/kubeless/kubeless/issues/861#issuecomment-408779664
What you expected to happen:
NAME NAMESPACE HANDLER RUNTIME DEPENDENCIES STATUS
weather kubeless test.weather nodejs12 request: ^2.88.0 1/1 READY
request-promise-native: ^1.0.8
I'm also seeing this issue with the serverless-kubeless plugin when packaging functions with dependencies.
How to reproduce it (as minimally and precisely as possible): Run the weather example
Anything else we need to know?: Using kubeless with minikube and context virtual box.
Environment:
- Kubernetes version (use
kubectl version
):
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.8", GitCommit:"211047e9a1922595eaa3a1127ed365e9299a6c23", GitTreeState:"clean", BuildDate:"2019-10-15T12:11:03Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-07T21:12:17Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}
-
Kubeless version (use
kubeless version
): v1.0.5-dirty -
Cloud provider or physical cluster: local cluster using minikube and virtualbox
Hi @randyyaj,
Maybe the code of the function has become obsolete. Can you check the function YAML and logs? There you should be able to find more info of what's going wrong. More information about how to debug Kubeless functions can be found here:
https://kubeless.io/docs/debug-functions/
Let me know if you are able to find the source of the error.