Skip to content

Add documentation for AKS Planned Maintenance Windows#11291

Open
MXClyde wants to merge 2 commits into
mendix:developmentfrom
MXClyde:feature/MXFORAZURE-732-aks-maintenance-windows
Open

Add documentation for AKS Planned Maintenance Windows#11291
MXClyde wants to merge 2 commits into
mendix:developmentfrom
MXClyde:feature/MXFORAZURE-732-aks-maintenance-windows

Conversation

@MXClyde
Copy link
Copy Markdown
Contributor

@MXClyde MXClyde commented Jun 2, 2026

Add comprehensive documentation for customer self-configuration of AKS planned maintenance windows via Azure Portal. This enables customers to schedule node OS upgrades and cluster version upgrades during off-peak hours to avoid application pod restarts during business hours.

Changes

  • Add AKS Planned Maintenance Windows to self-service configuration table
  • Add detailed configuration section with recommendations
  • Include step-by-step instructions for Azure Portal configuration
  • Document permission requirements (Owner/Contributor + Cluster Manager)
  • Add best practices: 4-hour minimum, weekly frequency, UTC timezone
  • Reference Microsoft documentation for schedule syntax
  • Clarify distinction from PostgreSQL maintenance windows

Customer Need

Novocure and other enterprise customers need control over when infrastructure upgrades cause pod restarts to minimize business impact.

Related Issues

  • MXFORAZURE-728 (parent story)
  • MXFORAZURE-729 (permissions)
  • MXFORAZURE-730 (Terraform)
  • MXFORAZURE-731 (retroactive refresh)
  • MXFORAZURE-732 (this documentation task)

Testing

Documentation changes only - no code changes required.

Add comprehensive documentation for customer self-configuration of AKS
planned maintenance windows via Azure Portal. This enables customers to
schedule node OS upgrades and cluster version upgrades during off-peak
hours to avoid application pod restarts during business hours.

Changes:
- Add AKS Planned Maintenance Windows to self-service configuration table
- Add detailed configuration section with recommendations
- Include step-by-step instructions for Azure Portal configuration
- Document permission requirements (Owner/Contributor + Cluster Manager)
- Add best practices: 4-hour minimum, weekly frequency, UTC timezone
- Reference Microsoft documentation for schedule syntax
- Clarify distinction from PostgreSQL maintenance windows

Customer request: Novocure and other enterprise customers need control
over when infrastructure upgrades cause pod restarts to minimize
business impact.

Related: MXFORAZURE-728 (parent story), MXFORAZURE-729 (permissions),
MXFORAZURE-730 (Terraform), MXFORAZURE-731 (retroactive refresh)

Fixes: MXFORAZURE-732

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@MXClyde
Copy link
Copy Markdown
Contributor Author

MXClyde commented Jun 2, 2026

This should not be merged until functionality is live.

Fix incorrect permission statement
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant