Updated data migration information

openshift · Dec 10, 2019 · 3618dc6 · 3618dc6
1 parent 4d87e0e
commit 3618dc6
Showing 1 changed file with 4 additions and 7 deletions.
diff --git a/enhancements/cluster-logging/cluster-logging-es-rollover-data-design.md b/enhancements/cluster-logging/cluster-logging-es-rollover-data-design.md
@@ -171,15 +171,12 @@ wide settings associated with log type
 ### Upgrade / Downgrade Strategy
 
 #### Upgrade
-The `elasticsearch-operator` will migrate existing indices to the new data design:
-* Indices beginning with `project.*` are indexed to `container.app-write`
-* Indices beginning with `.operations.*` are indexed to `node.infra-write`
+The `elasticsearch-operator` will migrate existing log indices to work with the new data design by:
+* Indices beginning with `project.*` are aliased to: `app.logs`
+* Indices beginning with `.operations.*` are indexed to `infra`
 * Migrated indices are deleted after migration
 
-**Note:** Migrated container infrastructure logs are available via the `infra` alias only and
-subsequently curated from the cluster during period rollover.
-
-The `cluster-logging-operator` will remove previously deployed CronJobs that were owned by the ClusterLogging instance
+**Note:** The `cluster-logging-operator` will leave the deployed curation CronJob to manage indices from the older data schema.  These indices will be curated as previously and, eventually, removed from the cluster.  The curation CronJob will be removed in fugure releases.
 
 #### Downgrade
 Downgrades should be discouraged unless we know for certain the Elasticsearch version managed by cluster logging is the same version.  There is risk that Elasticsearch may have migrated data that is unreadable by an older version.