Konrad Kaim comments

Results 12 comments of


                                            Konrad Kaim

add placement policy for NAP workload

@Obliviour we're just behind the corner with subsliicing support, so let's hold on on merging this. This will be supported through sub-slicing and should be possible to be used by...

add placement policy for NAP workload

Closing as this was addressed in https://github.com/AI-Hypercomputer/xpk/pull/847

fix: Improve clarity of command execution logs

@SikaGrr PTAL, but this looks good to me

kubectl describe suffers from N+1 query problem when falling back to prefix search, causing performance issues

This change was introduced ~7 years ago. People might be depending on this behavior. I would add ability to disable that through the flag.

kubectl describe suffers from N+1 query problem when falling back to prefix search, causing performance issues

/assign

kubectl describe suffers from N+1 query problem when falling back to prefix search, causing performance issues

There is generally a pattern in all `ResourceDescriber`. It is to fetch the main resource that we want to describe and then some complementary data. The first n+1 is on...

kubectl describe suffers from N+1 query problem when falling back to prefix search, causing performance issues

> When we've already fetched the object from the server, that sounds like a reasonable approach. You can also run `kubectl describe -f local_file.yaml`, make sure the new approach still...

kubectl describe suffers from N+1 query problem when falling back to prefix search, causing performance issues

@liggitt `Latest().` Indeed helped. I also modified an existing test to make sure that we're describing object from server rather than its local copy.

kubectl describe suffers from N+1 query problem when falling back to prefix search, causing performance issues

/assign

Update README.md in a fork branch

Closing as external contributor flow is already fixed.