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
Currently operator only detects diff only with yson configs and images, but if we deploy new version of operator, which will want to add something in pod specs — this wouldn't be applied.
It is expected that operator should compare all the desired state with state of the world and try to lead components to the desired state. Changes that operator makes should lead to minimum downtime possible.
The text was updated successfully, but these errors were encountered:
I think we could start with sts diff improvement. First option sound cleaner/simpler to me (less hardcoding fields for not comparing), but I think we need to research a number of calls to k8s api first and possibly stop requeuing reconcillation unless there is an error.
Currently operator only detects diff only with yson configs and images, but if we deploy new version of operator, which will want to add something in pod specs — this wouldn't be applied.
It is expected that operator should compare all the desired state with state of the world and try to lead components to the desired state. Changes that operator makes should lead to minimum downtime possible.
The text was updated successfully, but these errors were encountered: