From a7ebe6d50dcfb54a0bf1a35e0873b0d7b378427e Mon Sep 17 00:00:00 2001
From: Eirik A <sszynrae@gmail.com>
Date: Sat, 9 Jul 2022 08:22:13 +0100
Subject: [PATCH] docs: clarify that is_crd_stablished does not imply discovery
 done (#951)

docs: clarify that is_crd_stablished does not imply discovery

Signed-off-by: clux <sszynrae@gmail.com>
---
 kube-runtime/src/wait.rs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/kube-runtime/src/wait.rs b/kube-runtime/src/wait.rs
index 9978cc87f..47a09e592 100644
--- a/kube-runtime/src/wait.rs
+++ b/kube-runtime/src/wait.rs
@@ -184,6 +184,9 @@ pub mod conditions {
     }
 
     /// An await condition for `CustomResourceDefinition` that returns `true` once it has been accepted and established
+    ///
+    /// Note that this condition only guarantees you that you can use `Api<CustomResourceDefinition>` when it is ready.
+    /// It usually takes extra time for Discovery to notice the custom resource, and there is no condition for this.
     #[must_use]
     pub fn is_crd_established() -> impl Condition<CustomResourceDefinition> {
         |obj: Option<&CustomResourceDefinition>| {