Directories
¶
| Path | Synopsis |
|---|---|
|
AWS Strategy Setup A utility to abstract the various strategy map ConfigMaps from the service using CRO (RHMI) Problem Statement: - We require an AWS strategy map ConfigMaps to be in place to provide configuration used to provision AWS cloud resources This utility provides the abstraction necessary, provisioning an AWS strategy map We accept start times for maintenance and backup times as a level of abstraction Building the correct maintenance and backup times necessary for AWS Maintenance Window format ddd:hh:mm-ddd:hh:mm Backup/Snapshot Window hh:mm-hh:mm
|
AWS Strategy Setup A utility to abstract the various strategy map ConfigMaps from the service using CRO (RHMI) Problem Statement: - We require an AWS strategy map ConfigMaps to be in place to provide configuration used to provision AWS cloud resources This utility provides the abstraction necessary, provisioning an AWS strategy map We accept start times for maintenance and backup times as a level of abstraction Building the correct maintenance and backup times necessary for AWS Maintenance Window format ddd:hh:mm-ddd:hh:mm Backup/Snapshot Window hh:mm-hh:mm |
|
moq
|
|
|
aws
Cluster VPC and networking setup This file contains functions used to setup additional private sub-networks in an OpenShift cluster VPC The reason this file is required is due to CRO provisioning multi-AZ resources for AWS, even though the cluster it's provisioning resources for could be single AZ Problem statement: - A single-AZ OpenShift cluster exists in a VPC, in a single AZ, which contains a public and a private sub-network - A multi-AZ RDS instance for that OpenShift cluster exists in the same VPC, in at least 2 AZ's which must contain at least a private sub-network - By default, if we try to provision a multi-AZ RDS instance in the cluster VPC it will fail as there is only one private sub-network available in one AZ To allow for this, we must create the missing private sub-networks in the AZ's that the cluster is not provisioned in, so that RDS can successfully provision This file provides functions that help check if a private subnet already exists in an AZ, if it does not, it can create one.
|
Cluster VPC and networking setup This file contains functions used to setup additional private sub-networks in an OpenShift cluster VPC The reason this file is required is due to CRO provisioning multi-AZ resources for AWS, even though the cluster it's provisioning resources for could be single AZ Problem statement: - A single-AZ OpenShift cluster exists in a VPC, in a single AZ, which contains a public and a private sub-network - A multi-AZ RDS instance for that OpenShift cluster exists in the same VPC, in at least 2 AZ's which must contain at least a private sub-network - By default, if we try to provision a multi-AZ RDS instance in the cluster VPC it will fail as there is only one private sub-network available in one AZ To allow for this, we must create the missing private sub-networks in the AZ's that the cluster is not provisioned in, so that RDS can successfully provision This file provides functions that help check if a private subnet already exists in an AZ, if it does not, it can create one. |
Click to show internal directories.
Click to hide internal directories.