Add disk encryption options documentation

[bryan-cox]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
This PR reorganizes the disk pages into their own section and adds a new documentation section discussing disk encryption options.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
N/A

Special notes for your reviewer:

• cherry-pick candidate

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

Reorganized the disk pages into their own section and added a new documentation section discussing disk encryption options.

[k8s-ci-robot]

Welcome @bryan-cox!

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 @bryan-cox. 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/test-infra repository.

[bryan-cox]

Happy to squash those two commits into one. Just left them separate for now for peer review.

[mboersma]

/ok-to-test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1845be1) 61.91% compared to head (1777054) 61.96%.
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4415      +/-   ##
==========================================
+ Coverage   61.91%   61.96%   +0.05%     
==========================================
  Files         188      188              
  Lines       18725    18761      +36     
==========================================
+ Hits        11593    11625      +32     
- Misses       6494     6498       +4     
  Partials      638      638              

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

[mboersma]

This is great @bryan-cox, thank you! I just had a few nitpicks.

[bryan-cox]

@mboersma -Thanks for the feedback! I've addressed all the comments. Just let me know when you think it's good to go and I'll squash them all into one commit.

[mboersma]

/lgtm

Squash whenever time permits and I'm happy to approve this PR.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 947d63791074089f7bfefd3d3b0bf4b532368430

[bryan-cox]

Commits are all squashed now.

[mboersma]

/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