Categories
Hybrid Multicloud

Rancher K3S – “5 less than K8S”

I’m exploring a fascinating Kubernetes variant from Ranchel Labs, K3S (How do you pronounce this? “Kiss”? 😀 ).

https://rancher.com/docs/k3s/latest/en/architecture/

It’s looking very promising to me – lightweight, easy to install and using a real DB as control plane store instead of etcd! They target it to Edge and IOT kind of applications, but I see it larger that that. In my opinion it should also run in the cloud very well or be a nice base for on-premises development workflows, assuring good portability to “big” managed K8S in the cloud.

Also runs on Raspberry Pi!

Expect an article on this soon enough!

Categories
Oracle Cloud Infrastructure

OCI: Receive notification when your instance is down

Absolutely everybody:

– I would like to be notified when my instances go down, please? (≧︿≦)

This is one of the most common questions I’ve heard, so let’s see what’s required to put such notifications in place in Oracle Cloud Infrastructure (OCI).

0. What are the prerequisites?

  • Quite obviously, a subscription to OCI. If you don’t have it yet, please go and grab one – you’ll have access to $300 you can spend on any IaaS or PaaS service during one month, but when this month (or credits) expire, you will still have access to “always free” resources. More details here: https://www.oracle.com/cloud/free/
    Everything described here will work with always free subscription, none of the services used require upgrading to a paid subscription.
  • You already have basic knowledge of OCI – you know how to navigate the OCI console and create and run instances.
  • Rights to “Manage” the Notifications Service and rights to “Use” the OCI Metrics. If you are the tenancy admin, then you already have those; if you aren’t – more on this later in the article.
  • Bare metal or Virtual instances which state you’re going to track. The instances should have the metrics enabled.
  • A valid email address to receive the notifications.

TLDR: We will send notifications when the instance stops producing metrics. This is typically true in 3 cases: 1) when the instance is stopped; 2) when it crashed or its network connection was severed for some reason; 3) when the metrics agent stopped working.