Skip to content

Commit 14cf33e

Browse files
committed
Add FAQs
1 parent f24fe82 commit 14cf33e

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

docs/book/src/topics/FAQ.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,13 @@
11
# Frequently Asked Questions
22

33
## Does CAPZ support Feature X?
4-
The best way to check if CAPZ supports a feature is by reviewing [the public milestones](https://github.com/kubernetes-sigs/cluster-api-provider-azure/milestones). The public milestones will also provide insight into what's coming in the
5-
next 1-2 months. All open items for the next milestone are displayed in the [Milestone-Open project board](https://github.com/orgs/kubernetes-sigs/projects/26/views/7), which is updated at the start of each 2-month release cycle. Planning and
6-
discussions for these milestones typically happening during the [Cluster API Azure Office Hours](https://docs.google.com/document/d/1P2FrRjuCZjGy0Yh72lwWCwmXekSEkqliUVTmJy_ETIk/edit?tab=t.0) (every Thursday at 9am PT) after each major
7-
release.
4+
The best way to check if CAPZ supports a feature is by reviewing [the roadmap](https://capz.sigs.k8s.io/roadmap) and [the public milestones](https://github.com/kubernetes-sigs/cluster-api-provider-azure/milestones). The public milestones will
5+
also provide insight into what's coming in the next 1-2 months. All open items for the next milestone are displayed in the [Milestone-Open project board](https://github.com/orgs/kubernetes-sigs/projects/26/views/7), which is updated at the
6+
start of each 2-month release cycle. Planning and discussions for these milestones typically happen during the [Cluster API Azure Office Hours](https://docs.google.com/document/d/1P2FrRjuCZjGy0Yh72lwWCwmXekSEkqliUVTmJy_ETIk/edit?tab=t.0)
7+
(every Thursday at 9am PT) after each major release.
8+
9+
For managed (AKS) clusters, all features should be available when using the AzureASOManaged API specification, which provides 100% API surface coverage via ASO. If there is no issue for a new feature in the repository, it likely does not
10+
exist yet.
811

912
You can also check the [GitHub repository](https://github.com/kubernetes-sigs/cluster-api-provider-azure) issues and milestones for more details on specific features.
1013

@@ -25,7 +28,7 @@ We continuously evaluate and update our roadmap based on user feedback and evolv
2528
## How do I add Feature X to CAPZ?
2629
To add Feature X to CAPZ, consider following these steps:
2730
1. **Review the Roadmap:** Ensure that Feature X aligns with the CAPZ roadmap and that it's not already planned or in development.
28-
2. **Submit an Issue:** Open an issue on our [GitHub Repository](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues) to discuss Feature X with the maintainers and the community. P;ease provid detailed information about the
31+
2. **Submit an Issue:** Open an issue on our [GitHub Repository](https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues) to discuss Feature X with the maintainers and the community. Please provide detailed information about the
2932
feature and its benefits.
3033
3. **Contribute Code:** If you have the capabilities, you can implement Feature X yourself. Fork the repository, develop the feature following our contribution guidelines, and submit a pull request for review.
3134
4. **Collaborate with the Community:** Engage with and receive updates from other contributors and maintainers through our [Slack channel](https://kubernetes.slack.com/messages/CEX9HENG7) or

0 commit comments

Comments
 (0)