Add FAQs to Documentation

[mbrow137]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Adds a place for FAQs and answers a few as well

Release note:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mbrow137 / name: Morgan B. (14cf33e, f24fe82)

[k8s-ci-robot]

Welcome @mbrow137!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-azure 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-azure has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @mbrow137. 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.

[mboersma]

/ok-to-test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.66%. Comparing base (a369783) to head (14cf33e).
Report is 27 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5193      +/-   ##
==========================================
+ Coverage   51.35%   52.66%   +1.30%     
==========================================
  Files         273      273              
  Lines       24671    29189    +4518     
==========================================
+ Hits        12670    15371    +2701     
- Misses      11212    13029    +1817     
  Partials      789      789              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mboersma]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 2deb2af4302bf569cfc2d73d7bdcabb191d0b71c

[mboersma]

/hold

@mbrow137 can you squash the commits so there's only one?

[mboersma]

/label tide/merge-method-squash
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mboersma

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mboersma]

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

[mboersma]

/release-note-none
/hold cancel