Add Coder 2.24.1 to 2.25.0 upgrade bundle spec

[Azahorscak]

Checklist

• I have signed the CLA
• I have updated/added any relevant documentation

Description

What's the goal of this PR?

This PR adds a comprehensive GoNoGo bundle specification for evaluating the upgrade confidence from Coder version 2.24.1 to 2.25.0. This bundle helps administrators assess their readiness to upgrade by checking for compatibility issues, breaking changes, and required actions before performing the upgrade.

What changes did you make?

1. Added Coder bundle spec (pkg/bundle/bundles/coder.yaml):

   • Version range: 2.24.1 → 2.25.0
   • Helm chart source: https://helm.coder.com/v2
   • Kubernetes compatibility: 1.19 - 1.36
   • 12 comprehensive warnings covering breaking changes and new features

2. Implemented 4 OPA policy checks:

   • Connection Log Retention Configuration: Warns if retention policy is not configured for new connection logs
   • PostgreSQL Version Compatibility: Ensures PostgreSQL 11+ is being used
   • Audit Log Backup Warning: Alerts about connection events being deleted from audit log (90+ days old)
   • Non-Interactive Workflow Compatibility: Identifies automated workflows that may break due to preset flag changes

3. Added comprehensive documentation (examples/coder-upgrade-example.md):

   • Detailed explanation of breaking changes in v2.25.0
   • Pre-upgrade checklist
   • Usage examples
   • Troubleshooting guide
   • Links to official Coder documentation

Key Features Covered

Breaking Changes:

• Connection logs moved from Audit Log to new Connection Log entity
• CLI --preset flag now required for templates with presets (breaks non-interactive workflows)
• Workspace update behavior change (stop → start instead of in-place update)
• Audit log cleanup for old connection events

New Features:

• Dynamic Parameters GA (immutable parameters, masking, search)
• DevContainer integration improvements (auto-detect, auto-start)
• OAuth2 provider (experimental)
• External MCP server for AI agents (experimental)
• New Connection Logs page and API

What alternative solution should we consider, if any?

Alternative approaches considered:

1. Single combined warning: Could combine all warnings into one, but individual warnings provide better granularity for users to track which issues they've addressed.
2. Separate bundles per major feature: Could create separate bundles for connection logs, presets, etc., but a unified bundle provides a better holistic view of the upgrade.
3. More granular OPA checks: Could add more specific checks (e.g., checking for specific annotations, labels), but kept it focused on the most critical upgrade blockers to avoid over-alerting.

The current approach balances comprehensiveness with usability, providing enough detail to guide administrators through the upgrade process without overwhelming them with checks.

References

• Coder v2.25.0 Release Notes
• Coder v2.25 Changelog
• Connection Logs Documentation
• Dynamic Parameters Documentation

Slack Thread

  

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}