search

vmware-archive / purser

Kubernetes Cloud Native Applications visibility
Other
170 stars 43 forks source link

Installation issues when deploying the controller in either minikube or AWS EKS #285

Open dkc-bitsian opened 4 years ago

dkc-bitsian commented 4 years ago

Describe the bug i am using the code with version 1.0.0 tag. i did the first thing that is mentioned in the readme which is to install the controller. however, the deployment fails.

kubectl describe po  purser-controller-76dcf6bbd6-4kz6w
Name:               purser-controller-76dcf6bbd6-4kz6w
Namespace:          default
Priority:           0
PriorityClassName:  <none>
Node:               minikube/192.168.99.108
Start Time:         Thu, 09 Apr 2020 23:56:08 -0700
Labels:             app=purser
                    pod-template-hash=76dcf6bbd6
Annotations:        <none>
Status:             Running
IP:                 172.17.0.4
Controlled By:      ReplicaSet/purser-controller-76dcf6bbd6
Containers:
  purser-controller:
    Container ID:   docker://c41ce5dff97add4bd922c7196b0626d40f7ca24d34591688e9b82e01535c8b66
    Image:          kreddyj/controller-amd64:1.0.0
    Image ID:       docker-pullable://kreddyj/controller-amd64@sha256:ef17da8f92be1fa26c0a7888c0623e8192bb41e31d7aa1e8b1256028fbdca629
    Port:           3030/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Thu, 09 Apr 2020 23:59:28 -0700
      Finished:     Thu, 09 Apr 2020 23:59:28 -0700
    Ready:          False
    Restart Count:  5
    Limits:
      cpu:     300m
      memory:  1000Mi
    Requests:
      cpu:        300m
      memory:     1000Mi
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from purser-service-account-token-5j59z (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  purser-service-account-token-5j59z:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  purser-service-account-token-5j59z
    Optional:    false
QoS Class:       Guaranteed
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
  ----     ------     ----               ----               -------
  Normal   Scheduled  5m                 default-scheduler  Successfully assigned default/purser-controller-76dcf6bbd6-4kz6w to minikube
  Normal   Created    4m (x4 over 5m)    kubelet, minikube  Created container purser-controller
  Normal   Started    4m (x4 over 5m)    kubelet, minikube  Started container purser-controller
  Normal   Pulling    4m (x5 over 5m)    kubelet, minikube  Pulling image "kreddyj/controller-amd64:1.0.0"
  Normal   Pulled     4m (x5 over 5m)    kubelet, minikube  Successfully pulled image "kreddyj/controller-amd64:1.0.0"
  Warning  BackOff    43s (x25 over 5m)  kubelet, minikube  Back-off restarting failed container

To Reproduce Steps to reproduce the behavior:

  1. kubectl create -f purser-controller-setup.yaml

Expected behavior No error **

Screen Shot 2020-04-10 at 12 04 17 AM

**

Environment (please complete the following information):