TL;DR – Last Week’s Container News (01/12/18-01/19/18)

DockerCon 2018: Registration Now Open

DockerCon 2018 registration opened up this week. This conference features latest Docker news, training and certification opportunities, and the chance to network with some 6000 attendees. The conference will be June 12-15 in San Francisco. Register now for early bird pricing (ends Jan 31).

Tips for Kubernetes Logging

A recent article in The New Stack states that “any Kubernetes production environment will rely heavily on logs” and provides five suggestions for logging in a Kubernetes environment. Among them:

  • Use a single, highly available log aggregator
  • Create a single, common transaction ID across the entire end-to-end call
  • Ensure service names / applications are being logged
  • Standardize logging levels throughout the stack
  • Ensure no data meant to be secure are being logged in the open

PowerShell Increasingly Cross-Platform

Although traditionally associated with “core Microsoft workloads,” PowerShell is now becoming a cross-platform scripting tool, according to The New Stack. PowerShell Core now runs in versions of Ubuntu, Debian, CentOS, RedHat, OpenSUSE, Fedora, and macOS. There are also experimental versions for Raspbain and Windows on ARM. For more info on PowerShell Core — including a comparison to Windows Powershell — check out The New Stack article. 

Meltdown / Spectre Exploits: Why Raspberry Pi Boards Aren’t Affected

The recently-discovered Meltdown / Spectre exploits do not affect Raspberry Pi boards, according to Raspberry Pi Foundation founder Eben Upton.

These exploits take advantage of modern processors’ tendency to use “techniques including caching, instruction reordering, and speculation to deliver much higher performance than a simple processor could hope to achieve.” Cores used in Raspberry Pis do not use the speculation techniques that are vulnerable to these exploits.

Meltdown / Spectre Exploits: Patches Affecting Performance / Cost

Some patches for the Meltdown / Spectre vulnerabilities have come at the cost of CPU performance, according to The New Stack’s “This Week in Numbers“. This may mean higher bills for folks running workloads on some cloud services. However, Google seems to have developed a technique to prevent the exploit without disabling speculative execution — meaning the performance impact for workloads on Google’s systems should be minimal.


About the Author: