Illogical roles position in key hierarchy of values

[R-omk]

What does a list of roles have to do with the vshard?

helm-charts/charts/cartridge/values.yaml

Lines 195 to 204 in 9317219

 vshard: 
   # Make all instances writable 
   # see: https://www.tarantool.io/ru/doc/latest/book/cartridge/cartridge_api/modules/cartridge/#replicasetinfo 
   allRw: true 
   # Weight of replicasets 
   weight: 1 
   # Vshard roles list 
   roles: 
     - failover-coordinator 
     - app.roles.router 

I may have an application that doesn't use the vshard at all.

А similar problem with naming in the operator code.

[Andrew Kluev]

My bad. I don't know why but up to this point, for some reason I was sure that roles and vshard related things...
But it's not... I going to rename it in free time, that field will be deprecated, but not removed for BC, new field at role level will be added