Race between seeing a CRD added event and being able to select the kind about kubernetes

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[JamesMcNee]

/sig api-machinery

[karlkfi]

This seems working as intended. The CRD existing does not mean the resource is usable yet. You have to watch the CRD and wait for the status to say that it is established. This means that the CRD controller has seen the new CRD and created the necessary APIService for it. The APIService is then used by the apiserver to know where to route requests for that resource.

[JamesMcNee]

Hi @karlkfi, ah, thanks for clarifying, I was not aware of this! I will go ahead and close the issue.