This post reviews four main virtualization options in short.

💡 VM technologies are essentially considered by people when addressing on-premise use cases or when building DR for data centers.

VMware Virtualization

• Started at (2003).

• Offers type-1 hypervisor that runs on bare-metal called ESXi with minimum disk image footprint (32MB), with resources, storage, and networking capabilities, and UI console (DCUI).

This post is a follow up on the previous one where I discussed the concept of infrastructure as code and Terraform. In this post, I will provide few useful notes I took while working on IaC projects, with examples to illustrate the techniques on two of the public providers (AWS / Oracle).

An interesting usecase I have encountered recently is establishing a secure path (bridge) between Traefik as ingress controller and its destination backends.

The post addresses traefik usage within Kubernetes, however it is applicable to other setups.

I have enjoyed reading this piece on stability and reliability by Colm MacCárthaigh. It is part of a concise and valuable series by AWS about the art of system operations collected under the name “Amazon Builders’ Library”.

The comparison between coffee urn and computers when building reliable operational model is perfect and up to the point. Then, three characteristics taken from this analogy are observed: 1. have a simple constant function that does not scale based on load stress solely, 2. no different modes or operational branching, 3. anti-fragility which is the preparations that hold systems reliable when most needed. The author mentions the coined term for these principles on reliability: “Constant Work Patterns”. Route 53 and S3 are presented as use cases that fit and demonstrate the model.

Helmfile is an orchestrator tool for collecting, building, and deploying cloud-native apps. Basically it’s the packager for helm chart based applications.

One of the interesting ideas I came along recently, is utilizing it for working in air-gapped environments, where access to the internet is not feasible.

Use Case

Let’s say you were deploying an application to a Kubernetes cluster. The idea is to package all dependencies and manifests beforehand in a local or control machine, then push the consolidated deployment directory to the offline machine.

The diagram below depicts the flow.