Understand technologies in context.

Ansible · Technical documentation · English

Architecture: Ansible

This architecture reference explains Ansible as an agentless, inventory-based automation model. It separates control node, managed nodes, inventory, playbooks, modules, plugins, roles, collections, Vault, Runner, AWX, and execution envir…

Open document ↗ Ansible · Technical documentation · English

Best Practices: Ansible

This file summarizes proven working practices for Ansible projects. It separates technical recommendations, review rules, security requirements, and operational maturity.

Open document ↗ Ansible · Technical documentation · English

Command Reference: Ansible

This command reference describes important Ansible commands, safe usage, and common diagnostic flows. It does not replace --help; it explains usage in the workshop and operations model.

Open document ↗ Ansible · Technical documentation · English

Concepts: Ansible

This concept reference collects the terms used across all workshop levels. It is written as a practical reference, not marketing material.

Open document ↗ Ansible · Technical documentation · English

Curriculum: Ansible

This curriculum structures the Ansible workshop from entry level to advanced operations and security review. It is designed for multi-day trainings, internal enablement tracks, and self-study.

Open document ↗ Ansible · Technical documentation · English

Diagrams: Ansible

This file contains text-based diagrams for architecture, execution flow, role model, variable flow, secret flow, CI, and security review. Diagrams are written in Mermaid and stay versionable.

Open document ↗ Ansible · Technical documentation · English

Operations: Ansible

This operations reference describes how Ansible automation becomes plannable, observable, and reversible. It covers runbooks, evidence, rollouts, troubleshooting, and responsibilities.

Open document ↗ Ansible · Technical documentation · English

Remote and Cloud Environments: Ansible

This guide describes safe use of prepared remote hosts or cloud instances. Ansible configures target systems; cloud provisioning is separated from Terraform/OpenTofu or provider-native APIs.

Open document ↗ Ansible · Technical documentation · English

Security: Ansible

This security reference treats Ansible as a privileged change path. It focuses on scope control, least privilege, secrets, supply chain, logs, CI, and platform operation.

Open document ↗ Ansible · Technical documentation · English

Troubleshooting: Ansible

This troubleshooting reference groups common failure modes by source: configuration, inventory, connection, Python, privileges, variables, modules, idempotence, Vault, collections, and CI.

Open document ↗ Ansible · Technical documentation · English

Ubuntu in a VM: Ansible

This guide describes an Ubuntu VM as a reproducible Ansible lab environment. A VM is the preferred environment for realistic managed-node exercises.

Open document ↗ Ansible · Technical documentation · English

Ubuntu on Bare Metal: Ansible

This guide describes bare-metal Ubuntu as an Ansible lab. Bare metal is useful when hardware, services, networking, or performance should be studied realistically.

Open document ↗ Ansible · Technical documentation · English

Ubuntu on WSL: Ansible

This guide prepares an Ubuntu WSL environment as an Ansible control node. WSL is suitable for CLI, inventory, playbook, role, and many local lab tasks.

Open document ↗ Certificate Authority · Technical documentation · English

Architecture: Certificate Authority

PKI Trust Model is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Best Practices: Certificate Authority

PKI Design is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Command Reference: Certificate Authority

OpenSSL Ground Rules is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Concepts: Certificate Authority

X.509 is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Curriculum: Certificate Authority

Curriculum Goal is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Diagrams: Certificate Authority

Overall Architecture is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Operations: Certificate Authority

Operating Model is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Remote and Cloud Environments: Certificate Authority

Purpose is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Security: Certificate Authority

Threat Model is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Troubleshooting: Certificate Authority

Diagnostic Sequence is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Ubuntu in a VM: Certificate Authority

Purpose is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Ubuntu on Bare Metal: Certificate Authority

Purpose is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ Certificate Authority · Technical documentation · English

Ubuntu on WSL: Certificate Authority

Purpose is treated as a reviewable PKI building block. The important point is not merely that a command creates a certificate, but that purpose, extensions, trust chain, validity, key usage, and cleanup are understandable.

Open document ↗ containerd · Technical documentation · English

Architecture: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗ containerd · Technical documentation · English

Bare Metal Environment: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗ containerd · Technical documentation · English

Best Practices: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗ containerd · Technical documentation · English

Cloud Environment: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗ containerd · Technical documentation · English

Command Reference: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗ containerd · Technical documentation · English

Concepts: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗ containerd · Technical documentation · English

Curriculum: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗ containerd · Technical documentation · English

Diagrams: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗ containerd · Technical documentation · English

Operations: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗ containerd · Technical documentation · English

Security: containerd

Scope is treated as a reviewable containerd building block in this workshop. The relevant point is not just a command, but its position in the daemon, API, plugin, snapshotter, runtime, CRI or Kubernetes node layer.

Open document ↗