[
https://issues.apache.org/jira/browse/FLINK-26811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518603#comment-17518603
]
Gyula Fora commented on FLINK-26811:
------------------------------------
I think we need to document a few things here:
1. The regular CRD upgrade process that you mentioned, but also note that
because the CRD is large kubectly apply might not work and we probably need to
use kubectly replace instead. We need to highlight that users should never
delete the CRD in order to not lose running jobs.
2. Since we are still in experimental/preview phase and we will completely
remove the v1alpha1 version (see
[https://github.com/apache/flink-kubernetes-operator/pull/159)] We need to tell
users how to migrate between non-compatible versions. Suspend jobs with
savepoint -> delete all flinkdeployments -> update CRD -> create deployments
using new api version
> Document CRD upgrade process
> ----------------------------
>
> Key: FLINK-26811
> URL: https://issues.apache.org/jira/browse/FLINK-26811
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Thomas Weise
> Priority: Major
> Fix For: kubernetes-operator-0.1.0
>
>
> We need to document how to update the CRD with a newer version. During
> development, we delete the old CRD and create it from scratch. In an
> environment with existing deployments that isn't possible, as deleting the
> CRD would wipe out all existing CRs.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
