Goal

• Support configuring azure diagnostics for boot diagnostics on nodepools

Why is this important?

• When a node fails to join the cluster, serial console logs are useful in troubleshooting, especially for managed services. 

Scenarios

1. Customer scales / creates nodepool
   1. nodes created
   2. one or more nodes fail to join the cluster
   3. cannot ssh to nodes because ssh daemon did not come online
   4. Can use diagnosics + managed storage account to fetch serial console logs to troubleshoot

Acceptance Criteria

• Dev - Has a valid enhancement if necessary
• CI - MUST be running successfully with tests automated
• QE - covered in Polarion test plan and tests implemented
• Release Technical Enablement - Must have TE slides
• ...

Dependencies (internal and external)

1. Capz already supports this, so dependency should be on hypershift team implementing this: https://github.com/openshift/cluster-api-provider-azure/blob/master/api/v1beta1/azuremachine_types.go#L117

Previous Work (Optional):

1. …

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical Enablement <link to Feature Enablement Presentation>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Enhancement merged: <link to meaningful PR or GitHub Issue>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>