From ab2d26d8e7b327f1dd9fd0ba2f26cc76c3f77f85 Mon Sep 17 00:00:00 2001
From: Josh Voravong <jvoravong@splunk.com>
Date: Tue, 12 Apr 2022 10:22:14 -0600
Subject: [PATCH 1/2] Added more documentation about a k8sclusterreceiver
 breaking change that was introduced in version 0.45.0 of the chart

---
 CHANGELOG.md |  5 +++++
 UPGRADING.md | 32 ++++++++++++++++++++++++++++++++
 2 files changed, 37 insertions(+)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 00669276bb..28f528bcfa 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -35,6 +35,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 ### Changed
 
 - Upgrade splunk-otel-collector image to 0.45.0 (#407)
+- [BREAKING CHANGE] Use newer batch and autoscaling APIs in the Kubernetes
+  cluster receiver (#433). The Kubernetes cluster receiver will not be able to
+  collect all the metrics it previously did for Kubernetes clusters with
+  versions below 1.21 or Openshift clusters with versions below 4.8.
+  See [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0441-to-0450)
 
 ### Fixed
 
diff --git a/UPGRADING.md b/UPGRADING.md
index 86e9ba28c0..01b2f3b019 100644
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -30,6 +30,38 @@ clusterReceiver:
   featureGates: receiver.k8sclusterreceiver.reportCpuMetricsAsDouble
 ```
 
+## 0.44.1 to 0.45.0
+
+[[receiver/k8sclusterreceiver] Use newer batch and autoscaling APIs](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/7406)
+
+Kubernetes clusters with version 1.20 stopped having active support on
+2021-12-28 and had an end of life date on
+[2022-02-28](https://kubernetes.io/releases/patch-releases/#non-active-branch-history).
+The k8s_cluster receiver was refactored to use newer Kubernetes APIs that
+are available starting in Kubernetes version 1.21. The latest version of the
+k8s_cluster receiver will no longer be able to collect all the
+[previously available metrics](https://docs.splunk.com/Observability/gdi/kubernetes-cluster/kubernetes-cluster-receiver.html#metrics)
+with Kubernetes clusters that have versions below 1.21.
+
+If version 0.45.0 of the chart cannot collect metrics from your Kubernetes
+cluster that is a version below 1.21, you will see error messages in your
+cluster receiver logs that look like this.
+
+`Failed to watch *v1.CronJob: failed to list *v1.CronJob: the server could not
+find the requested resource`
+
+To better support users, in a future release we are adding a feature gate that
+will enable users to use the k8s_cluster receiver at the last version that
+supported Kubernetes clusters below version 1.21.
+
+If you still want to keep the previous behavior of the k8s_cluster receiver and
+upgrade to v0.45.0 of the chart, make sure your Kubernetes cluster uses one of
+the following versions.
+- `kubernetes`, `aks`, `eks`, `eks/fargate`, `gke`,  `gke/autopilot`
+  - Use v1.21 or above
+- `openshift`
+  - Use v4.8 or above
+
 ## 0.43.1 to 0.43.2
 
 [#375 Resource detection processor is configured to override all host and cloud

From 9aa93e45c678439340fee187c2611b0263accbe2 Mon Sep 17 00:00:00 2001
From: Josh Voravong <jvoravong@splunk.com>
Date: Tue, 12 Apr 2022 13:46:40 -0600
Subject: [PATCH 2/2] patch1 doc update

---
 UPGRADING.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/UPGRADING.md b/UPGRADING.md
index 01b2f3b019..c9b3882b40 100644
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -50,17 +50,17 @@ cluster receiver logs that look like this.
 `Failed to watch *v1.CronJob: failed to list *v1.CronJob: the server could not
 find the requested resource`
 
-To better support users, in a future release we are adding a feature gate that
-will enable users to use the k8s_cluster receiver at the last version that
+To better support users, in a future release we are adding a feature that
+will allow users to use the last version of the k8s_cluster receiver that
 supported Kubernetes clusters below version 1.21.
 
 If you still want to keep the previous behavior of the k8s_cluster receiver and
 upgrade to v0.45.0 of the chart, make sure your Kubernetes cluster uses one of
 the following versions.
 - `kubernetes`, `aks`, `eks`, `eks/fargate`, `gke`,  `gke/autopilot`
-  - Use v1.21 or above
+  - Use version 1.21 or above
 - `openshift`
-  - Use v4.8 or above
+  - Use version 4.8 or above
 
 ## 0.43.1 to 0.43.2