@@ -23,13 +23,14 @@ limitations under the License.
2323// and uncommon cases should be possible. In general, controller-runtime tries
2424// to guide users towards Kubernetes controller best-practices.
2525//
26- // Getting Started
26+ // # Getting Started
2727//
2828// The main entrypoint for controller-runtime is this root package, which
2929// contains all of the common types needed to get started building controllers:
30- // import (
31- // ctrl "sigs.k8s.io/controller-runtime"
32- // )
30+ //
31+ // import (
32+ // ctrl "sigs.k8s.io/controller-runtime"
33+ // )
3334//
3435// The examples in this package walk through a basic controller setup. The
3536// kubebuilder book (https://book.kubebuilder.io) has some more in-depth
@@ -38,7 +39,7 @@ limitations under the License.
3839// controller-runtime favors structs with sane defaults over constructors, so
3940// it's fairly common to see structs being used directly in controller-runtime.
4041//
41- // Organization
42+ // # Organization
4243//
4344// A brief-ish walkthrough of the layout of this library can be found below. Each
4445// package contains more information about how to use it.
@@ -47,7 +48,7 @@ limitations under the License.
4748// controllers can be found at
4849// https://github.com/kubernetes-sigs/controller-runtime/blob/master/FAQ.md.
4950//
50- // Managers
51+ // # Managers
5152//
5253// Every controller and webhook is ultimately run by a Manager (pkg/manager). A
5354// manager is responsible for running controllers and webhooks, and setting up
@@ -56,7 +57,7 @@ limitations under the License.
5657// generally configured to gracefully shut down controllers on pod termination
5758// by wiring up a signal handler (pkg/manager/signals).
5859//
59- // Controllers
60+ // # Controllers
6061//
6162// Controllers (pkg/controller) use events (pkg/event) to eventually trigger
6263// reconcile requests. They may be constructed manually, but are often
@@ -67,15 +68,15 @@ limitations under the License.
6768// trigger reconciles. There are pre-written utilities for the common cases, and
6869// interfaces and helpers for advanced cases.
6970//
70- // Reconcilers
71+ // # Reconcilers
7172//
7273// Controller logic is implemented in terms of Reconcilers (pkg/reconcile). A
7374// Reconciler implements a function which takes a reconcile Request containing
7475// the name and namespace of the object to reconcile, reconciles the object,
7576// and returns a Response or an error indicating whether to requeue for a
7677// second round of processing.
7778//
78- // Clients and Caches
79+ // # Clients and Caches
7980//
8081// Reconcilers use Clients (pkg/client) to access API objects. The default
8182// client provided by the manager reads from a local shared cache (pkg/cache)
@@ -91,19 +92,19 @@ limitations under the License.
9192// may retrieve event recorders (pkg/recorder) to emit events using the
9293// manager.
9394//
94- // Schemes
95+ // # Schemes
9596//
9697// Clients, Caches, and many other things in Kubernetes use Schemes
9798// (pkg/scheme) to associate Go types to Kubernetes API Kinds
9899// (Group-Version-Kinds, to be specific).
99100//
100- // Webhooks
101+ // # Webhooks
101102//
102103// Similarly, webhooks (pkg/webhook/admission) may be implemented directly, but
103104// are often constructed using a builder (pkg/webhook/admission/builder). They
104105// are run via a server (pkg/webhook) which is managed by a Manager.
105106//
106- // Logging and Metrics
107+ // # Logging and Metrics
107108//
108109// Logging (pkg/log) in controller-runtime is done via structured logs, using a
109110// log set of interfaces called logr
@@ -117,7 +118,7 @@ limitations under the License.
117118// serve these by an HTTP endpoint, and additional metrics may be registered to
118119// this Registry as normal.
119120//
120- // Testing
121+ // # Testing
121122//
122123// You can easily build integration and unit tests for your controllers and
123124// webhooks using the test Environment (pkg/envtest). This will automatically
0 commit comments