[
https://issues.apache.org/jira/browse/FLINK-30858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682903#comment-17682903
]
Gyula Fora commented on FLINK-30858:
------------------------------------
I discussed this with Max yesterday, and it should also be possible to use the
current generation metadata in the status to track the last observed generation
with a slight change to the reconciler logic.
I just want to point out that the original intention with the generation field
was to be able to match deployed (jobmanager generation label) with the last
reconciled spec for resiliency to failures during deploy operations. This is
not currently intended as a user facing information.
With this change however it would be easier to is for users, I agree :)
> Kubernetes operator does not update reconciled generation
> ---------------------------------------------------------
>
> Key: FLINK-30858
> URL: https://issues.apache.org/jira/browse/FLINK-30858
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.3.1
> Reporter: Thomas Weise
> Priority: Major
>
> Kubernetes manages the generation field as part of the spec metadata. It will
> be increased when changes are made to the resource. The counterpart in status
> is "observed generation", provided by a controller. By comparing the two, the
> client can determine that the controller has processed the spec and in
> conjunction with other status information conclude that a change has been
> reconciled.
> The Flink operator currently tracks the generation as part of reconciled and
> stable specs but these cannot be used as "observed generation" to perform the
> check. The value isn't updated in cases where operator determines that there
> are no changes to the spec that require deployment. This can be reproduced
> through PUT/replace with the same spec or a change in upgrade mode.
> The operator should provide the observed spec, which in conjunction with
> deployment state can then be used by clients to determine that the spec has
> been reconciled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
