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
This is a breaking change, although it should not have any negative
effects in practise.
The v1alpha6 cluster restorer had become too complex with too many
individual fields. This change reduces the number of fields to be
consistent with the v1alpha7 restorer.
With this change, an object stored as v1alpha6 with previous v1beta1
annotations could have fields in its spec restored to a semantically
equivalent but slightly different serialisation when converted to
v1beta1. Differences in the bastion and status are not affected.
In practise this should not matter for 2 reasons:
* The storage version is v1beta1, so the annotation should have been
freshly generated in the new format anyway.
* Even if it were not, and the v1alpha6 were under external control, the
external controller would observe a difference and restore it to the
previous version. It would then converted again with the new
annotation.
Note that if the object is not under external control these differences
don't matter anyway.
0 commit comments