<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scheduler on Cloudowski DevOps Expert</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/tags/scheduler/</link><description>Recent content in Scheduler on Cloudowski DevOps Expert</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 11 Mar 2018 22:00:00 +0000</lastBuildDate><atom:link href="https://63db89d1.hugo-coudowski-website.pages.dev/tags/scheduler/index.xml" rel="self" type="application/rss+xml"/><item><title>Treat your pods according to their needs - three QoS classes in Kubernetes</title><link>https://63db89d1.hugo-coudowski-website.pages.dev/articles/three-qos-classes-in-kubernetes/</link><pubDate>Sun, 11 Mar 2018 22:00:00 +0000</pubDate><guid>https://63db89d1.hugo-coudowski-website.pages.dev/articles/three-qos-classes-in-kubernetes/</guid><description>One of the features that comes with Kubernetes is its ability to scale horizontally services running on it and use available resources more efficiently. I’ve been hearing that containers are just &lt;em>lightweight virtualization&lt;/em> (which is not true) so you can put more apps on the same resources. I can agree that it’s partially true</description></item></channel></rss>