From 51c37cee34f71d7438878c4dece1fe41ebff3825 Mon Sep 17 00:00:00 2001 From: Sajiyah Salat <109643863+Sajiyah-Salat@users.noreply.github.com> Date: Fri, 19 May 2023 09:04:15 +0530 Subject: [PATCH] Update good-practices.md --- docs/book/src/reference/good-practices.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/book/src/reference/good-practices.md b/docs/book/src/reference/good-practices.md index f94fd94717e..85f408b4cb9 100644 --- a/docs/book/src/reference/good-practices.md +++ b/docs/book/src/reference/good-practices.md @@ -14,7 +14,7 @@ Writing reconciliation logic according to specific events, breaks the recommenda ## Understanding Kubernetes APIs and following API conventions -Building your operator commonly involves extending the Kubernetes API itself. It is helpful to understand precisely how Custom Resource Definitions (CRDs) interact with the Kubernetes API. Also, the [Kubebuilder documentation](./cronjob-tutorial/gvks.html) on Groups and Versions and Kinds may be helpful to understand these concepts better as they relate to operators. +Building your operator commonly involves extending the Kubernetes API itself. It is helpful to understand precisely how Custom Resource Definitions (CRDs) interact with the Kubernetes API. Also, the [Kubebuilder documentation][docs] on Groups and Versions and Kinds may be helpful to understand these concepts better as they relate to operators. By developing Operator pattern solutions, we extend the Kubernetes api. @@ -61,7 +61,7 @@ Therefore, you can check an example of Status Conditional usage by looking at it - +[docs]: ./cronjob-tutorial/gvks.html [operator-pattern]: https://kubernetes.io/docs/concepts/extend-kubernetes/operator/ [controllers]: https://kubernetes.io/docs/concepts/architecture/controller/