Changing the RV semantics in Upstream Kubernetes

[nilekhc]

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?

[brandond]

I think we should be fine - our db schema and interfaces define it as int64:

kine/pkg/logstructured/logstructured.go

Lines 19 to 30 in b6a3154

	type Log interface {
	Start(ctx context.Context) error
	CompactRevision(ctx context.Context) (int64, error)
	CurrentRevision(ctx context.Context) (int64, error)
	List(ctx context.Context, prefix, startKey string, limit, revision int64, includeDeletes bool) (int64, []*server.Event, error)
	Count(ctx context.Context, prefix, startKey string, revision int64) (int64, int64, error)
	After(ctx context.Context, prefix string, revision, limit int64) (int64, []*server.Event, error)
	Watch(ctx context.Context, prefix string) <-chan []*server.Event
	Append(ctx context.Context, event *server.Event) (int64, error)
	DbSize(ctx context.Context) (int64, error)
	Compact(ctx context.Context, revision int64) (int64, error)
	}

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...