📚 Master Standard Operating Procedures (SOP)
Scope: Polaris IT Solutions Technical Staff
Level: Fleet-Wide (Global Standards)
This directory contains the Master SOPs that govern how we manage infrastructure across all clients. These documents define the standards, naming conventions, and approved tools for our fleet.
📂 Documentation Hierarchy
-
Master SOPs (You are here):
- Defines "How we do things generally" (e.g., "All servers must use NetBird").
- Located in:
sops/(Root of Fleet Controller). - Authority: High. Deviations require approval from the Lead Architect.
-
Client SOPs:
- Defines "How this specific client is configured" (e.g., "Client A uses Port 8080 for their custom app").
- Located in:
clients/<client-name>/docs/. - Authority: Specific. Overrides Master SOPs only where explicitly documented as an exception.
📜 Available Procedures
| SOP | Description |
|---|---|
| Access & Security | How to connect to servers using NetBird VPN and SSH. |
| Docker Stacks | Standards for writing and deploying Docker Compose files. |
| Terraform | Guidelines for provisioning cloud resources and handling state. |
| CI/CD & Automation | Rules for Git workflows and automation pipelines. |
| Kubernetes | (Roadmap) Standards for K8s clusters. |
🛠️ Maintenance
- These documents are "Living Specifications."
- If you find a standard that is obsolete, update the document and notify the team via PR.