I write Kubernetes and cloud infrastructure documentation that your engineering team will actually trust and reference — grounded in your real cluster architecture and operational workflows, not adapted from generic tutorials.
Kubernetes documentation scope: cluster architecture overview (node pools, namespaces, RBAC model, network policy baseline); new service deployment guide (step by step for Helm, Kustomize, or raw manifests — from Dockerfile to running in production); networking reference (ingress configuration, service mesh if applicable, DNS resolution, network policy examples); secrets management guide; horizontal and vertical autoscaling guide; monitoring and alerting reference (how to use Prometheus, Grafana, and Alertmanager for your platform); and namespace onboarding guide for developers shipping new services.
Cloud infrastructure documentation: AWS/GCP/Azure account and OU structure; IAM role model and access request process; VPC architecture and CIDR allocation; CI/CD pipeline developer workflow; Terraform module documentation (inputs, outputs, examples); cloud cost allocation and tagging convention guide; and developer self-service guide for common infrastructure requests.
My platform engineering and DevOps background means the procedures I document are ones I've ran myself.