Templates have been migrated to using YAML, for consistency with other projects under the BCDevOps organization.
Updated build configuration to re-enable building containers different than Postgres.
Updated deployment configurations to include starter set of NetworkSecurityPolicies.
Updated deployment configurations to use labeling to group backup-container instances together, by default. This will allow several instances of the backup-container (e.g.: Postgres, SQL Server, MariaDB, MongoDB) to be grouped under the same backup-container app in OpenShift.
Added MariaDB example to default backup.conf.
Some notes:
Regarding above point number 4: it may be a good idea to use suffixes to label different types of build/deployments. I have not (yet) gone down that path, but I think it would be a good idea.
Regarding NetworkSecurityPolicies: I opted to reuse the ENVIRONMENT_NAME environment variable in their definitions in order to reduce the number of environment variables that need to be set and tracked. I think this can be a good pattern for these base NSPs, we could rename ENVIRONMENT_NAME to NAMESPACE or other keyword that would be automatically managed by the scripts when generating param file.
I have an instance (MariaDB) up and running, but additional testing and input is welcome.
backup-containerinstances together, by default. This will allow several instances of thebackup-container(e.g.: Postgres, SQL Server, MariaDB, MongoDB) to be grouped under the samebackup-containerapp in OpenShift.backup.conf.Some notes:
ENVIRONMENT_NAMEenvironment variable in their definitions in order to reduce the number of environment variables that need to be set and tracked. I think this can be a good pattern for these base NSPs, we could renameENVIRONMENT_NAMEtoNAMESPACEor other keyword that would be automatically managed by the scripts when generating param file.I have an instance (MariaDB) up and running, but additional testing and input is welcome.
@WadeBarnes