[
https://issues.apache.org/jira/browse/FLINK-27065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora updated FLINK-27065:
-------------------------------
Description:
Currently we store complete spec objects in the status. This leads to large CRD
schema sizes and will probably cause big headaches when implementing migration
logic from one api version to the other.
We suggest to store the lastReconciledSpec in String form instead. This will
also make it easier to store new spec copies for the rollback logic also.
Later when we want to support multiple versions this will allow us to handle
ser/de logic programmatically and not cause problems on the kubernetes side.
was:
Currently we store complete spec objects in the status. This leads to large CRD
schema sizes and will probably cause big headaches when implementing migration
logic from one api version to the other.
We suggest to store the lastReconciledSpec in String form instead. This will
also make it easier to store new spec copies for the rollback logic also.
> Store lastReconciledSpec as String in status
> --------------------------------------------
>
> Key: FLINK-27065
> URL: https://issues.apache.org/jira/browse/FLINK-27065
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Major
> Fix For: kubernetes-operator-1.0.0
>
>
> Currently we store complete spec objects in the status. This leads to large
> CRD schema sizes and will probably cause big headaches when implementing
> migration logic from one api version to the other.
> We suggest to store the lastReconciledSpec in String form instead. This will
> also make it easier to store new spec copies for the rollback logic also.
> Later when we want to support multiple versions this will allow us to handle
> ser/de logic programmatically and not cause problems on the kubernetes side.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
