Merge branch 'main' of github.com:MaterializeInc/materialize into source-table-migration

# Conflicts:
#	test/legacy-upgrade/mzcompose.py

Author: jkosh44

ci/nightly/pipeline.template.yml

@@ -909,6 +909,18 @@ steps:
               composition: platform-checks
               args: [--scenario=UpgradeEntireMz, "--seed=$BUILDKITE_JOB_ID"]
 
+      - id: checks-lts-upgrade
+        label: "Checks LTS upgrade, whole-Mz restart"
+        depends_on: build-aarch64
+        timeout_in_minutes: 180
+        parallelism: 2
+        agents:
+          queue: hetzner-aarch64-16cpu-32gb
+        plugins:
+          - ./ci/plugins/mzcompose:
+              composition: platform-checks
+              args: [--scenario=UpgradeEntireMzFromLatestLTS, "--seed=$BUILDKITE_JOB_ID"]
+
       - id: checks-preflight-check-rollback
         label: "Checks preflight-check and roll back upgrade"
         depends_on: build-aarch64
@@ -1709,7 +1721,7 @@ steps:
         plugins:
           - ./ci/plugins/mzcompose:
               composition: legacy-upgrade
-              args: ["--versions-source=docs"]
+              args: ["--versions-source=docs", "--lts-upgrade"]
         agents:
           queue: hetzner-aarch64-4cpu-8gb
 

doc/user/content/self-managed/_index.md

@@ -7,49 +7,4 @@ robots: "noindex, nofollow"
 draft: true
 ---
 
-With self-managed Materialize, you can deploy and operate Materialize in your
-Kubernetes environment. For self-managed Materialize, Materialize offers:
-
-- A Kubernetes Operator that manages your Materialize running in your Kubernetes
-  environment.
-
-- Materialize packaged as a containerized application that can be deployed in a
-  Kubernetes cluster.
-
-## Requirements
-
-The self-managed Materialize requires the following:
-
-{{% self-managed/requirements-list %}}
-
-See the [Installation guide](/self-managed/installation/) for more information.
-
-## Recommended instance types
-
-Materialize has been tested to work on instances with the following properties:
-
-- ARM-based CPU
-- 1:8 ratio of vCPU to GiB memory
-- 1:16 ratio of vCPU to GiB local instance storage (if enabling spill-to-disk)
-
-For specific cloud provider recommendations, see the [Installation guide for the
-cloud provider](/self-managed/installation/) as well as the [operational guidelines](/self-managed/operational-guidelines/).
-
-## Installation
-
-For instructions on installing Materialize on your Kubernetes cluster, see:
-
-- [Install locally on kind](/self-managed/installation/install-on-local-kind/)
-
-- [Install locally on
-  minikube](/self-managed/installation/install-on-local-minikube/)
-
-- [Install on AWS](/self-managed/installation/install-on-aws/)
-- [Install on GCP](/self-managed/installation/install-on-gcp/)
-
-## Related pages
-
-<!-- Temporary:
-Hugo will add links to the pages in the same folder.
-Since we're hiding this section from the left-hand nav, adding the links here.
--->
+<!-- Note: The self-managed docs are in a separate branch. The self-managed section in main is used for redirect purposes of the pre-LTS (circa Dec. 2024) self-managed docs -->

doc/user/content/self-managed/v25.1/_index.md

@@ -5,44 +5,5 @@ aliases:
   - /self-managed/
 suppress_breadcrumb: true
 ---
-With self-managed Materialize, you can deploy and operate Materialize in your
-Kubernetes environment. For self-managed Materialize, Materialize offers:
 
-- A Kubernetes Operator that manages your Materialize running in your Kubernetes
-  environment.
-
-- Materialize packaged as a containerized application that can be deployed in a
-  Kubernetes cluster.
-
-## Requirements
-
-The self-managed Materialize requires the following:
-
-{{% self-managed/requirements-list %}}
-
-See the [Installation guide](/self-managed/installation/) for more information.
-
-## Recommended instance types
-
-Materialize has been tested to work on instances with the following properties:
-
-- ARM-based CPU
-- 1:8 ratio of vCPU to GiB memory
-- 1:16 ratio of vCPU to GiB local instance storage (if enabling spill-to-disk)
-
-For specific cloud provider recommendations, see the [Installation guide for the
-cloud provider](/self-managed/installation/) as well as the [operational guidelines](/self-managed/operational-guidelines/).
-
-## Installation
-
-For instructions on installing Materialize on your Kubernetes cluster, see:
-
-- [Install locally on kind](/self-managed/installation/install-on-local-kind/)
-
-- [Install locally on
-  minikube](/self-managed/installation/install-on-local-minikube/)
-
-- [Install on AWS](/self-managed/installation/install-on-aws/)
-- [Install on GCP](/self-managed/installation/install-on-gcp/)
-
-## Related pages
+<!-- Note: The self-managed docs are in a separate branch. The self-managed section in main is used for redirect purposes of the pre-LTS (circa Dec. 2024) self-managed docs -->

doc/user/content/self-managed/v25.1/installation/_index.md

@@ -7,35 +7,4 @@ aliases:
 suppress_breadcrumb: true
 ---
 
-You can install self-managed Materialize on a Kubernetes cluster running locally
-or on a cloud provider.
-
-## Install locally
-
-{{< multilinkbox >}}
-{{< linkbox title="Using Docker/kind" >}}
-[Install locally on kind](/self-managed/installation/install-on-local-kind/)
-{{</ linkbox >}}
-{{< linkbox  title="Using Docker/minikube" >}}
-[Install locally on minikube](/self-managed/installation/install-on-local-minikube/)
-{{</ linkbox >}}
-{{</ multilinkbox >}}
-
-## Install on cloud provider
-
-{{< multilinkbox >}}
-{{< linkbox title="AWS" >}}
-[Install on AWS](/self-managed/installation/install-on-aws/)
-{{</ linkbox >}}
-{{< linkbox title="GCP" >}}
-[Install on GCP](/self-managed/installation/install-on-gcp/)
-{{</ linkbox >}}
-{{</ multilinkbox >}}
-
-## See also
-
-- [Materialize Kubernetes Operator Helm Chart](/self-managed/)
-- [Materialize Operator Configuration](/self-managed/configuration/)
-- [Troubleshooting](/self-managed/troubleshooting/)
-- [Operational guidelines](/self-managed/operational-guidelines/)
-- [Upgrading](/self-managed/upgrading/)
+<!-- Note: The self-managed docs are in a separate branch. The self-managed section in main is used for redirect purposes of the pre-LTS (circa Dec. 2024) self-managed docs -->

doc/user/content/self-managed/v25.1/installation/configuration.md

@@ -7,57 +7,4 @@ aliases:
 suppress_breadcrumb: true
 ---
 
-You can configure the Materialize operator chart. For example:
-
-- **RBAC**
-
-  The chart creates a `ClusterRole` and `ClusterRoleBinding` by default.
-
-- **Network Policies**
-
-  Network policies can be enabled by setting
-  [`networkPolicies.enabled=true`](#networkpoliciesenabled).
-  By default, the chart uses native Kubernetes network policies. For additional network policy configuration options, see [`networkPolicies` parameters](#networkpolicies-parameters).
-
-- **Observability**
-
-  To enable observability features, set
-  [`observability.enabled=true`](#observabilityenabled).
-  This will create the necessary resources for monitoring the operator. For
-  additional observability configuraiton options, see [`observability`
-  parameters](#observability-parameters).
-
-## Configure the Materialize operator chart
-
-To configure the Materialize operator chart, you can:
-
-- *Recommended:* Modify the provided  `values.yaml` file (or create your own
-  YAML file) that specifies the configuration values and then install the
-  chart with the `-f` flag:
-
-  ```shell
-  helm install my-materialize-operator -f /path/to/values.yaml /path/to/materialize/helm-charts/operator
-  ```
-
-- Specify each parameter using the `--set key=value[,key=value]` argument to
-  `helm install`. For example:
-
-  ```shell
-  helm install my-materialize-operator \
-    --set operator.image.tag=v1.0.0 \
-    /path/to/materialize/helm-charts/operator
-  ```
-
-{{%  self-managed/materialize-operator-chart-parameters-table %}}
-
-## Parameters
-
-{{%  self-managed/materialize-operator-chart-parameters %}}
-
-## See also
-
-- [Materialize Kubernetes Operator Helm Chart](/self-managed/)
-- [Troubleshooting](/self-managed/troubleshooting/)
-- [Installation](/self-managed/installation/)
-- [Operational guidelines](/self-managed/operational-guidelines/)
-- [Upgrading](/self-managed/upgrading/)
+<!-- Note: The self-managed docs are in a separate branch. The self-managed section in main is used for redirect purposes of the pre-LTS (circa Dec. 2024) self-managed docs -->