docs for 2.2.x (#657)

* template

Signed-off-by: Art Berger <art.berger@solo.io>

* hugo and versions.json

Signed-off-by: Art Berger <art.berger@solo.io>

* versions and shortcodes

Signed-off-by: Art Berger <art.berger@solo.io>

* version

Signed-off-by: Art Berger <art.berger@solo.io>

* latest to 2.1.x

Signed-off-by: Art Berger <art.berger@solo.io>

* main to latest

Signed-off-by: Art Berger <art.berger@solo.io>

* 2.3 main

Signed-off-by: Art Berger <art.berger@solo.io>

* relnotes

Signed-off-by: Art Berger <art.berger@solo.io>

---------

Signed-off-by: Art Berger <art.berger@solo.io>
Signed-off-by: Art <artberger@users.noreply.github.com>

Author: artberger

.github/ISSUE_TEMPLATE/release.md

@@ -15,6 +15,7 @@ assignees: ''
 - [ ] Confirm that the upgrade and release note pages are updated. Typically, this is a separate issue.
 - [ ] In `content/docs`, create the new `main` by making a copy of the current main directory. Rename the directories appropriately. For example, the old main is copied to a new `main`, the old main becomes `latest`, and the old latest becomes a `2.x.x` version.
 - [ ] In the `hugo.yaml` file, update the `versions` to include the new minor version as main, the previous main as latest, and the previous latest as its version.
+- [ ] In the `versions.json` file, update the `versions` to include the new minor version as main, the previous main as latest, and the previous latest as its version.
 - [ ] Retire any version older than `n-3` (remove the directory and version from the `hugo.yaml` file)
 - [ ] Update the version conrefs in the `assets/docs/versions` directory. Often, there is not a release for the next version, so you might have to use the same for latest and main.
 - [ ] Add the release date to the version table in `assets/docs/pages/reference/versions.md`, and remove any retired versions.
@@ -35,4 +36,5 @@ assignees: ''
 
 - [ ] Merge in the autogenerated PR that the workflow created
 - [ ] Verify that the docs are published
-- [ ] Cut a GitHub release of the docs repo for the new release, and include any retired version (such as `Release for 2.6.x and last state for retired 2.2.x`)
+- [ ] Cut a GitHub release of the docs repo for the new release, and include any retired version (such as `Release for 2.6.x and last state for retired 2.2.x`)
+- [ ] If maintaining a downstream version, update the content paths for the new version.

assets/docs/pages/about/custom-resources.md

@@ -67,7 +67,7 @@ Kgateway uses the following custom resources to attach policies to routes and ga
 
 * [**DirectResponse**]({{< link-hextra path="/traffic-management/direct-response/" >}}): Directly respond to incoming requests with a custom HTTP response code and body.
 * [**HTTPListenerPolicy**]({{< link-hextra path="/about/policies/httplistenerpolicy/" >}}): Apply policies to all HTTP and HTTPS listeners.
-* [**TrafficPolicy**](https://kgateway.dev/docs/envoy/main/about/policies/trafficpolicy/): Attach policies to routes in an HTTPRoute resource.
+* [**TrafficPolicy**]({{< link-hextra path="/about/policies/trafficpolicy/" >}}): Attach policies to routes in an HTTPRoute resource.
 
 ### {{< reuse "docs/snippets/backend.md" >}}s
 

assets/docs/pages/about/policies-index.md

@@ -7,7 +7,7 @@ While the {{< reuse "docs/snippets/k8s-gateway-api-name.md" >}} allows you to do
 
 Kgateway uses the following custom resources to attach policies to routes and gateway listeners. 
 
-{{< version include-if="2.2.x,2.1.x" >}}
+{{< version exclude-if="2.0.x" >}}
 {{< cards >}}
   {{< card link="../policies/backendconfigpolicy/" title="BackendConfigPolicy" subtitle="Configure connection settings to an upstream service." >}}
   {{< card link="../../traffic-management/direct-response/" title="Direct response" subtitle="Directly respond to incoming requests with a custom HTTP response code and body." >}}
@@ -37,12 +37,12 @@ Review the policies that you can configure in kgateway and the level at which yo
 | [External authorization](../../security/external-auth) | GatewayExtension and {{< reuse "docs/snippets/trafficpolicy.md" >}} |
 | [External processing (ExtProc)](../../traffic-management/extproc/) | {{< reuse "docs/snippets/trafficpolicy.md" >}} | 
 | [Health checks for the Gateway](../../traffic-management/health-checks/gateway)| HTTPListenerPolicy | 
-| [Health checks for the Backends](../../traffic-management/health-checks/backend)| BackendConfigPolicy |{{%  version include-if="2.2.x,2.1.x" %}} 
+| [Health checks for the Backends](../../traffic-management/health-checks/backend)| BackendConfigPolicy |{{%  version exclude-if="2.0.x" %}} 
 | [HTTP connection settings](../../resiliency/connection)| BackendConfigPolicy | 
 | [Outlier detection](../../resiliency/outlier-detection)| BackendConfigPolicy | {{% /version %}}
 | [Rate limiting](../../security/ratelimit/) | {{< reuse "docs/snippets/trafficpolicy.md" >}} | 
 | [Session affinity - Simple load balancing](../../traffic-management/session-affinity/loadbalancing/) | BackendConfigPolicy  | 
-| [Session affinity - Consistent hashing](../../traffic-management/session-affinity/consistent-hashing/) | BackendConfigPolicy  | {{%  version include-if="2.2.x,2.1.x" %}} 
+| [Session affinity - Consistent hashing](../../traffic-management/session-affinity/consistent-hashing/) | BackendConfigPolicy  | {{%  version exclude-if="2.0.x" %}} 
 | [TCP keepalive](../../resiliency/tcp-keepalive/) | BackendConfigPolicy | {{% /version %}}
 | [Transformations](../../traffic-management/transformations) | {{< reuse "docs/snippets/trafficpolicy.md" >}} | 
 ## Policy behavior

assets/docs/pages/install/advanced.md

@@ -20,7 +20,7 @@ For more information, see the [Helm reference docs]({{< link-hextra path="/refer
 
 When using the development build {{< reuse "docs/versions/patch-dev.md" >}}, add `--set controller.image.pullPolicy=Always` to ensure you get the latest image. For production environments, this setting is not recommended as it might impact performance.
 
-{{< version include-if="2.2.x" >}}
+{{< version exclude-if="2.0.x,2.1.x" >}}
 
 ### Experimental Gateway API features {#experimental-gateway-api-features}
 
@@ -40,7 +40,7 @@ controller:
 ```
 {{< /version >}}
 
-{{< version include-if="2.2.x,2.1.x" >}}
+{{< version exclude-if="2.0.x,2.1.x" >}}
 
 ## Leader election
 
@@ -87,7 +87,7 @@ discoveryNamespaceSelectors:
     version: v3
 ```
 
-{{< version include-if="2.2.x,2.1.x" >}}
+{{< version exclude-if="2.0.x,2.1.x" >}}
 
 ## TLS encryption {#tls-encryption}
 

assets/docs/pages/operations/upgrade.md

@@ -185,9 +185,8 @@ For Istio upgrades, consult the docs based on the way that you installed Istio.
 
 4. Upgrade the {{< reuse "docs/snippets/kgateway.md" >}} control plane Helm installation.
    * Make sure to include your Helm values when you upgrade either as a configuration file or with `--set` flags. Otherwise, any previous custom values that you set might be overwritten.
-   * When using the development build v{{< reuse "docs/versions/patch-dev.md" >}}, add the `--set controller.image.pullPolicy=Always` option to ensure you get the latest image. Alternatively, you can specify the exact image digest.{{< version include-if="2.2.x,2.1.x" >}}
-   * To use experimental Gateway API features, include the experimental feature gate, `--set controller.extraEnv.KGW_ENABLE_GATEWAY_API_EXPERIMENTAL_FEATURES=true`.
-   {{< /version >}}
+   * When using the development build v{{< reuse "docs/versions/patch-dev.md" >}}, add the `--set controller.image.pullPolicy=Always` option to ensure you get the latest image. Alternatively, you can specify the exact image digest.{{< version exclude-if="2.0.x" >}}
+   * To use experimental Gateway API features, include the experimental feature gate, `--set controller.extraEnv.KGW_ENABLE_GATEWAY_API_EXPERIMENTAL_FEATURES=true`.{{< /version >}}
 
    ```sh
    helm upgrade -i -n {{< reuse "docs/snippets/namespace.md" >}} {{< reuse "/docs/snippets/helm-kgateway.md" >}} oci://{{< reuse "/docs/snippets/helm-path.md" >}}/charts/{{< reuse "/docs/snippets/helm-kgateway.md" >}} \

assets/docs/pages/reference/add-docs.md

@@ -253,7 +253,7 @@ The documentation maintainers of the kgateway project will review your pull requ
 The kgateway project automatically generates the following documentation from the code.
 
 * [API reference]({{< link-hextra path="/reference/api/" >}})
-* [Helm reference]({{< link-hextra path="/reference/helm/" >}}){{< version include-if="2.2.x,2.1.x" >}}
+* [Helm reference]({{< link-hextra path="/reference/helm/" >}}){{< version exclude-if="2.0.x" >}}
 * [Control plane metrics](../../../observability/control-plane-metrics/){{< /version >}}
 
 To learn more about how to generate these docs, see the [GitHub Workflows README](https://github.com/kgateway-dev/kgateway.dev/tree/main/.github/workflows/README.md).

assets/docs/pages/reference/versions.md

@@ -4,6 +4,7 @@ Review the following information about supported release versions for kgateway.
 
 | Kgateway | Release date | Kubernetes | Gateway API`*` | Envoy | Helm | Istio`†` |
 |----------|--------------|------------|----------------|-------|------|----------|
+| 2.1.x | 09 Feb 2026 | 1.31 - 1.35 | 1.4.x | Proxy 1.35, API v3 | >= 3.12 | 1.23 - 1.27 |
 | 2.1.x | 10 Oct 2025 | 1.31 - 1.34 | 1.4.x | Proxy 1.35, API v3 | >= 3.12 | 1.23 - 1.27 |
 | 2.0.x | 01 Apr 2025 | 1.27 - 1.31 | 1.2.x | Proxy 1.33, API v3 | >= 3.12 | 1.18 - 1.23 |