Tom Lebreux

@aalves08 The PR is still being worked on but it already fixes _some_ issues so it could be worth a shot validating that it also fixes this issue before my...

@richard-cox > How long are we away from the fixes being available in v2.9-head The fix is now in steve `master`, we need to update steve version in rancher/rancher but...

> vai_test.go:421: Expected file informer_object_fields.db not found in pod rancher-c48878785-lf627 We have removed the db `informer_object_fields.db` in https://github.com/rancher/lasso/pull/97 so only `informer_object_cache.db` should be checked for existence. (In fact now we...

Verified and agree with @richard-cox it's that same issue. Basically, listing resources contain the state field correctly, but data coming from the watch doesn't. That page is watching the deployments...

A quick glance at the closed PRs, it looks like this PR introduced the wrapped refs: https://github.com/kubernetes/kube-openapi/pull/298/. The reason for wrapping the refs is explained here: https://github.com/kubernetes/kubernetes/issues/106387#issue-1052139640. > Any members...

After discussion with Prachi, if this doesn't make it to 2.10 then we'll do it for 2.11. The UI will likely need it at that point.

We're going to require aggregation layer to run Rancher so this is no longer needed. Closing.

Fwiw, lasso also uses the [v1 version](https://github.com/rancher/lasso/pull/47)

# Analysis Ok, a bit of digging and here's the issue. The `metadata.fields` are being injected here: https://github.com/rancher/steve/blob/527d44a3a7c8810c382738039993388a411443d9/pkg/stores/sqlproxy/tablelistconvert/client.go#L125 by the ListWatcher client. Basically, the ListWatcher asks for a table view...

Given it's a bug, it could make it to 2.11.x depending on how we prioritize it and whether we want it to be fixed for 2.11. Updated my comment above...