You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JOSDK could provide support and show how to ensure that if the values are stored as status, the up-to-date status is always available for subsequent reconciliation. Note that since the inform caches work in an async manner, this might not be the case by default.
The text was updated successfully, but these errors were encountered:
Although this is a bit of a controversial topic, storing allocated values in status is justified in some operators, and also k8s guidelines were updated regarding to this:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#representing-allocated-values
JOSDK could provide support and show how to ensure that if the values are stored as status, the up-to-date status is always available for subsequent reconciliation. Note that since the inform caches work in an async manner, this might not be the case by default.
The text was updated successfully, but these errors were encountered: