From f1effc11336840504b81960c434b4a6cdd273934 Mon Sep 17 00:00:00 2001
From: Aliaksandr Valialkin <valyala@victoriametrics.com>
Date: Tue, 30 Jan 2024 23:37:25 +0200
Subject: [PATCH] all: update VictoriaMetrics Docker image from v1.96.0 to
v1.97.0
See https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.97.0
---
deployment/docker/docker-compose-cluster.yml | 16 +++++++-------
deployment/docker/docker-compose.yml | 6 ++---
.../vmanomaly-integration/docker-compose.yml | 6 ++---
deployment/logs-benchmark/docker-compose.yml | 2 +-
.../files/etc/update-motd.d/99-one-click | 4 ++--
.../guides/guide-vmanomaly-vmalert.md | 12 +++++-----
docs/enterprise.md | 22 +++++++++----------
7 files changed, 34 insertions(+), 34 deletions(-)
diff --git a/deployment/docker/docker-compose-cluster.yml b/deployment/docker/docker-compose-cluster.yml
index 584e46bcc0..9b19b9c729 100644
--- a/deployment/docker/docker-compose-cluster.yml
+++ b/deployment/docker/docker-compose-cluster.yml
@@ -2,7 +2,7 @@ version: '3.5'
services:
vmagent:
container_name: vmagent
- image: victoriametrics/vmagent:v1.96.0
+ image: victoriametrics/vmagent:v1.97.0
depends_on:
- "vminsert"
ports:
@@ -33,7 +33,7 @@ services:
vmstorage-1:
container_name: vmstorage-1
- image: victoriametrics/vmstorage:v1.96.0-cluster
+ image: victoriametrics/vmstorage:v1.97.0-cluster
ports:
- 8482
- 8400
@@ -45,7 +45,7 @@ services:
restart: always
vmstorage-2:
container_name: vmstorage-2
- image: victoriametrics/vmstorage:v1.96.0-cluster
+ image: victoriametrics/vmstorage:v1.97.0-cluster
ports:
- 8482
- 8400
@@ -58,7 +58,7 @@ services:
vminsert:
container_name: vminsert
- image: victoriametrics/vminsert:v1.96.0-cluster
+ image: victoriametrics/vminsert:v1.97.0-cluster
depends_on:
- "vmstorage-1"
- "vmstorage-2"
@@ -71,7 +71,7 @@ services:
vmselect-1:
container_name: vmselect-1
- image: victoriametrics/vmselect:v1.96.0-cluster
+ image: victoriametrics/vmselect:v1.97.0-cluster
depends_on:
- "vmstorage-1"
- "vmstorage-2"
@@ -85,7 +85,7 @@ services:
vmselect-2:
container_name: vmselect-2
- image: victoriametrics/vmselect:v1.96.0-cluster
+ image: victoriametrics/vmselect:v1.97.0-cluster
depends_on:
- "vmstorage-1"
- "vmstorage-2"
@@ -99,7 +99,7 @@ services:
vmauth:
container_name: vmauth
- image: victoriametrics/vmauth:v1.96.0
+ image: victoriametrics/vmauth:v1.97.0
depends_on:
- "vmselect-1"
- "vmselect-2"
@@ -114,7 +114,7 @@ services:
vmalert:
container_name: vmalert
- image: victoriametrics/vmalert:v1.96.0
+ image: victoriametrics/vmalert:v1.97.0
depends_on:
- "vmauth"
ports:
diff --git a/deployment/docker/docker-compose.yml b/deployment/docker/docker-compose.yml
index dd786c7ec4..369eee536f 100644
--- a/deployment/docker/docker-compose.yml
+++ b/deployment/docker/docker-compose.yml
@@ -2,7 +2,7 @@ version: "3.5"
services:
vmagent:
container_name: vmagent
- image: victoriametrics/vmagent:v1.96.0
+ image: victoriametrics/vmagent:v1.97.0
depends_on:
- "victoriametrics"
ports:
@@ -18,7 +18,7 @@ services:
restart: always
victoriametrics:
container_name: victoriametrics
- image: victoriametrics/victoria-metrics:v1.96.0
+ image: victoriametrics/victoria-metrics:v1.97.0
ports:
- 8428:8428
- 8089:8089
@@ -58,7 +58,7 @@ services:
restart: always
vmalert:
container_name: vmalert
- image: victoriametrics/vmalert:v1.96.0
+ image: victoriametrics/vmalert:v1.97.0
depends_on:
- "victoriametrics"
- "alertmanager"
diff --git a/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml b/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml
index 009eeda80f..80ce540889 100644
--- a/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml
+++ b/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml
@@ -1,7 +1,7 @@
services:
vmagent:
container_name: vmagent
- image: victoriametrics/vmagent:v1.96.0
+ image: victoriametrics/vmagent:v1.97.0
depends_on:
- "victoriametrics"
ports:
@@ -18,7 +18,7 @@ services:
victoriametrics:
container_name: victoriametrics
- image: victoriametrics/victoria-metrics:v1.96.0
+ image: victoriametrics/victoria-metrics:v1.97.0
ports:
- 8428:8428
volumes:
@@ -51,7 +51,7 @@ services:
vmalert:
container_name: vmalert
- image: victoriametrics/vmalert:v1.96.0
+ image: victoriametrics/vmalert:v1.97.0
depends_on:
- "victoriametrics"
ports:
diff --git a/deployment/logs-benchmark/docker-compose.yml b/deployment/logs-benchmark/docker-compose.yml
index b65fc3fd1f..ddb4f66f27 100644
--- a/deployment/logs-benchmark/docker-compose.yml
+++ b/deployment/logs-benchmark/docker-compose.yml
@@ -46,7 +46,7 @@ services:
- '--config=/config.yml'
vmsingle:
- image: victoriametrics/victoria-metrics:v1.96.0
+ image: victoriametrics/victoria-metrics:v1.97.0
ports:
- '8428:8428'
command:
diff --git a/deployment/marketplace/digitialocean/one-click-droplet/files/etc/update-motd.d/99-one-click b/deployment/marketplace/digitialocean/one-click-droplet/files/etc/update-motd.d/99-one-click
index 4a0d741305..f17690f5cd 100755
--- a/deployment/marketplace/digitialocean/one-click-droplet/files/etc/update-motd.d/99-one-click
+++ b/deployment/marketplace/digitialocean/one-click-droplet/files/etc/update-motd.d/99-one-click
@@ -19,8 +19,8 @@ On the server:
* VictoriaMetrics is running on ports: 8428, 8089, 4242, 2003 and they are bound to the local interface.
********************************************************************************
- # This image includes 1.96.0 version of VictoriaMetrics.
- # See Release notes https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.96.0
+ # This image includes 1.97.0 version of VictoriaMetrics.
+ # See Release notes https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.97.0
# Welcome to VictoriaMetrics droplet!
diff --git a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert.md b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert.md
index bc42981c5e..71371ffbe2 100644
--- a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert.md
+++ b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert.md
@@ -19,9 +19,9 @@ aliases:
- To use *vmanomaly*, part of the enterprise package, a license key is required. Obtain your key [here](https://victoriametrics.com/products/enterprise/trial/) for this tutorial or for enterprise use.
- In the tutorial, we'll be using the following VictoriaMetrics components:
- - [VictoriaMetrics Single-Node](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html) (v.1.96.0)
- - [vmalert](https://docs.victoriametrics.com/vmalert.html) (v.1.96.0)
- - [vmagent](https://docs.victoriametrics.com/vmagent.html) (v.1.96.0)
+ - [VictoriaMetrics Single-Node](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html) (v.1.97.0)
+ - [vmalert](https://docs.victoriametrics.com/vmalert.html) (v.1.97.0)
+ - [vmagent](https://docs.victoriametrics.com/vmagent.html) (v.1.97.0)
- [Grafana](https://grafana.com/)(v.10.2.1)
- [Docker](https://docs.docker.com/get-docker/) and [Docker Compose](https://docs.docker.com/compose/)
- [Node exporter](https://github.com/prometheus/node_exporter#node-exporter)(v1.7.0) and [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/)(v0.25.0)
@@ -322,7 +322,7 @@ Let's wrap it all up together into the `docker-compose.yml` file.
services:
vmagent:
container_name: vmagent
- image: victoriametrics/vmagent:v1.96.0
+ image: victoriametrics/vmagent:v1.97.0
depends_on:
- "victoriametrics"
ports:
@@ -339,7 +339,7 @@ services:
victoriametrics:
container_name: victoriametrics
- image: victoriametrics/victoria-metrics:v1.96.0
+ image: victoriametrics/victoria-metrics:v1.97.0
ports:
- 8428:8428
volumes:
@@ -372,7 +372,7 @@ services:
vmalert:
container_name: vmalert
- image: victoriametrics/vmalert:v1.96.0
+ image: victoriametrics/vmalert:v1.97.0
depends_on:
- "victoriametrics"
ports:
diff --git a/docs/enterprise.md b/docs/enterprise.md
index 93952d4e01..5334a840ff 100644
--- a/docs/enterprise.md
+++ b/docs/enterprise.md
@@ -81,7 +81,7 @@ VictoriaMetrics Enterprise components are available in the following forms:
It is allowed to run VictoriaMetrics Enterprise components in [cases listed here](#valid-cases-for-victoriametrics-enterprise).
Binary releases of VictoriaMetrics Enterprise are available [at the releases page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest).
-Enterprise binaries and packages have `enterprise` suffix in their names. For example, `victoria-metrics-linux-amd64-v1.96.0-enterprise.tar.gz`.
+Enterprise binaries and packages have `enterprise` suffix in their names. For example, `victoria-metrics-linux-amd64-v1.97.0-enterprise.tar.gz`.
In order to run binary release of VictoriaMetrics Enterprise component, please download the `*-enterprise.tar.gz` archive for your OS and architecture
from the [releases page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest) and unpack it. Then run the unpacked binary.
@@ -101,8 +101,8 @@ For example, the following command runs VictoriaMetrics Enterprise binary with t
obtained at [this page](https://victoriametrics.com/products/enterprise/trial/):
```sh
-wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.96.0/victoria-metrics-linux-amd64-v1.96.0-enterprise.tar.gz
-tar -xzf victoria-metrics-linux-amd64-v1.96.0-enterprise.tar.gz
+wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.97.0/victoria-metrics-linux-amd64-v1.97.0-enterprise.tar.gz
+tar -xzf victoria-metrics-linux-amd64-v1.97.0-enterprise.tar.gz
./victoria-metrics-prod -license=BASE64_ENCODED_LICENSE_KEY
```
@@ -117,7 +117,7 @@ Alternatively, VictoriaMetrics Enterprise license can be stored in the file and
It is allowed to run VictoriaMetrics Enterprise components in [cases listed here](#valid-cases-for-victoriametrics-enterprise).
Docker images for VictoriaMetrics Enterprise are available [at VictoriaMetrics DockerHub](https://hub.docker.com/u/victoriametrics).
-Enterprise docker images have `enterprise` suffix in their names. For example, `victoriametrics/victoria-metrics:v1.96.0-enteprise`.
+Enterprise docker images have `enterprise` suffix in their names. For example, `victoriametrics/victoria-metrics:v1.97.0-enteprise`.
In order to run Docker image of VictoriaMetrics Enterprise component, it is required to provide the license key via command-line
flag as described [here](#binary-releases).
@@ -127,13 +127,13 @@ Enterprise license key can be obtained at [this page](https://victoriametrics.co
For example, the following command runs VictoriaMetrics Enterprise Docker image with the specified license key:
```sh
-docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.96.0-enteprise -license=BASE64_ENCODED_LICENSE_KEY
+docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.97.0-enteprise -license=BASE64_ENCODED_LICENSE_KEY
```
Alternatively, the license code can be stored in the file and then referred via `-licenseFile` command-line flag:
```sh
-docker run --name=victoria-metrics -v /vm-license:/vm-license victoriametrics/victoria-metrics:v1.96.0-enteprise -licenseFile=/path/to/vm-license
+docker run --name=victoria-metrics -v /vm-license:/vm-license victoriametrics/victoria-metrics:v1.97.0-enteprise -licenseFile=/path/to/vm-license
```
Example docker-compose configuration:
@@ -142,7 +142,7 @@ version: "3.5"
services:
victoriametrics:
container_name: victoriametrics
- image: victoriametrics/victoria-metrics:v1.96.0
+ image: victoriametrics/victoria-metrics:v1.97.0
ports:
- 8428:8428
volumes:
@@ -174,7 +174,7 @@ is used to provide key in plain-text:
```yaml
server:
image:
- tag: v1.96.0-enterprise
+ tag: v1.97.0-enterprise
license:
key: {BASE64_ENCODED_LICENSE_KEY}
@@ -185,7 +185,7 @@ In order to provide key via existing secret, the following values file is used:
```yaml
server:
image:
- tag: v1.96.0-enterprise
+ tag: v1.97.0-enterprise
license:
secret:
@@ -232,7 +232,7 @@ spec:
license:
key: {BASE64_ENCODED_LICENSE_KEY}
image:
- tag: v1.96.0-enterprise
+ tag: v1.97.0-enterprise
```
In order to provide key via existing secret, the following custom resource is used:
@@ -249,7 +249,7 @@ spec:
name: vm-license
key: license
image:
- tag: v1.96.0-enterprise
+ tag: v1.97.0-enterprise
```
Example secret with license key: