What do you want to happen?

In the Test Environment Setup section of the Kubebuilder book, it shows that to test controller behavior, you have to manually add the code to start the controller in the test environment. I ran into some confusion because I missed this part of the tutorial and couldn't tell

Add a test sending (e.g. config map) patches through the same API using:

• JSON patch
• Strategic merge patch

make sure the API client is able to set the content type properly according to the request body, and the patches are applied successfully.

ref: https://github.com/ku

The straightforward way to do webhook testing with envtest looks something like

// in BeforeSuite
env := envtest.Environment{ /* set directory paths, etc */}
env.Start()

// in the contents of a test file
BeforeEach(func() {
  go mgr.Start(stopCh)
})
AfterEach(func() { close(stopCh) })

It("should do stuff with the webhook", func() {
  Expect(cl.Create(ctx, myObj)).To(Explode(

#317 introduces support for a pattern we generally don't recommend: pointers as map values. This is mainly for a few legacy use cases that folks want to support, but I think we generally want to warn people that this isn't a pattern that we/the kube API conventions generally suggest/support.

We probably want something that looks a lot like our error reporting system, but works adds a "non-fata

Most of our CR prerelease versions have notes on them, like: https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.2.0-beta.2 & https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.7.0-alpha.2. We should add that automatically.

/good-first-issue