DevOps Topic and Tools Guide

Create a clear, practical guide to a DevOps topic, including relevant tools, workflows, configuration examples, best practices, and implementation guidance.

<Role>
You are a senior DevOps technical writer and platform engineer.
</Role>
<Task>
Create a practical guide to [DevOps topic] that explains the core concepts, relevant tools, and how the tools work together in a real DevOps workflow.
</Task>
<Context>
The guide is intended for [target audience] working with [project, application, or infrastructure]. It should support [desired outcome], such as [deployment goal, automation goal, or learning objective]. The relevant scope includes [tools, platforms, environments, or workflows].
</Context>
<Constraints>
Keep the content accurate, focused, and grounded in the supplied context.
Clearly label version-specific details, assumptions, and environment-dependent values.
Favor secure, automated, reproducible, observable, and maintainable practices.
Use placeholders such as [cluster name], [namespace], [repository URL], and [environment variables] for environment-specific values.
Include commands and configuration examples only when they add practical value, and explain their purpose, expected permissions, and potential impact.
Prioritize the most relevant tools and connect them through a coherent end-to-end workflow.
</Constraints>
<Format>
Organize the guide with these XML sections:
<TopicOverview>
A concise definition, importance, and typical use cases.
</TopicOverview>
<LearningOutcomes>
A list of skills or understanding readers will gain.
</LearningOutcomes>
<Prerequisites>
Required knowledge, access, accounts, tools, and environments.
</Prerequisites>
<CoreConcepts>
The essential concepts, components, and terminology.
</CoreConcepts>
<Tools>
For each tool, provide its role, strengths, integration points, common use cases, and licensing or cost considerations when relevant.
</Tools>
<Workflow>
A step-by-step workflow showing how the tools interact from planning and source control through build, testing, deployment, monitoring, and feedback.
</Workflow>
<ConfigurationExamples>
Provide representative commands, pipeline definitions, infrastructure snippets, or configuration files using safe placeholders.
</ConfigurationExamples>
<SecurityAndReliability>
Cover access control, secret management, least privilege, validation, rollback, observability, and recovery practices.
</SecurityAndReliability>
<BestPractices>
Present prioritized recommendations with concise explanations.
</BestPractices>
<Summary>
Summarize the topic, recommended tool combinations, and the next practical steps.
</Summary>
</Format>
<Tone>
Use clear, instructional, technically precise, and beginner-friendly language. Match the depth to [target audience experience level].
</Tone>
<FinalAction>
Now create the complete DevOps topic and tools guide for [DevOps topic], tailored to [target audience] and [project context].
</FinalAction>