Convert rough outline to markdwon

[tjcorr]

Outline of Managing AKS Infrastructure with GitHub and CI/CD:

• Into – Link back to the reference architecture
• Pros of using IaaC vs CLI
• Choosing Bicep vs Terraform
• Pre-reqs -> link it aks-baseline / CAF / hub/spoke
• Managing credentials
  • GitHub Secrets
  • OIDC
• Deploying with GitHub Actions (link to yaml files)
  • Manual? Should this be included?
  • Bicep
  • Terraform
• How to maintain your cluster
  • Upgrading versions
  • Changing pools / machine types
  • PR process / approval pipeline
  • We probably need a some example workflows written see https://github.com/tjcorr/tf-pipeline-demo/blob/main/.github/workflows/terraform.yml for starte TF version
  • Monitoring for drift
• How to scale this to an enterprise (multi-cluster),
• Outro – Link to maintaining cluster configuration with code (gitops / flux)

Target audience: CloudOps person / engineer

[tjcorr]

Feedback:

• [x] Add more details on the value of separating the plan vs apply stage
• [x] Modifiy TF drift pipeline to fail if drift detected
• [x] Add more details on how each separate AKS cluster would have it's own repo/pipeline
• [ ] Create PR to merge in @tjcorr workflows into aks-baseline-automation
• [ ] Make proper diagram in Visio