Add comprehensive next release planning documentation

[Copilot]

This PR addresses the need for structured release planning by creating comprehensive documentation to guide the next major release (v0.7.0) of the Cluster API Provider for CloudStack.

Background

The project currently lacks formal release planning documentation, making it difficult to:

• Prioritize critical issues and features
• Track progress toward release goals
• Communicate requirements to stakeholders
• Ensure consistent quality gates across releases

Changes Made

1. NEXT_RELEASE_MUST_HAVE.md - Primary Release Planning Document

This document provides a complete roadmap for the next release, including:

• Critical Bug Fixes (P0):

  • Issue Unable to deploy a CAPC cluster from a Normal user account #454: CloudStack user account deployment failure preventing normal users from deploying clusters
  • Issue Loadbalancing and firewall rules are not getting deleted when the capc cluster is destroyed. #293: Resource cleanup bug causing load balancer and firewall rule leakage

• High Priority Updates (P1):

  • Issue CAPI v1.11.0-beta.0 has been released and is ready for testing #457: CAPI v1.11.0 compatibility testing and integration
  • Issue Deprecate or Remove kube rbac proxy server in CAPC #446: Kube RBAC proxy port conflicts causing upgrade failures

• Detailed Timeline: 9-13 week estimated delivery with phased approach

• Success Criteria: Clear functional, quality, and performance metrics

• Release Checklist: Comprehensive pre-release and testing requirements

2. DETAILED_ISSUE_ANALYSIS.md - Technical Deep Dive

Provides thorough analysis of all current open issues:

• Priority Matrix: Issues categorized by impact and urgency
• Effort Estimation: Resource requirements and development timelines
• Risk Assessment: Technical and user experience impact analysis
• Dependency Mapping: Relationships between issues and external factors

3. RELEASE_PLANNING_TEMPLATE.md - Future Release Framework

Creates a reusable template for consistent release planning:

• Structured issue tracking and prioritization
• Quality gates and testing requirements
• Timeline and milestone management
• Risk assessment and communication planning

Key Findings

The analysis revealed several critical issues that must be addressed:

1. User Experience Blockers: Issues Unable to deploy a CAPC cluster from a Normal user account #454 and Loadbalancing and firewall rules are not getting deleted when the capc cluster is destroyed. #293 prevent successful deployments for significant user segments
2. Technical Debt: The RBAC proxy conflicts indicate infrastructure complexity that needs simplification
3. Compatibility Requirements: CAPI v1.11.0 support is essential for maintaining project relevance

Impact

This documentation will:

• Enable data-driven release planning decisions
• Improve communication with contributors and users
• Establish consistent quality standards
• Reduce time-to-release through better organization
• Provide historical context for future releases

The structured approach ensures that critical user-facing issues are prioritized while maintaining compatibility with the broader Kubernetes ecosystem.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Copilot

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @Copilot. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-cloudstack ready!

Name	Link
🔨 Latest commit	1d3472b
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-cloudstack/deploys/68b684bd0931200008710a69
😎 Deploy Preview	https://deploy-preview-465--kubernetes-sigs-cluster-api-cloudstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.