Deprecation Policy
Understanding ACK's deprecation process and timeline
Deprecation Policy
The AWS Controllers for Kubernetes (ACK) project follows a structured deprecation process to ensure users have adequate time to migrate to new features.
Deprecation Timeline
ACK follows a structured 3-month deprecation process to ensure users have adequate time for migration:
| Phase | Duration | Description | Actions |
|---|---|---|---|
| Announcement | Month 1 | Official deprecation announcement | • Public announcement via GitHub issue • Documentation updated with deprecation notices • Migration guidance provided |
| Deprecation | Months 1-3 | Feature marked deprecated with warnings | • Feature turned off by default • Alternative features promoted to higher stability • Community migration support provided |
| Removal | End of Month 3 | Complete feature removal | • Feature completely removed from codebase • CRDs and related resources deleted • Alternative features reach production readiness • Final migration deadline |
Current Deprecations
Deprecation Notice
The following features are deprecated and will be removed on October 31, 2024:
| Feature | Status | Replacement |
|---|---|---|
| FieldExport CRD | Deprecated Removal: Oct 31, 2024 | KRO (Kubernetes Resource Orchestrator) |
| AdoptedResource CRD | Deprecated Removal: Oct 31, 2024 | ResourceAdoption via annotations |
Feature Graduations
| Feature | Current Status | Next Milestone | Info |
|---|---|---|---|
| ResourceAdoption | Beta (July 2025) | GA: October 2025 | Replacement for AdoptedResource CRD |
| ReadOnlyResources | Beta (July 2025) | GA: October 2025 | - |
Getting Help
If you need assistance with migration:
- Check the ACK Community Discussions
- File an issue in the ACK Community repository