Skip to content

kubeadm cannot run Trainticket in k8s #284

@Paul-Lyu

Description

@Paul-Lyu

Summary

I tried to deploy train-ticket in k8s
However, many service-related pods would become Running state but not ready. Finally, they would become Error and loop.
At first, describe pod will display Readiness probe failed: dial tcp 192.39.213.36:12345: connect: connection refused. After searching online, some people said that the initialDelaySeconds needs to be increased. I have now adjusted it to 6400.

Expected behaviour

Running state and pod ready 1/1

Current behaviour

many service-related pods have not been working properly

Steps to reproduce

(1) kubectl create -f ts-deployment-part1.yml
(2) kubectl create -f ts-deployment-part2.yml
(3) kubectl create -f ts-deployment-part3.yml

Your environment

OS(e.g: cat /etc/os-release): Ubuntu 22.04.3 LTS

docker version(e.g docker version): 24.0.7

Kubeadm version: v1.27.8

Kubernetes version(use kubectl version):
client version: v1.27.8
server version: v1.27.6

Additional context

kubectl get pod -n trainticket
getpod

kubectl logs -n trainticket ts-config-service-6d85b96456-hr4d9
auth-service-log.txt

kubectl describe pod -n trainticket ts-config-service-6d85b96456-hr4d9
auth_service

Unhealthy pod
unhealthy

Search result and your thoughts

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions