This is a small article about understanding the liveness, readiness and startup in kubernetes. There's good explanation in the kubernetes documentation: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ This video also explains well the process: https://www.youtube.com/watch?v=aTlQBofihJQ But I wanted to understand it in a practical way. So I have this demo: https://github.com/DiegoTc/guest-book-js-docker/tree/Running-App-Version-1 It's a simple application running on a kubernetes cluster. https://github.com/DiegoTc/guest-book-js-docker/blob/Running-App-Version-1/argo/deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: chat-ui spec: replicas: 1 revisionHistoryLimit: 3 selector: matchLabels: app: chat-ui template: metadata: labels: app: chat-ui spec: containers: - image: diegotc/guestbook:20230803-064434 imagePullPolicy: Always nam
Long time without writing. Well this is a new experience I had. I was working last night, shut down my laptop. Today on the morning I noticed something strange in my laptop each time I enter my password Unity never finish to load. I restart several time, and decide to start the graphical environment from the CLI mode. My surprise is the following. starting timidity++ alsa midi emulation fail So I start to google it from my smartphone and find some solutions in askubuntu. Solution #1 http://askubuntu.com/questions/63382/ubuntu-11-04-hangs-while-booting Solution #2 http://lkubuntu.wordpress.com/2011/08/30/quick-and-easy-way-to-fix-x11-issues/ So when I restart my system again finally it loads completely, but I was missing a nice surprise!!! Seven or eight windows about error reports. The funny part of this story is that each time I click in the report button, it never open the launchpad window for reporting the bugs, so I decide it to leave it that way.