Skip to content

Commit 95f94d7

Browse files
authored
Merge pull request #4629 from dtzar/roadmapup
Update roadmap
2 parents 8cbd2ed + 79739c3 commit 95f94d7

File tree

1 file changed

+1
-15
lines changed

1 file changed

+1
-15
lines changed

docs/book/src/roadmap.md

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Cluster API Azure Roadmap
22

33
The best place to see what's coming within a 1-2 month timeline is in [the public milestones](https://github.com/kubernetes-sigs/cluster-api-provider-azure/milestones).
4-
All open items for the the next numbered milestone (e.g. **1.12**) are visualized in the [Milestone-Open project board view](https://github.com/orgs/kubernetes-sigs/projects/26/views/7) and planned at the very beginning of the 2-month release cycle. This planning and discussion begins at [Cluster API Azure Office Hours](http://bit.ly/k8s-capz-agenda) after a major release.
4+
All open items for the the next numbered milestone (e.g. **1.15**) are visualized in the [Milestone-Open project board view](https://github.com/orgs/kubernetes-sigs/projects/26/views/7) and planned at the very beginning of the 2-month release cycle. This planning and discussion begins at [Cluster API Azure Office Hours](http://bit.ly/k8s-capz-agenda) after a major release.
55
Active community PR contributions are prioritized throughout the release, but unplanned work will arise. Hence the items in the milestone are a rough estimate which may change.
66
The "next" milestone is a very rough collection of issues for the milestone after the current numbered one to help prioritize upcoming work.
77

@@ -12,17 +12,3 @@ CAPZ is the official production-ready Cluster API implementation to administer t
1212
## Epics
1313

1414
There are a number of large priority "Epics" which may span across milestones which we believe are important to providing CAPZ users an even better experience and improving the vision. The [CAPZ project board roadmap view](https://github.com/orgs/kubernetes-sigs/projects/26/views/11) tracks the larger "epic issues" and their progress.
15-
16-
- ManagedClusters - Provisioning new AKS (ManagedClusters) clusters at scale is a common use case we want to enable an excellent experience with stability and all of the same features available in AKS. Includes:
17-
- [ClusterClass support](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/2684)
18-
- [Enabling all AKS features](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/3446)
19-
- [Enable AKS preview features](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/2625)
20-
- [Evolution of standardized CAPI ManagedCluster for CAPZ](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20220725-managed-kubernetes.md)
21-
22-
- Latest features for self-managed - These larger or essential features enable a better experience for provisioning self-managed clusters on Azure. Includes:
23-
- [MachinePool autoscale support](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/2328)
24-
- Azure CNI v2 support (waiting on functionality to be available from the Azure Networking team)
25-
26-
- Supported adoption of existing AKS clusters - makes it easier to onboard to the CAPZ/ASO control plane. Includes:
27-
- [BYO nodes on AKS](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/826)
28-
- [Adopt existing AKS clusters](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/1173)

0 commit comments

Comments
 (0)