The microservices-chat from python-microservices

Can you add a license? Looking for starter microservice examples to use as the basis of examples for a course or an assignment for my students but need to make sure I build from examples I can use based on the license, which this project is missing. Thanks.

Unable to run docker image

Hi,

Thanks for your work. I am currently trying to learn kubernetes and Micro-services.

I followed your README file and I was able to see nginx server page.
But actually i am not able to see chat microservice running on this cluster.

I have one master node and one worker node kubernates setup. But for some reason all three micro-service failed to lunch.
For me it looks to be specific to these micro-service. But i am not pretty sure.

Please let me know why i am getting POD status as bellow for your micro-services.

root@k8s-master-node:/home/jmallesh/MSSpace/microservices-chat# kubectl get pods
NAME                          READY   STATUS             RESTARTS   AGE
chat-db-7c6f7c9885-vwn5k      0/1     CrashLoopBackOff   3          70s
chat-front-5c9fc95dff-g2x2j   0/1     CrashLoopBackOff   3          68s
chat-svc-595f484657-drpkb     0/1     CrashLoopBackOff   3          70s
root@k8s-master-node:/home/jmallesh/MSSpace/microservices-chat# 
`
`root@k8s-master-node:/home/jmallesh/MSSpace/microservices-chat# kubectl describe pods
Name:         chat-db-7c6f7c9885-vwn5k
Namespace:    default
Priority:     0
Node:         k8s-worker-node-1/10.0.2.6
Start Time:   Fri, 16 Oct 2020 00:43:44 +0530
Labels:       app.kubernetes.io/instance=chat-db
              app.kubernetes.io/name=chat-db
              pod-template-hash=7c6f7c9885
Annotations:  cni.projectcalico.org/podIP: 192.168.148.161/32
              cni.projectcalico.org/podIPs: 192.168.148.161/32
Status:       Running
IP:           192.168.148.161
IPs:
  IP:           192.168.148.161
Controlled By:  ReplicaSet/chat-db-7c6f7c9885
Containers:
  chat-db:
    Container ID:   docker://cb6ef788e921d02a1e33b4f58367cf46f30a4d90eee8bf0f9f445050fb26671f
    Image:          chat_db:v1
    Image ID:       docker://sha256:31e013ffee045f5f38a17cecafc4dbacac1b725ef38d064ea48d5a72169e9a5a
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    3
      Started:      Fri, 16 Oct 2020 00:44:38 +0530
      Finished:     Fri, 16 Oct 2020 00:44:39 +0530
    Ready:          False
    Restart Count:  3
    Liveness:       http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-2bj88 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-2bj88:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-2bj88
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                            From               Message
  ----     ------     ----                           ----               -------
  Normal   Scheduled  91s                            default-scheduler  Successfully assigned default/chat-db-7c6f7c9885-vwn5k to k8s-worker-node-1
  Normal   Pulled     <invalid> (x4 over <invalid>)  kubelet            Container image "chat_db:v1" already present on machine
  Normal   Created    <invalid> (x4 over <invalid>)  kubelet            Created container chat-db
  Normal   Started    <invalid> (x4 over <invalid>)  kubelet            Started container chat-db
  Warning  BackOff    <invalid> (x9 over <invalid>)  kubelet            Back-off restarting failed container


Name:         chat-front-5c9fc95dff-g2x2j
Namespace:    default
Priority:     0
Node:         k8s-worker-node-1/10.0.2.6
Start Time:   Fri, 16 Oct 2020 00:43:46 +0530
Labels:       app.kubernetes.io/instance=chat-front
              app.kubernetes.io/name=chat-front
              pod-template-hash=5c9fc95dff
Annotations:  cni.projectcalico.org/podIP: 192.168.148.163/32
              cni.projectcalico.org/podIPs: 192.168.148.163/32
Status:       Running
IP:           192.168.148.163
IPs:
  IP:           192.168.148.163
Controlled By:  ReplicaSet/chat-front-5c9fc95dff
Containers:
  chat-front:
    Container ID:   docker://b5e96f3a97dda24e407fd302b0c175776734d650ca01957a7aba9522fdc21a29
    Image:          chat_front:v1
    Image ID:       docker://sha256:23665fde27d75628a9e7209d177016fbb222377f5e79d3bda5c5595de75c2522
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Terminated
      Reason:       Error
      Exit Code:    3
      Started:      Fri, 16 Oct 2020 00:45:11 +0530
      Finished:     Fri, 16 Oct 2020 00:45:12 +0530
    Last State:     Terminated
      Reason:       Error
      Exit Code:    3
      Started:      Fri, 16 Oct 2020 00:44:26 +0530
      Finished:     Fri, 16 Oct 2020 00:44:28 +0530
    Ready:          False
    Restart Count:  4
    Liveness:       http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-2bj88 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-2bj88:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-2bj88
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                            From               Message
  ----     ------     ----                           ----               -------
  Normal   Scheduled  89s                            default-scheduler  Successfully assigned default/chat-front-5c9fc95dff-g2x2j to k8s-worker-node-1
  Warning  Unhealthy  <invalid>                      kubelet            Liveness probe failed: Get "http://192.168.148.163:8080/": dial tcp 192.168.148.163:8080: connect: connection refused
  Warning  BackOff    <invalid> (x8 over <invalid>)  kubelet            Back-off restarting failed container
  Normal   Pulled     <invalid> (x5 over <invalid>)  kubelet            Container image "chat_front:v1" already present on machine
  Normal   Created    <invalid> (x5 over <invalid>)  kubelet            Created container chat-front
  Normal   Started    <invalid> (x5 over <invalid>)  kubelet            Started container chat-front
  Warning  Unhealthy  <invalid>                      kubelet            Liveness probe failed: Get "http://192.168.148.163:8080/": read tcp 10.0.2.6:38862->192.168.148.163:8080: read: connection reset by peer


Name:         chat-svc-595f484657-drpkb
Namespace:    default
Priority:     0
Node:         k8s-worker-node-1/10.0.2.6
Start Time:   Fri, 16 Oct 2020 00:43:44 +0530
Labels:       app.kubernetes.io/instance=chat-svc
              app.kubernetes.io/name=chat-svc
              pod-template-hash=595f484657
Annotations:  cni.projectcalico.org/podIP: 192.168.148.162/32
              cni.projectcalico.org/podIPs: 192.168.148.162/32
Status:       Running
IP:           192.168.148.162
IPs:
  IP:           192.168.148.162
Controlled By:  ReplicaSet/chat-svc-595f484657
Containers:
  chat-svc:
    Container ID:   docker://b3d7ec26e1b2c46c47c41f285838b04aa88f50d4ad348e2fbffe196ec132b343
    Image:          chat_svc:v1
    Image ID:       docker://sha256:c76985a00a84fcf116e51b7e20ac8b5c6c55ff7666f041262ff958ff7d6aa242
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Fri, 16 Oct 2020 00:44:42 +0530
      Finished:     Fri, 16 Oct 2020 00:44:44 +0530
    Ready:          False
    Restart Count:  3
    Liveness:       http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:http/ delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-2bj88 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  default-token-2bj88:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-2bj88
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                             From               Message
  ----     ------     ----                            ----               -------
  Normal   Scheduled  91s                             default-scheduler  Successfully assigned default/chat-svc-595f484657-drpkb to k8s-worker-node-1
  Warning  Unhealthy  <invalid>                       kubelet            Liveness probe failed: Get "http://192.168.148.162:8080/": dial tcp 192.168.148.162:8080: connect: connection refused
  Normal   Pulled     <invalid> (x4 over <invalid>)   kubelet            Container image "chat_svc:v1" already present on machine
  Normal   Created    <invalid> (x4 over <invalid>)   kubelet            Created container chat-svc
  Normal   Started    <invalid> (x4 over <invalid>)   kubelet            Started container chat-svc
  Warning  BackOff    <invalid> (x10 over <invalid>)  kubelet            Back-off restarting failed container
root@k8s-master-node:/home/jmallesh/MSSpace/microservices-chat#

python-microservices / microservices-chat Goto Github PK

microservices-chat's People

Stargazers

Watchers

Forkers

microservices-chat's Issues

helm upgrade "upgrade false"

Missing License

Unable to run docker image

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

Jobs