The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Single-node deployments of Kubernetes are more common than what one would expect. In some scenarios, single-node clusters make much more sense. For development purposes or testing, there’s no need to deploy a full-blown production-grade cluster. Single-node deployments are also handy for appliances and IoT applications since they have a much smaller footprint. Enter MicroK8s, a tool by Canonical that enables you to easily deploy a lightweight single-node cluster in your local environment.
I wanted to follow up Ron Miller’s article in TechCrunch about Netdata’s Series A funding last month with the story of Netdata’s inception. It all started when I got… pissed off.
Big data, AI, machine learning, and numerous others are all buzzwords we seem to throw around lightly in recent years. Even though they are hugely different from one another, they all have one thing in common. Data! Huge amounts of data that need to be managed. The downside of that is that the more data you have the more of a headache it is to store, query, and make sense of.
A few weeks ago, Amazon announced a new feature for EBS snapshots: Amazon EBS Fast Snapshot Restore (FSR). Normally, accessing data on new EBS volumes was quite slow as the data is lazy-loaded from S3. When Fast Snapshot Restore (FSR) has been enabled on an EBS snapshot, new EBS volumes created from that snapshot will allow fast data access. While this feature is very good, it’s very expensive to keep enabled on an EBS snapshot for a long time.
As serverless application architectures have gained popularity, AWS Lambda has become the best-known service for running code on demand without having to manage the underlying compute instances. From an ops perspective, running code in Lambda is fundamentally different than running a traditional application. Most significantly from an observability standpoint, you cannot inspect system-level metrics from your application servers.
