kubectl third party resource race #24392
Labels
area/kubectl
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
When registering more than one ThirdPartyResource, there appears to be a race in kubectl for the ability to read the APIs. Note that all these commands are executed sequentially, and an empty response on the
get
is due to no objects being registered (this is an expected behavior). This is using kubectl at e81663c, which is after #18835 landed.I believe the fix is here, but I'm not in a position to properly test (although I did test a kubectl build by hand and it seemed to work).
The text was updated successfully, but these errors were encountered: