convert headers to lowercase and remove changelog

app/_includes/md/kgo/konnect-entities-prerequisites.md

@@ -18,7 +18,7 @@ You may create either a Personal Access Token (PAT) or a Service Account Token (
 to create a `KonnectAPIAuthConfiguration` object that will be used by the {{site.kgo_product_name}} to authenticate
 with Konnect APIs.
 
-### Create a {{site.konnect_product_name}} API Auth Configuration
+### Create a {{site.konnect_product_name}} API auth configuration
 
 Depending on your preferences, you can create a `KonnectAPIAuthConfiguration` object with the token specified
 directly in its spec or as a reference to a Kubernetes Secret. The `serverURL` field should be set to the Konnect API
@@ -86,7 +86,7 @@ konnect-api-auth   True    <your-konnect-org-id>                  https://eu.api
 ```
 
 {% if include.with-control-plane %}
-### Create a {{site.base_gateway}} Control Plane
+### Create a {{site.base_gateway}} control plane
 
 Creating the `KonnectGatewayControlPlane` object in your Kubernetes cluster will provision a {{site.konnect_product_name}} Gateway
 control plane in your [Gateway Manager](/konnect/gateway-manager). The `KonnectGatewayControlPlane` CR

app/_src/gateway-operator/guides/konnect-entities/certificate-and-cacertificate.md

@@ -9,7 +9,7 @@ and CA Certificates natively from your Kubernetes cluster.
 {% include md/kgo/konnect-entities-prerequisites.md disable_accordian=false version=page.version release=page.release
 with-control-plane=true %}
 
-## Create a Certificate
+## Create a certificate
 
 Creating the `KongCertificate` object in your Kubernetes cluster will provision a Konnect Certificate in
 your [Gateway Manager](/konnect/gateway-manager).
@@ -66,7 +66,7 @@ spec:
 
 At this point, you should see the certificate in the Gateway Manager UI.
 
-### Assign an SNI to the Certificate
+### Assign an SNI to the certificate
 
 You can assign multiple SNIs to a `KongCertificate`. To do so, you need to create a `KongSNI` object and associate it
 with

app/_src/gateway-operator/guides/konnect-entities/consumer-and-consumergroup.md

@@ -9,7 +9,7 @@ and consumer groups natively from your Kubernetes cluster.
 {% include md/kgo/konnect-entities-prerequisites.md disable_accordian=false version=page.version release=page.release
 with-control-plane=true %}
 
-## Create a Consumer
+## Create a consumer
 
 Creating the `KongConsumer` object in your Kubernetes cluster will provision a {{site.konnect_product_name}} Consumer in
 your [Gateway Manager](/konnect/gateway-manager).
@@ -42,7 +42,7 @@ spec:
 
 At this point, you should see the consumer in the Gateway Manager UI.
 
-## Associate the Consumer with Credentials
+## Associate the consumer with credentials
 
 Consumers can have credentials associated with them. You can create one of the supported credential types. Please refer
 to the below custom resource's documentation links to learn all the available fields for each credential type.
@@ -75,7 +75,7 @@ spec:
 
 At this point, you should see the credential in the consumer's credentials in the Gateway Manager UI.
 
-## Create a Consumer Group
+## Create a consumer group
 
 Creating the `KongConsumerGroup` object in your Kubernetes cluster will provision a {{site.konnect_product_name}} consumer group in
 your [Gateway Manager](/konnect/gateway-manager). Please refer to the
@@ -104,7 +104,7 @@ spec:
 
 At this point, you should see the consumer group in the Gateway Manager UI.
 
-### Associate a Consumer with a Consumer Group
+### Associate a consumer with a consumer group
 
 You can associate a `KongConsumer` with a `KongConsumerGroup` by modifying the `KongConsumer` object and adding the
 `consumerGroups` field. This field is a list of `KongConsumerGroup` names.

app/_src/gateway-operator/guides/konnect-entities/dpcertificate.md

@@ -8,7 +8,7 @@ Konnect [Vault](/konnect/gateway-manager/configuration/#vaults) natively from yo
 {% include md/kgo/konnect-entities-prerequisites.md disable_accordian=false version=page.version release=page.release
 with-control-plane=true %}
 
-## Create a Data Plane Client Certificate 
+## Create a data plane client certificate
 
 Creating the `KongDataPlaneClientCertificate` object in your Kubernetes cluster will provision a data plane client certificate in
 your [Gateway Manager](/konnect/gateway-manager). You can refer to the CR [API](/gateway-operator/{{ page.release

app/_src/gateway-operator/guides/konnect-entities/gatewaycontrolplane.md

@@ -8,7 +8,7 @@ Planes](/konnect/gateway-manager/#control-planes) natively from your Kubernetes
 
 {% include md/kgo/konnect-entities-prerequisites.md disable_accordian=false version=page.version release=page.release %}
 
-## Create a Self-Managed Hybrid Gateway Control Plane
+## Create a self-managed hybrid gateway control plane
 
 Creating the `KonnectGatewayControlPlane` object in your Kubernetes cluster will provision a {{site.konnect_short_name}} Gateway
 control plane in your [Gateway Manager](/konnect/gateway-manager). The `KonnectGatewayControlPlane` CR
@@ -47,7 +47,7 @@ NAME                    PROGRAMMED   ID                                     ORGI
 gateway-control-plane   True         <konnect-control-plane-id>             <your-konnect-ord-id>
 ```
 
-## Create a Control Plane Group
+## Create a control plane group
 
 Gateway Manager allows you to group multiple Gateway control planes. You can create
 a [Control Plane Group](/konnect/gateway-manager/#control-plane-groups) by setting the `cluster_type`
@@ -82,7 +82,7 @@ NAME                    PROGRAMMED   ID                                     ORGI
 control-plane-group     True         <konnect-control-plane-id>             <your-konnect-ord-id>
 ```
 
-### Add a Gateway Control Plane to a Control Plane Group
+### Add a gateway control plane to a control plane group
 
 To assign Gateway control planes to a control plane group, you need to specify the `members` field in the `spec` section of the `KonnectGatewayControlPlane` object.
 
@@ -106,7 +106,7 @@ spec:
 
 You can check in your Gateway Manager to see if the Gateway control plane was successfully added to the control plane group.
 
-## Create a Kubernetes Ingress Controller Control Plane
+## Create a Kubernetes ingress controller control plane
 
 To create a [Kubernetes Ingress Controller Control Plane](/konnect/gateway-manager/kic/), you need to specify the
 `cluster_type` field in the `spec` section of

app/_src/gateway-operator/guides/konnect-entities/key-and-keyset.md

@@ -63,7 +63,7 @@ spec:
 
 At this point, you should see the key in the Gateway Manager UI.
 
-## Create a Key Set
+## Create a key set
 
 Creating the `KongKeySet` object in your Kubernetes cluster will provision a {{site.konnect_product_name}} key set in
 your [Gateway Manager](/konnect/gateway-manager). You can refer to the CR [API](/gateway-operator/{{ page.release
@@ -94,7 +94,7 @@ spec:
 
 At this point, you should see the key set in the Gateway Manager UI.
 
-### Associate the Key with the Key Set
+### Associate the key with the key set
 
 A single `KongKey` can be associated with only one `KongKeySet`. To associate a `KongKey` with a `KongKeySet`, you need
 to update the `KongKey` object with the `keySetRef` field. You can do this by applying the following YAML manifest:

app/_src/gateway-operator/guides/konnect-entities/service-and-route.md

@@ -9,7 +9,7 @@ and [routes](/konnect/gateway-manager/configuration/#routes) natively from your
 {% include md/kgo/konnect-entities-prerequisites.md disable_accordian=false version=page.version release=page.release
 with-control-plane=true %}
 
-## Create a Service
+## Create a service
 
 Creating the `KongService` object in your Kubernetes cluster will provision a {{site.konnect_product_name}} service in
 your [Gateway Manager](/konnect/gateway-manager).
@@ -42,7 +42,7 @@ spec:
 
 At this point, you should see the Service in the Gateway Manager UI.
 
-## Create a Route
+## Create a route
 
 Creating the `KongRoute` object in your Kubernetes cluster will provision a {{site.konnect_product_name}} route in
 your [Gateway Manager](/konnect/gateway-manager).
@@ -51,7 +51,7 @@ You can refer to the CR [API](/gateway-operator/{{ page.release }}/reference/cus
 Your `KongRoute` can either be associated with a `KongService` (and inherit the relation with a `KonnectGatewayControlPlane` from it)
 or be directly associated with a `KonnectGatewayControlPlane` object when referring a `KongService`.
 
-### Associate a Route with a Service
+### Associate a route with a service
 
 You can create a `KongRoute` associated with a `KongService` by applying the following YAML manifest:
 
@@ -79,7 +79,7 @@ spec:
 
 At this point, you should see the Route in the Gateway Manager UI.
 
-### Associate a Route with a Gateway Control Plane
+### Associate a route with a gateway control plane
 
 You can also create a `KongRoute` that won't refer any `KongService`. In that case, you must associate it with a 
 `KonnectGatewayControlPlane` so that {{site.kgo_product_name}} knows what Gateway control plane it should be created in.

app/_src/gateway-operator/guides/konnect-entities/upstream-and-target.md

@@ -9,7 +9,7 @@ and their targets natively from your Kubernetes cluster.
 {% include md/kgo/konnect-entities-prerequisites.md disable_accordian=false version=page.version release=page.release
 with-control-plane=true %}
 
-## Create an Upstream
+## Create an upstream
 
 Creating the `KongUpstream` object in your Kubernetes cluster will provision a {{site.konnect_product_name}} key in
 your [Gateway Manager](/konnect/gateway-manager).
@@ -41,7 +41,7 @@ spec:
 
 At this point, you should see the Upstream in the Gateway Manager UI.
 
-## Create a Target
+## Create a target
 
 Each `KongTarget` must be associated with a `KongUpstream` it's meant to be a backend for. For this reason, you must
 specify the `upstreamRef` field in the `spec` section of the `KongTarget` object. Please refer to the CR [API](

app/_src/gateway-operator/guides/konnect-entities/vault.md

@@ -8,7 +8,7 @@ In this guide you'll learn how to use the `KongVault` custom resource to manage
 {% include md/kgo/konnect-entities-prerequisites.md disable_accordian=false version=page.version release=page.release
 with-control-plane=true %}
 
-## Create a Vault
+## Create a vault
 
 Creating the `KongVault` object in your Kubernetes cluster will provision a {{site.konnect_product_name}} Vault in
 your [Gateway Manager](/konnect/gateway-manager). You can refer to the CR [API](/gateway-operator/{{ page.release

app/gateway-operator/changelog.md

@@ -5,120 +5,6 @@ no_version: true
 
 Changelog for supported {{ site.kgo_product_name }} versions.
 
-## 1.4.0
-
-**Release Date** TBA
-
-### Added
-
-- Proper `User-Agent` header is now set on outgoing HTTP requests.
-  [#387](https://github.com/Kong/gateway-operator/pull/387)
-- Introduce `KongPluginInstallation` CRD to allow installing custom Kong
-  plugins distributed as container images.
-  [#400](https://github.com/Kong/gateway-operator/pull/400), [#424](https://github.com/Kong/gateway-operator/pull/424), [#474](https://github.com/Kong/gateway-operator/pull/474), [#560](https://github.com/Kong/gateway-operator/pull/560), [#615](https://github.com/Kong/gateway-operator/pull/615), [#476](https://github.com/Kong/gateway-operator/pull/476)
-- Extended `DataPlane` API with a possibility to specify `PodDisruptionBudget` to be
-  created for the `DataPlane` deployments via `spec.resources.podDisruptionBudget`.
-  [#464](https://github.com/Kong/gateway-operator/pull/464)
-- Add `KonnectAPIAuthConfiguration` reconciler.
-  [#456](https://github.com/Kong/gateway-operator/pull/456)
-- Add support for Konnect tokens in `Secrets` in `KonnectAPIAuthConfiguration`
-  reconciler.
-  [#459](https://github.com/Kong/gateway-operator/pull/459)
-- Add `KonnectControlPlane` reconciler.
-  [#462](https://github.com/Kong/gateway-operator/pull/462)
-- Add `KongService` reconciler for Konnect control planes.
-  [#470](https://github.com/Kong/gateway-operator/pull/470)
-- Add `KongUpstream` reconciler for Konnect control planes.
-  [#593](https://github.com/Kong/gateway-operator/pull/593)
-- Add `KongConsumer` reconciler for Konnect control planes.
-  [#493](https://github.com/Kong/gateway-operator/pull/493)
-- Add `KongRoute` reconciler for Konnect control planes.
-  [#506](https://github.com/Kong/gateway-operator/pull/506)
-- Add `KongConsumerGroup` reconciler for Konnect control planes.
-  [#510](https://github.com/Kong/gateway-operator/pull/510)
-- Add `KongCACertificate` reconciler for Konnect CA certificates.
-  [#626](https://github.com/Kong/gateway-operator/pull/626)
-- Add `KongCertificate` reconciler for Konnect Certificates.
-  [#643](https://github.com/Kong/gateway-operator/pull/643)
-- Added command line flags to configure the certificate generator job's images.
-  [#516](https://github.com/Kong/gateway-operator/pull/516)
-- Add `KongPluginBinding` reconciler for Konnect Plugins.
-  [#513](https://github.com/Kong/gateway-operator/pull/513), [#535](https://github.com/Kong/gateway-operator/pull/535)
-- Add `KongTarget` reconciler for Konnect Targets.
-  [#627](https://github.com/Kong/gateway-operator/pull/627)
-- Add `KongVault` reconciler for Konnect Vaults.
-  [#597](https://github.com/Kong/gateway-operator/pull/597)
-- Add `KongKey` reconciler for Konnect Keys.
-  [#646](https://github.com/Kong/gateway-operator/pull/646)
-- Add `KongKeySet` reconciler for Konnect KeySets.
-  [#657](https://github.com/Kong/gateway-operator/pull/657)
-- Add `KongDataPlaneClientCertificate` reconciler for Konnect DataPlaneClientCertificates.
-  [#694](https://github.com/Kong/gateway-operator/pull/694)
-- The `KonnectExtension` CRD has been introduced. Such a CRD can be attached
-  to a `DataPlane` via the extensions field to have a konnect-flavored `DataPlane`.
-  [#453](https://github.com/Kong/gateway-operator/pull/453),
-  [#578](https://github.com/Kong/gateway-operator/pull/578),
-  [#736](https://github.com/Kong/gateway-operator/pull/736)
-- Entities created in Konnect are now labeled (or tagged for those that does not
-  support labels) with origin Kubernetes object's metadata: `k8s-name`, `k8s-namespace`,
-  `k8s-uid`, `k8s-generation`, `k8s-kind`, `k8s-group`, `k8s-version`.
-  [#565](https://github.com/Kong/gateway-operator/pull/565)
-- Add `KongService`, `KongRoute`, `KongConsumer`, and `KongConsumerGroup` watchers
-  in the `KongPluginBinding` reconciler.
-  [#571](https://github.com/Kong/gateway-operator/pull/571)
-- Annotating the following resource with the `konghq.com/plugins` annotation results in
-  the creation of a managed `KongPluginBinding` resource:
-  - `KongService` [#550](https://github.com/Kong/gateway-operator/pull/550)
-  - `KongRoute` [#644](https://github.com/Kong/gateway-operator/pull/644)
-  - `KongConsumer` [#676](https://github.com/Kong/gateway-operator/pull/676)
-  - `KongConsumerGroup` [#684](https://github.com/Kong/gateway-operator/pull/684)
-    These `KongPluginBinding`s are taken by the `KongPluginBinding` reconciler
-    to create the corresponding plugin objects in Konnect.
-- `KongConsumer` associated with `ConsumerGroups` is now reconciled in Konnect by removing/adding
-  the consumer from/to the consumer groups.
-  [#592](https://github.com/Kong/gateway-operator/pull/592)
-- Add support for `KongConsumer` credentials:
-  - basic-auth [#625](https://github.com/Kong/gateway-operator/pull/625)
-  - API key [#635](https://github.com/Kong/gateway-operator/pull/635)
-  - ACL [#661](https://github.com/Kong/gateway-operator/pull/661)
-  - JWT [#678](https://github.com/Kong/gateway-operator/pull/678)
-  - HMAC Auth [#687](https://github.com/Kong/gateway-operator/pull/687)
-- Add support for `KongRoute`s bound directly to `KonnectGatewayControlPlane`s (serviceless routes).
-  [#669](https://github.com/Kong/gateway-operator/pull/669)
-- Allow setting `KonnectGatewayControlPlane`s group membership
-  [#697](https://github.com/Kong/gateway-operator/pull/697)
-- Apply Konnect-related customizations to `DataPlane`s that properly reference `KonnectExtension`
-  resources.
-  [#714](https://github.com/Kong/gateway-operator/pull/714)
-- The KonnectExtension functionality is enabled only when the `--enable-controller-konnect`
-  flag or the `GATEWAY_OPERATOR_ENABLE_CONTROLLER_KONNECT` env var is set.
-  [#738](https://github.com/Kong/gateway-operator/pull/738)
-
-### Fixed
-
-- Fixed `ControlPlane` cluster wide resources not migrating to new ownership labels
-  (introduced in 1.3.0) when upgrading the operator form 1.2 (or older) to 1.3.0.
-  [#369](https://github.com/Kong/gateway-operator/pull/369)
-- Requeue instead of reporting an error when a finalizer removal yields a conflict.
-  [#454](https://github.com/Kong/gateway-operator/pull/454)
-- Requeue instead of reporting an error when a GatewayClass status update yields a conflict.
-  [#612](https://github.com/Kong/gateway-operator/pull/612)
-- Guard object counters with checks whether CRDs for them exist
-  [#710](https://github.com/Kong/gateway-operator/pull/710)
-- Do not reconcile Gateways nor assign any finalizers when the referred GatewayClass is not supported.
-  [#711](https://github.com/Kong/gateway-operator/pull/711)
-- Fixed setting `ExternalTrafficPolicy` on `DataPlane`'s ingress `Service` during update and patch operations.
-  [#750](https://github.com/Kong/gateway-operator/pull/750)
-
-### Changes
-
-- Default version of `ControlPlane` is bumped to 3.3.1
-  [#580](https://github.com/Kong/gateway-operator/pull/580)
-- Default version of `DataPlane` is bumped to 3.8.0
-  [#572](https://github.com/Kong/gateway-operator/pull/572)
-- Gateway API has been bumped to v1.2.0
-  [#674](https://github.com/Kong/gateway-operator/pull/674)
-
 ## 1.3.0
 
 **Release Date** 2024/06/24