diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index de38a0b821..9c102a1f76 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -93,12 +93,11 @@ ** xref:upgrade:k-compatibility.adoc[] ** xref:manage:kubernetes/k-upgrade-kubernetes.adoc[Migrate Node Pools] ** xref:upgrade:deprecated/index.adoc[Deprecated Features] -** xref:upgrade:migrate/index.adoc[Migrate] -*** xref:upgrade:migrate/console-v3.adoc[Migrate to Redpanda Console v3.0.x] -*** xref:upgrade:migrate/data-migration.adoc[] -*** xref:upgrade:migrate/kubernetes/helm-to-operator.adoc[] -*** xref:upgrade:migrate/kubernetes/operator.adoc[] -*** xref:upgrade:migrate/kubernetes/strimzi.adoc[] +* xref:migrate:index.adoc[Migrate] +** xref:migrate:console-v3.adoc[Migrate to Redpanda Console v3.0.x] +** xref:migrate:data-migration.adoc[] +** xref:migrate:kubernetes/helm-to-operator.adoc[] +** xref:migrate:kubernetes/strimzi.adoc[] * xref:manage:index.adoc[Manage] ** xref:manage:kubernetes/index.adoc[Kubernetes] *** xref:manage:kubernetes/k-configure-helm-chart.adoc[Customize the Helm Chart] diff --git a/modules/deploy/pages/deployment-option/self-hosted/kubernetes/k-deployment-overview.adoc b/modules/deploy/pages/deployment-option/self-hosted/kubernetes/k-deployment-overview.adoc index d3b8627397..8ec6391e77 100644 --- a/modules/deploy/pages/deployment-option/self-hosted/kubernetes/k-deployment-overview.adoc +++ b/modules/deploy/pages/deployment-option/self-hosted/kubernetes/k-deployment-overview.adoc @@ -45,7 +45,7 @@ To deploy Redpanda in Kubernetes, you can choose between Helm for its simplicity |=== -TIP: If you are already using the Redpanda Helm chart and want to migrate to the latest Redpanda Operator for better lifecycle management, see xref:upgrade:migrate/kubernetes/helm-to-operator.adoc[Migrate from the Redpanda Helm chart]. +TIP: If you are already using the Redpanda Helm chart and want to migrate to the latest Redpanda Operator for better lifecycle management, see xref:migrate:kubernetes/helm-to-operator.adoc[Migrate from the Redpanda Helm chart]. [[helm-and-redpanda-operator]] === Redpanda Operator diff --git a/modules/deploy/pages/deployment-option/self-hosted/manual/production/production-readiness.adoc b/modules/deploy/pages/deployment-option/self-hosted/manual/production/production-readiness.adoc index c4e07a4a58..3cfe2ff247 100644 --- a/modules/deploy/pages/deployment-option/self-hosted/manual/production/production-readiness.adoc +++ b/modules/deploy/pages/deployment-option/self-hosted/manual/production/production-readiness.adoc @@ -493,7 +493,7 @@ rpk cluster config set default_topic_replications=3 ---- -See also: xref:upgrade:migrate/data-migration.adoc#change-topic-replication-factor[Change topic replication factor] +See also: xref:migrate:data-migration.adoc#change-topic-replication-factor[Change topic replication factor] [[maintenance-mode]] === No brokers in maintenance mode @@ -631,7 +631,7 @@ Check that you have a backup and disaster recovery (DR) solution in place. You c Be sure to confirm that the backup and DR solution has been tested. -For disaster recovery, confirm that a standby cluster is configured and running with replication (such as xref:upgrade:migrate/data-migration.adoc[MirrorMaker2]). Also verify that your monitoring ensures that MirrorMaker2 is running and checks replication traffic. See https://redpanda.com/blog/high-availability-software-deployment-patterns-part-1[High-availability deployment of Redpanda: Patterns and considerations^] for more details about HA and DR options. +For disaster recovery, confirm that a standby cluster is configured and running with replication (such as xref:migrate:data-migration.adoc[MirrorMaker2]). Also verify that your monitoring ensures that MirrorMaker2 is running and checks replication traffic. See https://redpanda.com/blog/high-availability-software-deployment-patterns-part-1[High-availability deployment of Redpanda: Patterns and considerations^] for more details about HA and DR options. === Deployment automation diff --git a/modules/get-started/pages/release-notes/redpanda.adoc b/modules/get-started/pages/release-notes/redpanda.adoc index b07676169f..c4c26c14e1 100644 --- a/modules/get-started/pages/release-notes/redpanda.adoc +++ b/modules/get-started/pages/release-notes/redpanda.adoc @@ -54,7 +54,7 @@ See xref:console:config/security/authentication.adoc[] for more information. * **Console settings:** - Moved `console.maxDeserializationPayloadSize` to `serde.maxDeserializationPayloadSize`. -*Action required*: xref:upgrade:migrate/console-v3.adoc[]. +*Action required*: xref:migrate:console-v3.adoc[]. === Other changes diff --git a/modules/manage/partials/whole-cluster-restore.adoc b/modules/manage/partials/whole-cluster-restore.adoc index ad951f7910..9e61be41d2 100644 --- a/modules/manage/partials/whole-cluster-restore.adoc +++ b/modules/manage/partials/whole-cluster-restore.adoc @@ -12,7 +12,7 @@ endif::[] include::shared:partial$enterprise-license.adoc[] ==== -With xref:{link-tiered-storage}[Tiered Storage] enabled, you can use Whole Cluster Restore to restore data from a failed cluster (source cluster), including its metadata, onto a new cluster (target cluster). This is a simpler and cheaper alternative to active-active replication, for example with xref:upgrade:migrate/data-migration.adoc[MirrorMaker 2]. Use this recovery method to restore your application to the latest functional state as quickly as possible. +With xref:{link-tiered-storage}[Tiered Storage] enabled, you can use Whole Cluster Restore to restore data from a failed cluster (source cluster), including its metadata, onto a new cluster (target cluster). This is a simpler and cheaper alternative to active-active replication, for example with xref:migrate:data-migration.adoc[MirrorMaker 2]. Use this recovery method to restore your application to the latest functional state as quickly as possible. [CAUTION] ==== diff --git a/modules/upgrade/pages/migrate/console-v3.adoc b/modules/migrate/pages/console-v3.adoc similarity index 99% rename from modules/upgrade/pages/migrate/console-v3.adoc rename to modules/migrate/pages/console-v3.adoc index c4f86ce2b0..cacb98e022 100644 --- a/modules/upgrade/pages/migrate/console-v3.adoc +++ b/modules/migrate/pages/console-v3.adoc @@ -1,6 +1,7 @@ = Migrate to Redpanda Console v3.0.0 :page-console-config-migrator: true :page-role: enable-ace-editor +:page-aliases: upgrade:migrate/console-v3.adoc This guide provides step-by-step instructions for migrating from Redpanda Console v2.x.x (v2) to v3.0.x (v3). The new release introduces user impersonation to unify authentication and authorization between Redpanda Console and Redpanda, along with several breaking changes. This guide explains these changes and provides examples to help you update your configuration. diff --git a/modules/upgrade/pages/migrate/data-migration.adoc b/modules/migrate/pages/data-migration.adoc similarity index 99% rename from modules/upgrade/pages/migrate/data-migration.adoc rename to modules/migrate/pages/data-migration.adoc index 117ef34e43..8719eef242 100644 --- a/modules/upgrade/pages/migrate/data-migration.adoc +++ b/modules/migrate/pages/data-migration.adoc @@ -1,6 +1,6 @@ = Migrate Data to Redpanda with MirrorMaker 2 :description: Use MirrorMaker 2 to replicate data between Redpanda clusters. -:page-aliases: data-management:data-migration.adoc, manage:data-migration.adoc +:page-aliases: data-management:data-migration.adoc, manage:data-migration.adoc, upgrade:migrate/data-migration.adoc :page-categories: Upgrades, Migration When you want to migrate data from Kafka or replicate data between Redpanda clusters, you can use the MirrorMaker 2 (MM2) tool bundled in the Kafka download package. This section describes the process of configuring MirrorMaker 2 to replicate data from one Redpanda cluster to another. diff --git a/modules/upgrade/pages/migrate/index.adoc b/modules/migrate/pages/index.adoc similarity index 80% rename from modules/upgrade/pages/migrate/index.adoc rename to modules/migrate/pages/index.adoc index 9ec1a9d3db..e23f7b967d 100644 --- a/modules/upgrade/pages/migrate/index.adoc +++ b/modules/migrate/pages/index.adoc @@ -1,5 +1,6 @@ = Migrate :description: Find guidance on migrating to new features or from deprecated features to newer versions. :page-layout: index +:page-aliases: upgrade:migrate/index.adoc :page-categories: Upgrades, Migration diff --git a/modules/upgrade/pages/migrate/kubernetes/helm-to-operator.adoc b/modules/migrate/pages/kubernetes/helm-to-operator.adoc similarity index 99% rename from modules/upgrade/pages/migrate/kubernetes/helm-to-operator.adoc rename to modules/migrate/pages/kubernetes/helm-to-operator.adoc index ab168a2852..15a03c2d6c 100644 --- a/modules/upgrade/pages/migrate/kubernetes/helm-to-operator.adoc +++ b/modules/migrate/pages/kubernetes/helm-to-operator.adoc @@ -2,6 +2,7 @@ :description: If you are using the Redpanda Helm chart, you can migrate to the Redpanda Operator and use it to manage your deployment. :page-categories: Upgrades, Migration :env-kubernetes: true +:page-aliases: upgrade:migrate/kubernetes/helm-to-operator.adoc If you are using the Redpanda Helm chart, you can migrate to the Redpanda Operator and use it to manage your Helm deployment. diff --git a/modules/upgrade/pages/migrate/kubernetes/strimzi.adoc b/modules/migrate/pages/kubernetes/strimzi.adoc similarity index 99% rename from modules/upgrade/pages/migrate/kubernetes/strimzi.adoc rename to modules/migrate/pages/kubernetes/strimzi.adoc index bf18072f12..1fee651b7b 100644 --- a/modules/upgrade/pages/migrate/kubernetes/strimzi.adoc +++ b/modules/migrate/pages/kubernetes/strimzi.adoc @@ -1,5 +1,6 @@ = Migrate from Strimzi to Redpanda Operator :description: This guide explores the migration from Strimzi to Redpanda Operator, highlighting key differences, deployment strategies, and how to leverage Kubernetes for managing Kafka clusters effectively. +:page-aliases: upgrade:migrate/kubernetes/strimzi.adoc :env-kubernetes: true :page-categories: Migration :strimzi-version: 0.40.0 diff --git a/modules/shared/partials/operator-deprecation-notice.adoc b/modules/shared/partials/operator-deprecation-notice.adoc index d40f10712b..d5d61af1bf 100644 --- a/modules/shared/partials/operator-deprecation-notice.adoc +++ b/modules/shared/partials/operator-deprecation-notice.adoc @@ -1,3 +1,3 @@ {badge-deprecated} -IMPORTANT: The Cluster and Console resources are deprecated. For details, see the xref:upgrade:deprecated/cluster-resource.adoc[deprecation notice]. To migrate to the Redpanda resource, see xref:upgrade:migrate/kubernetes/operator.adoc[] \ No newline at end of file +IMPORTANT: The Cluster and Console resources are deprecated. For details, see the xref:upgrade:deprecated/cluster-resource.adoc[deprecation notice]. \ No newline at end of file diff --git a/modules/upgrade/pages/deprecated/index.adoc b/modules/upgrade/pages/deprecated/index.adoc index 2cc45b9080..8733d9bd36 100644 --- a/modules/upgrade/pages/deprecated/index.adoc +++ b/modules/upgrade/pages/deprecated/index.adoc @@ -269,7 +269,7 @@ ifndef::env-cloud[] This section lists all deprecated configuration options and features related to Redpanda Console. Review these deprecations and update your configurations accordingly to ensure compatibility with v3.0.0 and beyond. -See xref:upgrade:migrate/console-v3.adoc[]. +See xref:migrate:console-v3.adoc[]. [cols="1a,2a,3a"] |=== diff --git a/modules/upgrade/pages/rolling-upgrade.adoc b/modules/upgrade/pages/rolling-upgrade.adoc index a2efa70fb2..e5c394df0a 100644 --- a/modules/upgrade/pages/rolling-upgrade.adoc +++ b/modules/upgrade/pages/rolling-upgrade.adoc @@ -107,7 +107,7 @@ include::partial$rolling-upgrades/post-upgrade-tasks.adoc[] == Upgrade Redpanda Console -Before upgrading to Console v3.0.x, xref:upgrade:migrate/console-v3.adoc[review the migration guide] to address breaking changes. +Before upgrading to Console v3.0.x, xref:migrate:console-v3.adoc[review the migration guide] to address breaking changes. [tabs] ====== diff --git a/modules/upgrade/partials/incompat-changes.adoc b/modules/upgrade/partials/incompat-changes.adoc index ce5f25b523..f28d230a12 100644 --- a/modules/upgrade/partials/incompat-changes.adoc +++ b/modules/upgrade/partials/incompat-changes.adoc @@ -1,6 +1,6 @@ === Review incompatible changes -* Redpanda Console v3.0.0 introduces breaking changes. If you are using Redpanda Console v2.x, xref:upgrade:migrate/console-v3.adoc[review the migration guide] to address breaking changes before upgrading Redpanda Console. +* Redpanda Console v3.0.0 introduces breaking changes. If you are using Redpanda Console v2.x, xref:migrate:console-v3.adoc[review the migration guide] to address breaking changes before upgrading Redpanda Console. * Starting in version 24.2, when managing configuration properties using the AlterConfigs API directly, Redpanda resets all unspecified values to the default values. This aligns more closely with the behavior in Apache Kafka. There is no change if you're managing your configuration with tools like `rpk`, Redpanda Console, Kubernetes, Helm, or Terraform. +