-
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)
Add support to OpenShift to be deployed into Azure Gov Secret US East region ( DoD IL6 )
Goals (aka. expected user outcomes)
OpenShift can be deployed using full stack automation (IPI) into Azure Gov Secret US East region ( DoD IL6 )
Requirements (aka. Acceptance Criteria):
OpenShift can be deployed using full stack automation (IPI) into Azure Gov Secret US East region ( DoD IL6 )
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 | |
| 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
Palantir, a Red Hat partner that works intensively with cloud government regions is requesting OpenShift to be enabled for the Azure Secret regions starting with Azure Gov Secret US East region ( DoD IL6 )
Documentation Considerations
Specific documentation on how to deploy OpenShift on these special regions will be required
- is related to
-
-
- Accepted
-
