chore(releasing): Prepare v0.23.0 release

Signed-off-by: Jesse Szwedko <jesse@szwedko.me>
vectordotdev · Jul 8, 2022 · d91ff35 · d91ff35
1 parent 8df13fc
commit d91ff35
Show file tree

Hide file tree

Showing 7 changed files with 798 additions and 32 deletions.
diff --git a/distribution/install.sh b/distribution/install.sh
@@ -12,7 +12,7 @@ set -u
 
 # If PACKAGE_ROOT is unset or empty, default it.
 PACKAGE_ROOT="${PACKAGE_ROOT:-"https://packages.timber.io/vector"}"
-VECTOR_VERSION="0.22.2"
+VECTOR_VERSION="0.23.0"
 _divider="--------------------------------------------------------------------------------"
 _prompt=">>>"
 _indent="   "

diff --git a/website/content/en/highlights/2022-05-03-0-22-0-upgrade-guide.md b/website/content/en/highlights/2022-05-03-0-22-0-upgrade-guide.md
@@ -13,7 +13,6 @@ badges:
 Vector's 0.22.0 release includes **breaking changes**:
 
 1. [`gcp_stackdriver_metrics` configuration change](#stackdriver-metrics)
-2. [`kubernetes_logs` source now requires rights to list and watch nodes](#kubernetes-logs-list-watch-nodes)
 3. [VRL now supports template strings](#vrl-template-strings)
 4. [`encode_key_value` and `encode_logfmt` quote wrapping behavior change](#encode-key-value-quote-wrapping)
 
@@ -33,35 +32,7 @@ The `gcp_stackdriver_metrics` sink now matches the `gcp_stackdriver_logs`
 configuration, and doesn't require an additional `labels` section to add
 labels to submitted metrics.
 
-#### `kubernetes_logs` source now requires rights to list and watch nodes {#kubernetes-logs-list-watch-nodes}
-
-Logs from Kubernetes pods are now annotated with a node's labels on which a pod is running.
-
-1. For official helm-chart users, upgrade the chart to the version >= [0.11.0](https://github.com/vectordotdev/helm-charts/releases/tag/vector-0.11.0)
-   before upgrading the vector version in your cluster.
-2. For custom vector installations, modify the cluster role assigned to the vector service account to include nodes.
-   The result should look like the following snippet:
-
-```yaml
-# Permissions to use Kubernetes API.
-# Requires that RBAC authorization is enabled.
-apiVersion: rbac.authorization.k8s.io/v1
-kind: ClusterRole
-metadata:
-  name: vector
-rules:
-  - apiGroups:
-      - ""
-    resources:
-      - namespaces
-      - nodes
-      - pods
-    verbs:
-      - list
-      - watch
-```
-
-### TOML transform example
+##### TOML transform example
 
 Old configuration
 

diff --git a/website/content/en/highlights/2022-07-07-0-23-0-upgrade-guide.md b/website/content/en/highlights/2022-07-07-0-23-0-upgrade-guide.md
@@ -20,6 +20,8 @@ Vector's 0.23.0 release includes **breaking changes**:
 7. [`gcp_pubsub` sink requires setting `encoding` option](#gcp_sink-mandatory-encoding)
 8. [`humio_metrics` sink no longer has `encoding` option](#humio_metrics-sink-fixed-encoding)
 9. [New `framing` and `encoding` options for sinks](#sinks-framing-encoding-options)
+10. [Support for older OSes dropped](#old-oses)
+11. [`kubernetes_logs` source now requires rights to list and watch nodes](#kubernetes-logs-list-watch-nodes)
 
 and **deprecations**:
 
@@ -300,6 +302,47 @@ The following sinks support setting an encoding codec: `aws_cloudwatch_logs`,
 Additionally, the following sinks support setting a framing method: `aws_s3`, `azure_blob`,
 `console`, `file`, `gcp_cloud_storage`, `http` and `socket`.
 
+#### Support for older OSes dropped {#old-oses}
+
+Due to changes to the [tool we use for cross-compiling Vector](https://github.com/cross-rs/cross), support for operating
+systems with old versions of `libstdc++` were dropped for the `x86-uknown_linux-gnu` target. Vector now requires that
+the host system has `libstdc++` >= 3.4.21 with support for ABI version 1.3.8.
+
+Known OSes that this affects:
+
+- Amazon Linux 1
+- Ubuntu 14.04
+
+We will be looking at options to re-add support for these OSes in the future.
+
+#### `kubernetes_logs` source now requires rights to list and watch nodes {#kubernetes-logs-list-watch-nodes}
+
+Logs from Kubernetes pods are now annotated with a node's labels on which a pod is running.
+
+1. For official helm-chart users, upgrade the chart to the version >= [0.11.0](https://github.com/vectordotdev/helm-charts/releases/tag/vector-0.11.0)
+   before upgrading the vector version in your cluster.
+2. For custom vector installations, modify the cluster role assigned to the vector service account to include nodes.
+   The result should look like the following snippet:
+
+```yaml
+# Permissions to use Kubernetes API.
+# Requires that RBAC authorization is enabled.
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+  name: vector
+rules:
+  - apiGroups:
+      - ""
+    resources:
+      - namespaces
+      - nodes
+      - pods
+    verbs:
+      - list
+      - watch
+```
+
 ### Deprecations
 
 #### Shorthand values for `encoding` options deprecated {#deprecated-encoding-shorthand}

diff --git a/website/content/en/releases/0.23.0.md b/website/content/en/releases/0.23.0.md
@@ -0,0 +1,4 @@
+---
+title: Vector v0.23.0 release notes
+weight: 21
+---
diff --git a/website/cue/reference/administration/interfaces/kubectl.cue b/website/cue/reference/administration/interfaces/kubectl.cue
@@ -19,7 +19,7 @@ administration: interfaces: kubectl: {
 	role_implementations: [Name=string]: {
 		commands: {
 			_deployment_variant:       string
-			_vector_version:           "0.22"
+			_vector_version:           "0.23"
 			_namespace:                string | *"vector"
 			_controller_resource_type: string
 			_controller_resource_name: string | *_deployment_variant