From 4a6026d9d439680fbd2136eeabb83df22c84f2aa Mon Sep 17 00:00:00 2001 From: mateczagany Date: Mon, 21 Oct 2024 14:42:03 +0200 Subject: [PATCH] [hotfix][docs] Add FlinkStateSnapshot to upgrade docs --- docs/content/docs/operations/upgrade.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/content/docs/operations/upgrade.md b/docs/content/docs/operations/upgrade.md index e9b7ec922d..70987d81e5 100644 --- a/docs/content/docs/operations/upgrade.md +++ b/docs/content/docs/operations/upgrade.md @@ -51,16 +51,18 @@ backwards-compatible with the previous minor version of the operator. ### 2. Upgrading the CRD -The first step of the upgrade process is upgrading the CRDs for `FlinkDeployment` and `FlinkSessionJob` resources. +The first step of the upgrade process is upgrading the CRDs for `FlinkDeployment`, `FlinkSessionJob` and `FlinkStateSnapshot` resources. This step must be completed manually and is not part of the helm installation logic. ```sh kubectl replace -f helm/flink-kubernetes-operator/crds/flinkdeployments.flink.apache.org-v1.yml kubectl replace -f helm/flink-kubernetes-operator/crds/flinksessionjobs.flink.apache.org-v1.yml +kubectl replace -f helm/flink-kubernetes-operator/crds/flinkstatesnapshots.flink.apache.org-v1.yml ``` {{< hint danger >}} Please note that we are using the `replace` command here which ensures that running deployments are unaffected. +If the CRD does not exist yet, you will get an error and you should try `kubectl apply` instead. {{< /hint >}} ### 3. Upgrading the Helm deployment