Feature Overview (aka. Goal Summary)  

Microsoft is planning to  retire default outbound access connectivity for all new virtual machines in Azure. Once this takes effect no Nodes in OCP deployed in Azure will have outbound connectivity unless this is configured explicitely.

This feature will tackle this deprecation notice from Microsoft and plan a long term solution for OpenShift once this new "policy" is applied in Azure

Goals (aka. expected user outcomes)

Find a solution to replace the existing default behaviour today on Azure for VMs outbound traffic that will impact future OpenShift clusters on Azure

Requirements (aka. Acceptance Criteria):

This needs to be solved not only for new OpenShift Clusters but also for existing ones. While existing clusters are not going to be affected straightaway (existing VMs won't loose outbound access) they will get impacted as any new Node added to the cluster won't get outbound access by default.

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Background

https://azure.microsoft.com/en-us/updates/default-outbound-access-for-vms-in-azure-will-be-retired-updates-and-more-information/

Documentation Considerations

Is it not clear yet that user facing documentation would be required after this change