-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
BU Product Work
-
False
-
-
False
-
100% To Do, 0% In Progress, 0% Done
-
0
Feature Overview (aka. Goal Summary)
When deploying OpenShift on Azure all the cluster Nodes are created with OSdisks that have public access by default. This feature will add the option to change this behaviour at install time for every Node in the cluster so the OSdisks are configured as private.
Goals (aka. expected user outcomes)
Allow the user to specify how to publish the OSdisks attached to the OpenShift Nodes at install time when deploying OpenShift on Azure.
Requirements (aka. Acceptance Criteria):
The user will be able to set at install time how OSdisks attached to OpenShift Nodes on Azure are published. By default these are configured as public but the user will have the option to change this behaviour to make the publish value private.
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.
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | Both |
Classic (standalone cluster) | |
Hosted control planes | |
Multi node, Compact (three node), or Single node (SNO), or all | |
Connected / Restricted Network | |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | |
Operator compatibility | |
Backport needed (list applicable versions) | |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | |
Other (please specify) |
Background
ARO customers require VM's disk configuration where the disks are setup for public access as private.
While this request is coming from ARO this will be available to self-manages users as well
Documentation Considerations
Usual documentation on how to use the feature will be required
- is related to
-
RFE-5132 [ARO] Locking down OSDisks to be only accessible to local network (rather than public)
- Accepted