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
We are codifying the schema of ResourceVersion in upstream Kubernetes with KEP.
tl;dr
With this change, we are parsing ResourceVersion to an int, thus explicitly defining RV as an integer rather than an opaque string as it is today. Does this affect the project in any way?
The text was updated successfully, but these errors were encountered:
Does defining it as int instead of int64 have any impact on 32bit platforms like arm, where int will be int32 instead of int64? We do still support arm...
We are codifying the schema of ResourceVersion in upstream Kubernetes with KEP.
tl;dr
With this change, we are parsing ResourceVersion to an
int
, thus explicitly defining RV as an integer rather than an opaque string as it is today. Does this affect the project in any way?The text was updated successfully, but these errors were encountered: