Kirill Sibirev

Is the issue still relevant? Can you provide minimal example, which can reproduce the problem?

We've discussed with contributors team and came to the conclusion that to have more convienient api for reading tables considering schema (so sdk user would manipulate with scale-aware structs) is...

**tl;dr** it seems that ytsaurus works in the Orbstack for Sonoma MacOs. I'm not sure if Orbstack issues should be mixed with "arm support" issue, since (as far as I...

After update to Sonoma 14.4 @orloffv also can't reproduce the problem if I understood correctly. Though our other colleaugue still can't run ytsaurus in orbstack with same OS and Orbstack...

I guess this one also not actual now after labels refactoring.

@Kontakter @psushin is it still an issue? If server code supports it already (or don't want yt operator to configure it in any case) we can close it. If it...

It is possible to store this flag in the cypress of updated yt, but not 100% sure it wouldn't bite us at some point when cluster is not available and...

Maybe we can have some fuse-resource which is created on successfull cluster update by operator and is never deleted by operator. But human can delete that resource via kubectl which...

Maybe we could use some in-memory volumes for tests and that could speed up tests with small change. Or maybe ytsaurus could be tweaked somehow to faster delete things and...

Here is very relevant discussion https://github.com/kubernetes-sigs/kubebuilder/issues/592 As far as I understood recommended options are: 1) use update with dry-run and compare results https://github.com/kubernetes-sigs/kubebuilder/issues/592#issuecomment-1193067879 — this should work good, but will...