{"id":544,"date":"2017-12-08T07:00:22","date_gmt":"2017-12-08T15:00:22","guid":{"rendered":"http:\/\/andrewwippler.com\/?p=544"},"modified":"2017-11-30T14:36:15","modified_gmt":"2017-11-30T22:36:15","slug":"kubernetes-health-check","status":"publish","type":"post","link":"https:\/\/andrewwippler.com\/2017\/12\/08\/kubernetes-health-check\/","title":{"rendered":"kubernetes health check"},"content":{"rendered":"

The day before thanksgiving, I was pondering an issue I was having. I was pinning a package to a specific version in my Docker container and the repository I grabbed it from stopped offering this specific version. This resulted in a container that Jenkins responded as being built correctly, but missing an integral package that allowed my application to function properly. This led me to believe I had to implement Puppet’s Lumogon<\/a> in my Jenkins build process. Curious if anyone had something like this already developed, I headed over to github.com which eventually led me to compose this tweet:<\/p>\n

\n

Step 1: Have k8s technical problem
\nStep 2: Review
@kelseyhightower<\/a>‘s recent git pushes
\nStep 3: Find:
https:\/\/github.com\/kelseyhightower\/ato\/blob\/master\/deployments\/helloworld.yaml#L26-L29<\/a>
\nStep 4: Realize this is exactly something I needed to implement
\nStep 5: Implement feature
\nStep 6: Enjoy thanksgiving without worry
\nStep 7: Blog post<\/p>\n

\u2014 Andrew J. Wippler (@AndrewWippler) November 22, 2017<\/a><\/p><\/blockquote>\n