When master image is being updated operator should set //sys/@config/node_tracker/enable_real_chunk_locations=%true. It is required to enable update to 24.2 in the future. It is possible to set the flag starting from 23.2 (or even 23.1 need to check)
N.B. Such update should be done with re-creating all ytsaurus nodes pods, which is default behaviour for full update (which is triggered when master image is updated). Node restart wouldn't happen with updateSelector=MasterOnly, but we consider updateSelector experimental functionality for those who knows what they doing (for example they can restart nodes themselves to have less downtime).
Also we should restrict users to update to 24.2 if the flag is not set to true and add note to release notes that cluster should be updated to 24.1 with min version of ytop (the version where current issue is implemented) before 24.2 update.
When master image is being updated operator should set
//sys/@config/node_tracker/enable_real_chunk_locations=%true. It is required to enable update to 24.2 in the future. It is possible to set the flag starting from 23.2 (or even 23.1 need to check)N.B. Such update should be done with re-creating all ytsaurus nodes pods, which is default behaviour for full update (which is triggered when master image is updated). Node restart wouldn't happen with
updateSelector=MasterOnly, but we considerupdateSelectorexperimental functionality for those who knows what they doing (for example they can restart nodes themselves to have less downtime).Also we should restrict users to update to 24.2 if the flag is not set to true and add note to release notes that cluster should be updated to 24.1 with min version of ytop (the version where current issue is implemented) before 24.2 update.