From ed2a0c03a9759b32c4bea8abf5681fe131fef6b8 Mon Sep 17 00:00:00 2001 From: LavredisG Date: Sun, 13 Oct 2024 23:27:06 +0300 Subject: [PATCH] Update faq.md Signed-off-by: LavredisG --- docs/faq/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq/faq.md b/docs/faq/faq.md index ca466569..142ca425 100644 --- a/docs/faq/faq.md +++ b/docs/faq/faq.md @@ -45,7 +45,7 @@ TODO: Link to adoption use case once it gets on board. Kubernetes provides two methods to extend APIs: Custom Resource and Kubernetes API Aggregation Layer. For more detail, you can refer to [Extending the Kubernetes API](https://kubernetes.io/docs/concepts/extend-kubernetes/). -Karmada uses the both extension methods. For example, `PropagationPolicy` and `ResourceBinding` use Custom Resource, and `Cluster` resource uses Kubernetes API Aggregation Layer. +Karmada uses both extension methods. For example, `PropagationPolicy` and `ResourceBinding` use Custom Resource, and `Cluster` resource uses Kubernetes API Aggregation Layer. Therefore, `Cluster` resources do not have a CRD YAML file, and they are not visible when you execute the `kubectl get crd` command.