[DOCU-2469] Changelog for 3.0

.github/styles/kong/dictionary.txt

@@ -84,6 +84,7 @@ jwk
 jwks
 jwt
 Keycloak
+keyspace
 kiali
 kibibytes
 Knative
@@ -220,6 +221,7 @@ uncomment
 uncommenting
 Unicode
 unix
+unnormalized
 unprocessable
 unpublish
 unregister

app/_data/docs_nav_gateway_3.0.x.yml

@@ -185,14 +185,12 @@ items:
         url: /production/clustering
       - text: Logging Reference
         url: /production/logging
-      - text: Upgrade Kong Gateway
+      - text: Upgrade and Migration
         items:
-          - text: Upgrade Kong Enterprise
-            url: /upgrade/enterprise
-          - text: Upgrade Kong Gateway OSS
-            url: /upgrade/oss
-          - text: Migrate from OSS to EE
-            url: /upgrade/migrate-ce-to-ke
+          - text: Upgrade Kong Gateway
+            url: /upgrade/
+          - text: Migrate from OSS to Enterprise
+            url: /migrate-ce-to-ke/
   - title: Kong Enterprise
     icon: /assets/images/icons/documentation/icn-enterprise-blue.svg
     items:

app/_hub/kong-inc/prometheus/_index.md

@@ -102,7 +102,7 @@ data plane nodes is exported to control plane.
 license signature. Those metrics are only exported on {{site.base_gateway}}.
 - **DB Entity Count** <span class="badge enterprise"></span> : A gauge metric that
     measures the current number of database entities.
-- **Number of Nginx timers** : A gauge metric that measures the total number of Nginx 
+- **Number of Nginx timers** : A gauge metric that measures the total number of Nginx
     timers, in Running or Pending state.
 
 Following metrics are disabled by default as it may create high cardinality of metrics and may
@@ -112,7 +112,7 @@ When `status_code_metrics` is set to true:
 - **Status codes**: HTTP status codes returned by upstream services.
   These are available per service, across all services, and per route per consumer.
 
-When `lantency_metrics` is set to to true:
+When `lantency_metrics` is set to true:
 - **Latencies Histograms**: Latency (in ms), as measured at Kong:
    - **Request**: Total time taken by Kong and upstream services to serve
      requests.
@@ -298,7 +298,7 @@ allow access to the `/metrics` endpoint to Prometheus:
   * `http_status` to `http_requests_total`
   * `latency` to `kong_request_latency_ms`/`kong_upstream_latency_ms`/`kong_kong_latency_ms`
   * `kong_bandwidh` to `kong_bandwidth_bytes`
-  * `nginx_http_current_connections`/`nginx_stream_current_connections` to `nginx_hconnections_total`
+  * `nginx_http_current_connections`/`nginx_stream_current_connections` to `nginx_connections_total`
   * Removed: `http_consumer_status`
 * New metric: `session_duration_ms` for monitoring stream connections
 * New metric: `node_info` is a single gauge set to 1 that outputs the node's ID and {{site.base_gateway}} version
@@ -307,7 +307,6 @@ allow access to the `/metrics` endpoint to Prometheus:
 * `request_count` and `consumer_status` were merged into `http_requests_total`. If the `per_consumer` config is set to false, the `consumer` label will be empty.  If the `per_consumer` config is true, the `consumer` label will be filled.
 * `http_requests_total` has a new label [`source`](/gateway/latest/plugin-development/pdk/kong.response/#kongresponseget_source/). It can be set to `exit`, `error`, or `service`.
 * All Memory metrics have a new label, `node_id`.
-* `nginx_http_current_connections` merged with `nginx_stream_current_connection` to `nginx_current_connections`
 * Plugin version bumped to 3.0.0
 * The `node_id` label was added to memory metrics.
 

app/moved_urls.yml

@@ -11,9 +11,9 @@
 /gateway/VERSION/install-and-run/debian/: "/gateway/VERSION/install/linux/debian/"
 /gateway/VERSION/install-and-run/rhel/: "/gateway/VERSION/install/linux/rhel/"
 /gateway/VERSION/install-and-run/ubuntu/: "/gateway/VERSION/install/linux/ubuntu/"
-/gateway/VERSION/install-and-run/migrate-ce-to-ke/: "/gateway/VERSION/upgrade/migrate-ce-to-ke/"
-/gateway/VERSION/install-and-run/upgrade-enterprise/: "/gateway/VERSION/upgrade/enterprise/"
-/gateway/VERSION/install-and-run/upgrade-oss/: "/gateway/VERSION/upgrade/oss/"
+/gateway/VERSION/install-and-run/migrate-ce-to-ke/: "/gateway/VERSION/migrate-ce-to-ke/"
+/gateway/VERSION/install-and-run/upgrade-enterprise/: "/gateway/VERSION/upgrade/"
+/gateway/VERSION/install-and-run/upgrade-oss/: "/gateway/VERSION/upgrade/"
 /gateway/2.8.x/get-started/quickstart/: "/gateway/VERSION/get-started/"
 /gateway/2.8.x/get-started/quickstart/configuring-a-service/: "/gateway/VERSION/get-started/services-and-routes/"
 /gateway/2.8.x/get-started/quickstart/configuring-a-grpc-service/: "/gateway/VERSION/kong-plugins/configuring-a-grpc-service"

src/gateway/migrate-ce-to-ke.md

@@ -0,0 +1,37 @@
+---
+title: Migrating from Kong Gateway (OSS) to Kong Gateway
+toc: true
+---
+
+Run `kong migrations` commands to migrate from an open-source {{site.base_gateway}} installation to an Enterprise one.
+
+You can only migrate to a {{site.ee_product_name}} version that
+supports the same {{site.ce_product_name}} version.
+
+## Prerequisites
+
+{:.warning}
+> **Warning:** This action is irreversible, therefore it is strongly
+   recommended to back up your production data before migrating from
+   {{site.ce_product_name}} to {{site.ee_product_name}}.
+
+If running a version of {{site.ce_product_name}} earlier than 3.0.x,
+[upgrade to {{site.ce_product_name}} 3.0.x](/gateway/{{page.kong_version}}/upgrade/) before migrating
+{{site.ce_product_name}} to {{site.ee_product_name}} 3.0.x.
+
+## Migration steps
+
+The following steps guide you through the migration process.
+
+1. [Download](/gateway/{{page.kong_version}}/install) the {{site.base_gateway}}
+3.0.x Enterprise package and configure it to point to the same data store as your
+{{site.ce_product_name}} 2.8.x node. The migration command expects the data store
+to be up to date on any pending migration:
+
+   ```shell
+   kong migrations up [-c configuration_file]
+   kong migrations finish [-c configuration_file]
+   ```
+
+2. Confirm that all of the entities are now available on your
+   {{site.ee_product_name}} node.