From 4ee1b5f1e382d27793752bdcf0eb68805f613141 Mon Sep 17 00:00:00 2001 From: jennybuckley Date: Wed, 3 Jan 2018 13:48:07 -0800 Subject: [PATCH] fixed typo in docs/concepts/api-extension/custom-resources.md --- docs/concepts/api-extension/custom-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/api-extension/custom-resources.md b/docs/concepts/api-extension/custom-resources.md index 0035d677eb..3acedae31c 100644 --- a/docs/concepts/api-extension/custom-resources.md +++ b/docs/concepts/api-extension/custom-resources.md @@ -112,7 +112,7 @@ This frees you from writing your own API server to handle the custom resource, but the generic nature of the implementation means you have less flexibility than with [API server aggregation](#api-server-aggregation). -Refer to the [Custom Controler example, which uses Custom Resources](https://github.com/kubernetes/sample-controller) +Refer to the [Custom Controller example, which uses Custom Resources](https://github.com/kubernetes/sample-controller) for a demonstration of how to register a new custom resource, work with instances of your new resource type, and setup a controller to handle events.