forked from hechuan73/train_ticket
-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubeadm cannot run Trainticket in k8s #284
Comments
HI, did you get this up and running? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 LTSdocker version(e.g
docker version
): 24.0.7Kubeadm 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
kubectl logs -n trainticket ts-config-service-6d85b96456-hr4d9
auth-service-log.txt
kubectl describe pod -n trainticket ts-config-service-6d85b96456-hr4d9
Unhealthy pod
Search result and your thoughts
The text was updated successfully, but these errors were encountered: