<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for IanMLewis</title><link>http://disqus.com/by/IanMLewis/</link><description></description><atom:link href="http://disqus.com/IanMLewis/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 04 Dec 2019 19:43:32 -0000</lastBuildDate><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4712515270</link><description>&lt;p&gt;I'm glad it was helpful to you!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Wed, 04 Dec 2019 19:43:32 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4699721036</link><description>&lt;p&gt;I'm glad it was helpful! Will look out for you at the meetup.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Sat, 23 Nov 2019 03:22:33 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4483725569</link><description>&lt;p&gt;But of course it has! files never seem to stay put...&lt;/p&gt;&lt;p&gt;Thanks for pointing this out. The link should be fixed now.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Fri, 31 May 2019 03:25:33 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4456708232</link><description>&lt;p&gt;Maybe it's this issue? &lt;a href="https://github.com/kubernetes-sigs/cri-tools/issues/436" rel="nofollow noopener" target="_blank" title="https://github.com/kubernetes-sigs/cri-tools/issues/436"&gt;https://github.com/kubernet...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Other than that you might be using an older version of crictl?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Thu, 09 May 2019 21:41:38 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4430610356</link><description>&lt;p&gt;Glad it was helpful to you!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Fri, 19 Apr 2019 19:33:56 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4421812187</link><description>&lt;p&gt;Great to hear! I'm glad you got something out of it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Sat, 13 Apr 2019 17:08:05 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4421811845</link><description>&lt;p&gt;Thanks. I'm glad it was helpful for you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Sat, 13 Apr 2019 17:07:44 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4388725923</link><description>&lt;p&gt;Hi, thanks! It would be great if you translated this into Korean! Please just add my name as original author and link back to the original post.&lt;/p&gt;&lt;p&gt;Let me know when you've finished! :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Thu, 21 Mar 2019 18:56:06 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4368874980</link><description>&lt;p&gt;Grad it was helpful!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Thu, 07 Mar 2019 18:17:12 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4348803567</link><description>&lt;p&gt;I'm glad they were helpful!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Thu, 21 Feb 2019 21:01:32 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4312040030</link><description>&lt;p&gt;For those paying attention there is also rktlet, which I haven't had time to investigate yet.&lt;br&gt;&lt;a href="https://github.com/kubernetes-incubator/rktlet" rel="nofollow noopener" target="_blank" title="https://github.com/kubernetes-incubator/rktlet"&gt;https://github.com/kubernet...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Mon, 28 Jan 2019 23:53:43 -0000</pubDate></item><item><title>Re: Container Runtimes Part 4: Kubernetes Container Runtimes &amp; CRI</title><link>https://www.ianlewis.org/en/container-runtimes-part-4-kubernetes-container-run#comment-4311566717</link><description>&lt;p&gt;You're welcome!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Mon, 28 Jan 2019 16:30:04 -0000</pubDate></item><item><title>Re: The Almighty Pause Container</title><link>https://www.ianlewis.org/en/almighty-pause-container#comment-4120124033</link><description>&lt;p&gt;Yah. I guess I wasn't trying to go to deep into the weeds since the post is mostly geared towards folks who don't use the syscalls directly and I cared mostly about wait but I see now that it's necessary. Re-written with full explanation about what exactly fork and exec do and how a new, totally different process is started.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Sat, 29 Sep 2018 00:56:24 -0000</pubDate></item><item><title>Re: Container Runtimes Part 1: An Introduction to Container Runtimes</title><link>https://www.ianlewis.org/en/container-runtimes-part-1-introduction-container-r#comment-4053565708</link><description>&lt;p&gt;Thanks! Glad it was useful to you&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Wed, 22 Aug 2018 06:38:37 -0000</pubDate></item><item><title>Re: Container Runtimes Part 2: Anatomy of a Low-Level Container Runtime</title><link>https://www.ianlewis.org/en/container-runtimes-part-2-anatomy-low-level-contai#comment-3994367954</link><description>&lt;p&gt;Thanks! I'm glad you got something out of it.&lt;br&gt;Also, good catch. I fixed the typo.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Wed, 18 Jul 2018 01:56:22 -0000</pubDate></item><item><title>Re: Blue/Green Deployments on Kubernetes</title><link>https://www.ianlewis.org/en/bluegreen-deployments-kubernetes#comment-3967606310</link><description>&lt;p&gt;In general there is a small amount of time between when the service is updated and kube-proxy updates iptables on each node to service the new pods. It should be on the order of a second or two. But could be longer if you have a lot of nodes. I don't think there is an SLO that I know of for updates to services. Either way there shouldn't be downtime as I'm pretty sure the rules are updated atomically.&lt;/p&gt;&lt;p&gt;However, if you can service traffic from your old and new versions of the app at the same time then, by all means, use canaries and rolling-updates.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Sat, 30 Jun 2018 08:20:39 -0000</pubDate></item><item><title>Re: What are Kubernetes Pods Anyway?</title><link>https://www.ianlewis.org/en/what-are-kubernetes-pods-anyway#comment-3917552511</link><description>&lt;p&gt;Thanks! Glad you found it useful.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Fri, 25 May 2018 21:27:52 -0000</pubDate></item><item><title>Re: What are Kubernetes Pods Anyway?</title><link>https://www.ianlewis.org/en/what-are-kubernetes-pods-anyway#comment-3723395328</link><description>&lt;p&gt;Yah, a sidecar usually has some sort of interface that is uses to communicate with the main pod. Whether that be a file or a network port over localhost. Theoretically you could replace the sidecar with anything that can implement that interface.&lt;/p&gt;&lt;p&gt;If the containers don't need to communicate in any way then that's a good indication they can run in separate pods. Also if the containers are going to scale out, you would do that by adding new pods rather than new containers onto a single pod. Separate pods should be the default so when in doubt they can be separate I think.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Wed, 24 Jan 2018 00:45:02 -0000</pubDate></item><item><title>Re: What are Kubernetes Pods Anyway?</title><link>https://www.ianlewis.org/en/what-are-kubernetes-pods-anyway#comment-3711467666</link><description>&lt;p&gt;You're very welcome!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Tue, 16 Jan 2018 18:15:04 -0000</pubDate></item><item><title>Re: The Almighty Pause Container</title><link>https://www.ianlewis.org/en/almighty-pause-container#comment-3687693604</link><description>&lt;p&gt;I'm thinking signals like TERM or HUP could be sent from a sidecar container to another container in the same pod to tell it to restart it to reload it's configuration.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Mon, 01 Jan 2018 23:43:50 -0000</pubDate></item><item><title>Re: The Almighty Pause Container</title><link>https://www.ianlewis.org/en/almighty-pause-container#comment-3624094372</link><description>&lt;p&gt;You're right and I specifically addressed that point in the post. I described it as an entry in the process table. Do you think that I addressed the point inadequately?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Sun, 19 Nov 2017 20:09:50 -0000</pubDate></item><item><title>Re: The Almighty Pause Container</title><link>https://www.ianlewis.org/en/almighty-pause-container#comment-3618364311</link><description>&lt;p&gt;My pleasure!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Wed, 15 Nov 2017 22:50:10 -0000</pubDate></item><item><title>Re: The Almighty Pause Container</title><link>https://www.ianlewis.org/en/almighty-pause-container#comment-3616774046</link><description>&lt;p&gt;All fixed. Make sure to put the -p option before the image name in the command so it's not passed as an argument to the pause process.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Wed, 15 Nov 2017 00:08:17 -0000</pubDate></item><item><title>Re: The Almighty Pause Container</title><link>https://www.ianlewis.org/en/almighty-pause-container#comment-3616756184</link><description>&lt;p&gt;Ah, right, good catch. That's likely a copy and paste error. I'll fix it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Tue, 14 Nov 2017 23:44:28 -0000</pubDate></item><item><title>Re: The Almighty Pause Container</title><link>https://www.ianlewis.org/en/almighty-pause-container#comment-3616616323</link><description>&lt;p&gt;When you use --net you are joining another containers network namespace so AFAIK you need to expose the ports you want to expose on that container.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Lewis</dc:creator><pubDate>Tue, 14 Nov 2017 21:18:00 -0000</pubDate></item></channel></rss>