From the article that we use OpenTofu, this one will replace the code in OpenTofu. This article covers the transition from raw hardware to a functional orchestrator and back to zero. We call this the Provision-Orchestrate-Collapse-Destroy cycle. 1. The Provisioning Phase We start at the VM level. OpenTofu interacts with your provider to reserve CPU, RAM, and storage. Create a Virtual Machine. Use cloud-init to bootstrap the environment. Install the K8s Control Plane (e.g., K3s for efficiency). 2. The Orchestration Phase Once the cluster is “Healthy,” OpenTofu switches to the Kubernetes Provider. ...

This article is a continuation of the “Terraform Phoenix Cycle.” The core concept remains the same: the underlying Infrastructure as Code (IaC) layer is constant, while the Kubernetes (K8s) workload layer becomes interchangeable. In this model, K8s modules are deployed based on specific operational needs; once their task is complete, the module is destroyed, only to be resurrected when the next requirement arises. We will explore three specific modules in this guide: ...

note: this is refernce from Writing custom terraform providers. As the retired article, I want to reference this as full content before it’s gone. In Terraform, a “provider” is the logical abstraction of an upstream API. This guide details how to build a custom provider for Terraform. Custom providers in Terraform let you use Terraform to build and manage new infrastructure components. These custom providers can be written for public components (such as a new SaaS provider) or private components (such as a private cloud). In this blog post, we’ll show you how easy it is to write a complete custom provider. ...

This article covers the transition from raw hardware to a functional orchestrator and back to zero. We call this the Provision-Orchestrate-Collapse-Destroy cycle. 1. The Provisioning Phase We start at the VM level. Terraform interacts with your provider to reserve CPU, RAM, and storage. Create a Virtual Machine. Use cloud-init to bootstrap the environment. Install the K8s Control Plane (e.g., K3s for efficiency). 2. The Orchestration Phase Once the cluster is “Healthy,” Terraform switches to the Kubernetes Provider. ...

We begin by examining the training resources provided by the three major cloud providers. Microsoft Azure Microsoft offers a dedicated learning path for Terraform through their “Fundamentals” course: Terraform Fundamentals. For those requiring deeper implementation details, they maintain a comprehensive technical overview here: Azure Terraform Documentation. Google Cloud Platform (GCP) Similarly, Google provides structured training templates designed to help engineers integrate Terraform into their cloud workflows: Google Cloud Terraform Course. Amazon Web Services (AWS) Interestingly, while Microsoft and Google provide official, structured courses, AWS focuses primarily on prescriptive guidance and documentation. Their approach centers on helping users choose the right tool for their environments: AWS Prescriptive Guidance. ...

For IT professionals managing infrastructure, IaaS (Infrastructure as a Service) established the foundation for programmable infrastructure delivery. Over time, however, the industry has increasingly shifted toward IaC (Infrastructure as Code) as the operational model for managing modern cloud environments. What is IaC? Infrastructure as Code (IaC) applies declarative, version-controlled workflows to infrastructure in much the same way Kubernetes applies them to application orchestration. Instead of manually provisioning servers, networks, and storage through a dashboard, engineers define infrastructure in code. These configurations can then be deployed, destroyed, modified, and recreated repeatedly through automation tools and CLI workflows. ...

Disaster Recovery Planning (DRP) is governed by specific operational constraints: media type, backup frequency, hardware lifecycle management, and allocated maintenance windows. These variables define the necessary budget before a recovery plan is structured. The system logic is then calculated through two primary metrics: RPO (Recovery Point Objective) and RTO (Recovery Time Objective). 1. Defining the Metrics RPO (Recovery Point Objective): The Data Loss Limit RPO defines the maximum age of files that must be recovered from backup for operations to resume. It answers the question: “How much data can we afford to lose?” ...

OSINT (Open Source Intelligence) is the systematic collection and analysis of publicly available data. To the untrained eye, a LinkedIn post or a public GitHub repository is harmless. To a systematic analyst, it is a blueprint for an attack. 1. What is OSINT? OSINT is the practice of collecting and analyzing information that is legally and publicly available. In the context of security, we treat OSINT as the “External System View.” ...

What is CVSS, and why does it matter? The Common Vulnerability Scoring System (CVSS) is the universal language of security. It provides a numerical score (0-10) to help IT and security teams prioritize which holes to plug first. In a business context, CVSS is a “triage” system. Without it, teams have no objective way to prioritize patches, leading to wasted resources on low-risk bugs while critical threats remain unaddressed. The Four Pillars of Calculation Logic A CVSS score is built from specific metric groups that move from the technical “vacuum” to the reality of your business environment. ...

This is the decalaration that we move from wordpress to SSG (Static Site Generator) era. As far as I know Wordpress is very bloat. you need to add many tools to make it usable in the way it should. For the site like gfxtm that never need to be. Hugo is website generator that runs on Go lang, it’s very lisgtning fast on generate the website, I use hugo on my own three website. gfxtm rathwjj and possibe. ...