You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ted Chang (Jira)" <ji...@apache.org> on 2022/04/06 20:54:00 UTC

[jira] [Comment Edited] (FLINK-26811) Document CRD upgrade process

    [ https://issues.apache.org/jira/browse/FLINK-26811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518463#comment-17518463 ] 

Ted Chang edited comment on FLINK-26811 at 4/6/22 8:53 PM:
-----------------------------------------------------------

[~gyfora] Are we trying to document a generic upgrading strategy, like this [1], for the consumers who deploy the flink-kubernetes-operator in production ?
[1]https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#upgrade-existing-objects-to-a-new-stored-version


was (Author: JIRAUSER287036):
[~gyfora] Are we trying to document a generic upgrading strategy, like this [1], for the consumers who deploy the flink-kubernetes-operator in production ?

> 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)