Remove references to old versions

versioned_docs/version-2.7/pages-for-subheaders/cloud-marketplace.md

@@ -4,4 +4,4 @@ title: Cloud Marketplace Integration
 
 Rancher offers integration with cloud marketplaces to easily purchase support for installations hosted on certain cloud providers. In addition, this integration also provides the ability to generate a supportconfig bundle which can be provided to rancher support.
 
-As of Rancher v2.6.7, only AWS is supported for this integration.
+Only AWS is supported for this integration.

versioned_docs/version-2.7/pages-for-subheaders/helm-charts-in-rancher.md

@@ -4,18 +4,12 @@ title: Helm Charts in Rancher
 
 In this section, you'll learn how to manage Helm chart repositories and applications in Rancher. Helm chart repositories are managed using **Apps**. It uses a catalog-like system to import bundles of charts from repositories and then uses those charts to either deploy custom Helm applications or Rancher's tools such as Monitoring or Istio. Rancher tools come as pre-loaded repositories which deploy as standalone Helm charts. Any additional repositories are only added to the current cluster.
 
-### Changes in Rancher v2.6
+### Versioning Scheme
 
-Starting in Rancher v2.6.0, a new versioning scheme for Rancher feature charts was implemented. The changes are centered around the major version of the charts and the +up annotation for upstream charts, where applicable.
+The Rancher feature charts versioning scheme is centered around the major version of the charts and the +up annotation for upstream charts, where applicable.
 
 **Major Version:** The major version of the charts is tied to Rancher minor versions. When you upgrade to a new Rancher minor version, you should ensure that all of your **Apps** charts are also upgraded to the correct release line for the chart.
 
-:::note
-
-Any major versions that are less than the ones mentioned in the table below are meant for 2.5 and below only. For example, you are advised to not use <100.x.x versions of Monitoring in 2.6.x+.
-
-:::
-
 **Feature Charts:**
 
 | **Name** | **Supported Minimum Version** | **Supported Maximum Version** |
@@ -103,10 +97,9 @@ To add a private CA for Helm Chart repositories:
     [...]
     ```
 
-
 :::note Helm chart repositories with authentication
 
-As of Rancher v2.6.3, a new value `disableSameOriginCheck` has been added to the Repo.Spec. This allows users to bypass the same origin checks, sending the repository Authentication information as a Basic Auth Header with all API calls. This is not recommended but can be used as a temporary solution in cases of non-standard Helm chart repositories such as those that have redirects to a different origin URL.
+The Repo.Spec contains a `disableSameOriginCheck` that allows users to bypass the same origin checks, sending the repository Authentication information as a Basic Auth Header with all API calls. This is not recommended but can be used as a temporary solution in cases of non-standard Helm chart repositories such as those that have redirects to a different origin URL.
 
 To use this feature for an existing Helm chart repository, click <b>⋮ > Edit YAML</b>. On the `spec` portion of the YAML file, add `disableSameOriginCheck` and set it to `true`.
 
@@ -144,7 +137,7 @@ If you are upgrading your chart using _"Customize Helm options before upgrade"_
 
 :::
 
-#### Changes in Rancher v2.6.3
+#### Legacy Apps
 
 The upgrade button has been removed for legacy apps from the **Apps > Installed Apps** page.
 

versioned_docs/version-2.7/pages-for-subheaders/rancher-security.md

@@ -22,9 +22,8 @@ title: Security
 Security is at the heart of all Rancher features. From integrating with all the popular authentication tools and services, to an enterprise grade [RBAC capability](manage-role-based-access-control-rbac.md), Rancher makes your Kubernetes clusters even more secure.
 
 On this page, we provide security related documentation along with resources to help you secure your Rancher installation and your downstream Kubernetes clusters.
-### NeuVector Integration with Rancher
 
-_New in v2.6.5_
+### NeuVector Integration with Rancher
 
 NeuVector is an open-source, container-focused security application that is now integrated into Rancher. NeuVector provides production security, DevOps vulnerability protection, and a container firewall, et al. Please see the [Rancher docs](../integrations-in-rancher/neuvector.md) and the [NeuVector docs](https://open-docs.neuvector.com/) for more information.
 

versioned_docs/version-2.7/pages-for-subheaders/use-windows-clusters.md

@@ -17,13 +17,6 @@ For the full list of requirements, see [this section.](#requirements-for-windows
 
 For a summary of Kubernetes features supported in Windows, see the Kubernetes documentation on [supported functionality and limitations for using Kubernetes with Windows](https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#supported-functionality-and-limitations) or the [guide for scheduling Windows containers in Kubernetes](https://kubernetes.io/docs/setup/production-environment/windows/user-guide-windows-containers/).
 
-
-## Changes in Rancher v2.6
-
-Rancher v2.6 introduces provisioning for [RKE2](https://docs.rke2.io/) clusters directly from the Rancher UI. RKE2, also known as RKE Government, is a fully conformant Kubernetes distribution that focuses on security and compliance within the U.S. Federal Government sector.
-
-As of Rancher v2.6.5, provisioning for RKE2 is GA.
-
 ### RKE2 Windows
 
 The RKE2 provisioning feature also includes installing RKE2 on Windows clusters. Windows features for RKE2 include:
@@ -41,8 +34,6 @@ Rancher will allow Windows workload pods to deploy on both Windows and Linux wor
 
 :::
 
-**_New in Rancher v2.6.7_**
-
 - HostProcess containers in Windows RKE2 are supported in Kubernetes v1.24.1 and up. See [the upstream documentation](https://kubernetes.io/docs/tasks/configure-pod-container/create-hostprocess-pod/) for more information.
 
 ## Requirements for Windows Clusters