All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Grafana operator dependency has been updated to bring in up to date data structs.
- Alerts updated to support Openshift 4.8.
- New field databaseSecret to UnifiedPushServer CRD spec.
- Logic that cleans up DeploymentConfigs & ImageStreams after migration
- Reduced permissions given to operator SA, since it no longer uses DC/IS
- Re-add POSTGRES_VERSION to secret to allow backup jobs to succeed again
- UnifiedPushDatabaseDown alert always fired if using external database
- UnifiedpushServer CRs can contain coordinates for an external PostgreSQL database
- UnifiedpushServer CR status block has more useful information
- Operator SA permissions are limited to the namespace now, no cluster permissions are given
- Operator creates the Monitoring Resources (GrafanaDashboard, PrometheusRule and ServiceMonitor) on creation of the UnifiedPushServer CR.
- Operator creates its own Monitoring Resources (GrafanaDashboard, PrometheusRule) on installation.
- This version of the operator no longer deals with the PushApplication or *Variant CRDs
- Use Deployments instead of DeploymentConfigs
- Use static image references instead of ImageStreams
- Delete old resources that were created by the previous versions of the operator (DeploymentConfig and ImageStreams)
PushApplication
,AndroidVariant
, andIOSVariant
all now store their relevant IDs (from UPS) as annotations in their CRs.
- Some values received from UPS (notably
MasterSecret
forPushApplication
,Secret
for "variant" kinds), will now be updated in the CR Status if they're "renewed" throught the UPS Admin UI. This update may take some time (next sync interval, since there's no event to trigger immediate reconciliation).
- The ID fields in the Status block (
PushApplicationId
,VariantId
) currently only exist for compatibility, and are likely to be removed in a future version.
- Added resource limits for UPS Server, oauthproxy, and postgres pods
- Fixed an issue where enmasse resources would be cached in a bad state
- Made delete methods in UPS client package idempotent
- Added step to the SOP to re-deploy UPS & PostgreSQL
- Initial implementation of the unifiedpush-operator
UnifiedPushServer
kind to deploy a UPS deployment (only one supported)PushApplication
kind to create an application in your UPS deploymentAndroidVariant
kind to create an Android variant for an applicationIOSVariant
kind to create an iOS variant for an application