<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on A Curious Coder</title>
    <link>http://acuriouscoder.net/tag/kubernetes/</link>
    <description>Recent content in Kubernetes on A Curious Coder</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Apr 2018 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://acuriouscoder.net/tag/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Kubernetes &amp; Logging</title>
      <link>http://acuriouscoder.net/kubernetes-logging/</link>
      <pubDate>Wed, 04 Apr 2018 00:00:00 +0000</pubDate>
      
      <guid>http://acuriouscoder.net/kubernetes-logging/</guid>
      <description>When you are running services in a Kubernetes cluster they are probably writing log statements that contain all sorts of useful information you need to have look at now and then. Being the good developer you behaved and made sure all logging statements are written to the console. This gives you the possibility to use kubectl logs -f &amp;lt;pod-name&amp;gt; -c &amp;lt;container&amp;gt; to tail the logs of a specific pod and container.</description>
    </item>
    
  </channel>
</rss>