Not rendering correctly? View this email as a web page here.

This Week: Continuing Our Deep Dive On K8s 101!

Hey there,

We've been hard at work writing great articles to continue our deep dive into the nuts and bolts of K8s, so you can sit back and relax and gain a deeper understanding of how this awesome new technology works. 

Take a look, and let us know what you think by replying to this email!



Check Out our latest article

Screenshot 2019-08-12 16.16.42

Kubernetes Jobs 101

Kubernetes features several controllers for managing pods. We have ReplicaSetsDaemonSetsStatefulSets, and Deployments. Each one of those has its own scenario and use case. However, they all share one common property: they ensure that their pods are always running. If a pod fails, the controller restarts it or reschedules it to another node to make sure the application the pods is hosting keeps running.

Screenshot 2019-08-12 16.23.44

Kubernetes DaemonSets 101

Sometimes, you may need to run a process on all the nodes of the cluster. Think of log-collecting services like Prometheus Log Exporter or storage daemons like glusterd. Such services need to be started on each node as soon as the node joins the cluster. You may think: we can use a cron job that runs on machine boot/reboot. Perhaps use the /etc/init.local file to ensure that a specific process or command gets executed as soon as the server gets started. While certainly a valid solution, using the node itself to control the daemons that run on it (especially within a Kubernetes cluster) suffers some drawbacks:


From the Community

As always, a selection of cool stuff we've found in the larger K8s community - exciting news, updates, releases, vulnerabilities and more. If there is something you want us to include in a newsletter please send it to

How hot is Kubernetes? Even traditional banks are transforming to embrace it

While Kubernetes is still not in production at most enterprises, Italy's biggest bank shows the way forward. Kubernetes has become a standard infrastructure API with a gravitational pull that vendors like Red Hat, Mesosphere (now D2IQ), and Pivotal have been unable to escape. If you're in the business of enabling enterprises to build applications, you've got to support Kubernetes. Period.


Survey Identifies Myriad Kubernetes Adoption Drivers

One of the assumptions made about key drivers Kubernetes adoption is that organizations are trying to accelerate the rate at which software is built by embracing microservices based on containers. However, a survey of 130 attendees of three recent container conferences published by Replex, a provider of governance and cost management tools for Kubernetes, finds the top two drivers of Kubernetes adoption are improving scalability (61%) and resource utilization (46%), followed by a desire to adopt a cloud-native stack (37%) and shortening development and deployment times (42%).


Latest Kubernetes Release Focuses on Continuous Improvement and Stability

The Kubernetes team launched the 1.15 release on June 19th, 2019, the second release of 2019. According to the release announcement, the goal of the latest version is continuous improvement and extensibility. Kubernetes 1.15 includes new features, such as pruning on custom resource definitions, but relative to previous releases, focuses primarily on stability over enhancements.


Kubernetes catches up with operational reality

With Kubernetes now established in many organisations as the container orchestration platform of the future, are cracks already starting to show? Well, not exactly – but if I could pull out one common theme from what’s hot in the world of cloud-native, it’s the dawning light of Day Two.


For more details about magalix agent:

Magalix agent repo github_PNG58

Magalix agent at GCP Marketplace Untitled-2