but what if you was out of town, or had some kind of other issue that prevented you from updating…
getting punished with no ingress skipping a single update, imo seems a bit harsh…
sure updating doesn’t take long, but i also have more than just a single node…
and right now… we are like … lets see
this post was made with the release for v1.26.3 for windows on the 7th of april.
and release for docker is usually a week after, meaning right now.
with my 10 nodes 3 of which are already updated, i am basically forced to updated them if i want ingress for today.
which is according to your estimates 50-100minutes of work… tho i’m pretty sure i can do that in less.
and then tomorrow the update of 1.26.3 goes live for docker and then i can do the whole thing again.
sure i can just wait, but the matter of fact is now matter how your twist and turn it that to maintain my nodes, even if i was having them auto update i would have to check that the individual nodes was running correctly after the updates.
aside from that we was told that we would be allowed to be two updates behind…
keep in mind that if you go outside the punishment the node supposely gets DQ
when the DQ range moves before the update moves and not the other way around.
people that may have wanted to update could get DQ.
duno if there is an actual warning for that… there really should be… aside from ingress stopping.
yesterday the minimum allowed version was 1.22.0 and current version was v1.25.0
today it’s 1.24.0 and current version is v1.25.0
so if i had been running on the tail end with v1.22 and wanted to updated to v1.26
i would now get DQ 1 day before the newest version is released… instead of after…
i think that is a problem… should be the other way around… a few days after the update, people can then get DQ if they are out of range.
i could also ask if v1.24.0 is the minimum, then why am i being punished when running v1.24.3
it’s a mistake… obviously