Weekly Newsletter
#
4
Maybe you don't need Kubernetes, Git commit message convention, and more
This week we've been working hard to prepare for today's webinar on secrets. We were wondering how big of a problem securing secrets is - turns out, it's quite big. A recent academic study found that over 100,000 Github repositories (!!) are unknowingly leaking secret keys, and thousands of new, unique secret keys are being leaked every day. That's just wild.
Maybe you don't need Kubernetes
In this post, Mathias Endler dives into why Kubernetes wasn't the right fit based on their requirements for container orchestration, and went with Nomad instead. It attracted a good number of comments on HN.
‘AWS vs K8s’ is the new ‘Windows vs Linux’
Ian Miell described how Kubernetes could be at risk of going the way of OpenStack in relation to AWS. That kind of title for a post is bound to attract some comments, and it did. I'll only link to the HN ones - Redditers said things like "OP is a recruiter", which may be quite harsh...
Do I need a service mesh?
Owen Garrett explains what service mesh is, the state of the technology, and how it is a milestone in your journey, but not the starting point.
AWS: How to get notified on compromised credentials
Tamás Sallai describes how when you create access keys you are basically blind how they are used, and writes about his approach to create notification alerts to help detect when a compromise occurs.
How to get more out of your Git commit messages
Defining a project Git commit message convention is probably low on a developer’s “to-do” list, but it is so easy there's no excuse not to do it. In this article, Eyar Zilberman explains why a commit message convention is useful and how to get started, including a Regex cheatsheet.