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
If user has many pods in the ECK operator/resource namespace, it may take long time to run ECK diag.
i.e. 200+ pods can take 35 min to run ECK diag by default.
It might be great to provide an ability for user to choose which node role (master/data/etc) or data tier (hot/warm) to take.
Thanks @pebrc
Yeah it looks like the same from a high level, but maybe in details, this one has more clear requirements.
Anyway I am fine with closing this one as long as it's on the board :)
If user has many pods in the ECK operator/resource namespace, it may take long time to run ECK diag.
i.e. 200+ pods can take 35 min to run ECK diag by default.
It might be great to provide an ability for user to choose which node role (master/data/etc) or data tier (hot/warm) to take.
cc @jstrassb @eedugon
The text was updated successfully, but these errors were encountered: