Error in kubeless installation

Hello
I am tryng to install Kubeless on Kubernetes.  When I ran kubectl get pods -n kubeless , I gove this output:
NAME                                  READY     STATUS    RESTARTS   AGE
kafka-0                               0/1       Pending   0          7m
kubeless-controller-b54bc9db6-fl276   0/1       Pending   0          7m
zoo-0                                 0/1       Pending   0          7m

I waited some minutes and ran it again but status won't change.
How can I fixed it and install Kubeless?

@meysam001 could you please use Kubernetes troubleshooting guidline to figure why pods are stuck in pending state.

@murali-reddy what part of that exactly I run? it seems that everything is ok.
I installed Kubernetes 1.9 with Weave Net for pod network. output of kubectl get pods -n kube-system -o wide is:
NAME                          READY     STATUS    RESTARTS   AGE       IP                NODE
etcd-srv                      1/1       Running   0          29m       <IP_ADDRESS>   srv
kube-apiserver-srv            1/1       Running   0          29m       <IP_ADDRESS>   srv
kube-controller-manager-srv   1/1       Running   0          29m       <IP_ADDRESS>   srv
kube-dns-6f4fd4bdf-g6l6s      3/3       Running   0          29m       <IP_ADDRESS>         srv
kube-proxy-jwncf              1/1       Running   0          29m       <IP_ADDRESS>   srv
kube-scheduler-srv            1/1       Running   0          29m       <IP_ADDRESS>   srv
weave-net-wg6wc               2/2       Running   0          17m       <IP_ADDRESS>   srv

Please try kubectl describe  pod kubeless-controller-b54bc9db6-fl276 -n kubeless

Name:           kubeless-controller-b54bc9db6-8l874
Namespace:      kubeless
Node:           <none>
Labels:         kubeless=controller
                pod-template-hash=610675862
Annotations:    <none>
Status:         Pending
IP:
Controlled By:  ReplicaSet/kubeless-controller-b54bc9db6
Containers:
  kubeless-controller:
    Image:  bitnami/kubeless-controller@sha256:939d64b5a50c36036738530d29af678752236e412d06c5eda1831be1a5b588e4
    Port:   <none>
    Environment:
      KUBELESS_INGRESS_ENABLED:  <set to the key 'ingress-enabled' of config map 'kubeless-config'>  Optional: false
      KUBELESS_SERVICE_TYPE:     <set to the key 'service-type' of config map 'kubeless-config'>     Optional: false
      KUBELESS_NAMESPACE:        kubeless (v1:metadata.namespace)
      KUBELESS_CONFIG:           kubeless-config
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from controller-acct-token-cb6tc (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  controller-acct-token-cb6tc:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  controller-acct-token-cb6tc
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason            Age               From               Message
  ----     ------            ----              ----               -------
  Warning  FailedScheduling  1s (x18 over 4m)  default-scheduler  0/1 nodes are available: 1 PodToleratesNodeTaints.

(The name had changed because I reinstalled it.)

Warning  FailedScheduling  1s (x18 over 4m)  default-scheduler  0/1 nodes are available: 1 PodToleratesNodeTaints.

Your node is not ready for some reason or pod can not be scheduled. Please check.

@murali-reddy
How can I check it?
The Kubernetes document said when pod stays waiting:

There should be messages from the scheduler about why it can not schedule your pod. Reasons include:

You don’t have enough resources....
You are using hostPort........

I checked both of them and There are no problem.

Can you try to start a simple pod, do:
kubectl run nginx --image=nginx

Then run kubectl get pods and see if the nginx pod gets running. If it stays pending then the problem is not kubeless specific and you need to figure out why your pods don't get scheduled. From the kubectl describe you ran above it seems that you have some taint on your nodes and the Pods would need to have a toleration.

My guess,  its only only node running in the cluster and master may be tainted with NoSchedule

I tried to start  nginx , it stayed pending  like kubeless.
I have only a master node and it has 4 GB of RAM and 2 core of CPU. Does it have enough resource?
I will reinstall OS in server and will try to do everything first.

So it is not a kubeless problem since you cannot start a regular nginx container with kubectl run.
Check out taint and tolerations here https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
My guess is that you have an existing taint on your master. You need to remove that taint.
Just as a tip I would do kubectl edit nodes <nodename> and remove the taint section from the yaml, then the pods should schedule.

I rebuilded  everything on my server and could install it finally.
I created a function that was in example and it work well:
kubeless function deploy test --runtime python2.7 \
                                --handler test.foobar \
                                --from-file test.py \
                                --trigger-topic test-topic

kubeless function call get-python --data '{"echo": "echo echo"}'
# result: {"echo": "echo echo"}

But when I ran kubectl get pods -n kubeless , I got this output:
NAME                                  READY     STATUS     RESTARTS   AGE
kafka-0                               0/1       Init:0/1   0          1h
kubeless-controller-b54bc9db6-66zq5   1/1       Running    4          1h
zoo-0                                 0/1       Init:0/1   0          1h

Is Kubeless installed well ? Is there any wrong?

@meysam001 please see https://github.com/kubeless/kubeless/issues/614 also see the requirements for using pubsub functionality http://kubeless.io/docs/quick-start/

@murali-reddy ok. So I close this issue and I will follow that issue


Keyboard shortcut and navigation buttons stop working after accepting whole URL

After accepting URL, keyboard shortcut [ and ] and navigation button >, < stops working. There are no fast way to go to next URL.

Hi rogemus,
Thanks for posting, the issue has been already fixed in version 2.1.0.
Thanks!


[Windows][melodic] Fix install destination path

Follow the catkin guide to place output binaries correctly for cross-platform:

Place shared libraries like: http://docs.ros.org/api/catkin/html/howto/format2/building_libraries.html

install(TARGETS your_library your_other_library
        ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
        LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION}
        RUNTIME DESTINATION ${CATKIN_GLOBAL_BIN_DESTINATION})

Place executables like: http://docs.ros.org/api/catkin/html/howto/format2/building_executables.html

install(TARGETS your_node
        RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION})

@rhaschke JFYI, I has sent out the diff that we made in RViz side for Windows bring up. Feel free to start review them. Thanks!


Record spans when parsing Statement

Allows #4 to add labels to CFG nodes.
Uses PEG's rule arguments (similar to LALRPOP macros). It should be straightforward to extend this to the rest of the AST as needed.

Thanks a ton