From 05e4fdd400df3426b34fbdd2040339b531e2050d Mon Sep 17 00:00:00 2001
From: Rafael Polanco <6497491+rrpolanco@users.noreply.github.com>
Date: Mon, 8 May 2023 17:07:01 -0500
Subject: [PATCH] Add Sonobuoy limitation when installing Kubernetes 1.27 and
 Prometheus (#968)

Add Kubernetes 1.27.x and Prometheus limitation
---
 src/markdown-pages/add-ons/sonobuoy.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/markdown-pages/add-ons/sonobuoy.md b/src/markdown-pages/add-ons/sonobuoy.md
index 3bc0cf97..b2adf312 100644
--- a/src/markdown-pages/add-ons/sonobuoy.md
+++ b/src/markdown-pages/add-ons/sonobuoy.md
@@ -13,6 +13,10 @@ It is a customizable, extendable, and cluster-agnostic way to generate clear, in
 This makes Sonobuoy assets available in the cluster, but does not run conformance tests.
 The `sonobuoy` binary will be installed in the directory `/usr/local/bin`.
 
+## Limitations
+
+This add-on does not work if Kubernetes 1.27.x and Prometheus is installed as `sonobuoy` will panic with the error: `panic: runtime error: invalid memory address or nil pointer dereference`. This problem is being [addressed](https://github.com/vmware-tanzu/sonobuoy/pull/1909) in the upstream Sonobuoy project.
+
 ## Advanced Install Options
 
 ```yaml