deployment: update references to VictoriaMetrics components from v1.94.0 to v1.95.0

This commit is contained in:
Aliaksandr Valialkin 2023-11-15 20:35:11 +01:00
parent 0ea35215f6
commit 9b248e3b2f
No known key found for this signature in database
GPG key ID: A72BEC6CD3D0DED1
5 changed files with 25 additions and 25 deletions

View file

@ -2,7 +2,7 @@ version: '3.5'
services:
vmagent:
container_name: vmagent
image: victoriametrics/vmagent:v1.94.0
image: victoriametrics/vmagent:v1.95.0
depends_on:
- "vminsert"
ports:
@ -32,7 +32,7 @@ services:
vmstorage-1:
container_name: vmstorage-1
image: victoriametrics/vmstorage:v1.94.0-cluster
image: victoriametrics/vmstorage:v1.95.0-cluster
ports:
- 8482
- 8400
@ -44,7 +44,7 @@ services:
restart: always
vmstorage-2:
container_name: vmstorage-2
image: victoriametrics/vmstorage:v1.94.0-cluster
image: victoriametrics/vmstorage:v1.95.0-cluster
ports:
- 8482
- 8400
@ -57,7 +57,7 @@ services:
vminsert:
container_name: vminsert
image: victoriametrics/vminsert:v1.94.0-cluster
image: victoriametrics/vminsert:v1.95.0-cluster
depends_on:
- "vmstorage-1"
- "vmstorage-2"
@ -70,7 +70,7 @@ services:
vmselect-1:
container_name: vmselect-1
image: victoriametrics/vmselect:v1.94.0-cluster
image: victoriametrics/vmselect:v1.95.0-cluster
depends_on:
- "vmstorage-1"
- "vmstorage-2"
@ -84,7 +84,7 @@ services:
vmselect-2:
container_name: vmselect-2
image: victoriametrics/vmselect:v1.94.0-cluster
image: victoriametrics/vmselect:v1.95.0-cluster
depends_on:
- "vmstorage-1"
- "vmstorage-2"
@ -98,7 +98,7 @@ services:
vmauth:
container_name: vmauth
image: victoriametrics/vmauth:v1.94.0
image: victoriametrics/vmauth:v1.95.0
depends_on:
- "vmselect-1"
- "vmselect-2"
@ -113,7 +113,7 @@ services:
vmalert:
container_name: vmalert
image: victoriametrics/vmalert:v1.94.0
image: victoriametrics/vmalert:v1.95.0
depends_on:
- "vmauth"
ports:

View file

@ -2,7 +2,7 @@ version: "3.5"
services:
vmagent:
container_name: vmagent
image: victoriametrics/vmagent:v1.94.0
image: victoriametrics/vmagent:v1.95.0
depends_on:
- "victoriametrics"
ports:
@ -18,7 +18,7 @@ services:
restart: always
victoriametrics:
container_name: victoriametrics
image: victoriametrics/victoria-metrics:v1.94.0
image: victoriametrics/victoria-metrics:v1.95.0
ports:
- 8428:8428
- 8089:8089
@ -57,7 +57,7 @@ services:
restart: always
vmalert:
container_name: vmalert
image: victoriametrics/vmalert:v1.94.0
image: victoriametrics/vmalert:v1.95.0
depends_on:
- "victoriametrics"
- "alertmanager"

View file

@ -46,7 +46,7 @@ services:
- '--config=/config.yml'
vmsingle:
image: victoriametrics/victoria-metrics:v1.94.0
image: victoriametrics/victoria-metrics:v1.95.0
ports:
- '8428:8428'
command:

View file

@ -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.94.0 version of VictoriaMetrics.
# See Release notes https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.94.0
# This image includes 1.95.0 version of VictoriaMetrics.
# See Release notes https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.95.0
# Welcome to VictoriaMetrics droplet!

View file

@ -80,7 +80,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.94.0-enterprise.tar.gz`.
Enterprise binaries and packages have `enterprise` suffix in their names. For example, `victoria-metrics-linux-amd64-v1.95.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.
@ -100,8 +100,8 @@ For example, the following command runs VictoriaMetrics Enterprise binary with t
obtained at [this page](https://victoriametrics.com/products/enterprise/trial/):
```console
wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.94.0/victoria-metrics-linux-amd64-v1.94.0-enterprise.tar.gz
tar -xzf victoria-metrics-linux-amd64-v1.94.0-enterprise.tar.gz
wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.95.0/victoria-metrics-linux-amd64-v1.95.0-enterprise.tar.gz
tar -xzf victoria-metrics-linux-amd64-v1.95.0-enterprise.tar.gz
./victoria-metrics-prod -license=BASE64_ENCODED_LICENSE_KEY
```
@ -116,7 +116,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.94.0-enteprise`.
Enterprise docker images have `enterprise` suffix in their names. For example, `victoriametrics/victoria-metrics:v1.95.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).
@ -126,13 +126,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:
```console
docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.94.0-enteprise -license=BASE64_ENCODED_LICENSE_KEY
docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.95.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:
```console
docker run --name=victoria-metrics -v /vm-license:/vm-license victoriametrics/victoria-metrics:v1.94.0-enteprise -licenseFile=/path/to/vm-license
docker run --name=victoria-metrics -v /vm-license:/vm-license victoriametrics/victoria-metrics:v1.95.0-enteprise -licenseFile=/path/to/vm-license
```
Example docker-compose configuration:
@ -141,7 +141,7 @@ version: "3.5"
services:
victoriametrics:
container_name: victoriametrics
image: victoriametrics/victoria-metrics:v1.94.0
image: victoriametrics/victoria-metrics:v1.95.0
ports:
- 8428:8428
volumes:
@ -173,7 +173,7 @@ is used to provide key in plain-text:
```yaml
server:
image:
tag: v1.94.0-enterprise
tag: v1.95.0-enterprise
license:
key: {BASE64_ENCODED_LICENSE_KEY}
@ -184,7 +184,7 @@ In order to provide key via existing secret, the following values file is used:
```yaml
server:
image:
tag: v1.94.0-enterprise
tag: v1.95.0-enterprise
license:
secret:
@ -231,7 +231,7 @@ spec:
license:
key: {BASE64_ENCODED_LICENSE_KEY}
image:
tag: v1.94.0-enterprise
tag: v1.95.0-enterprise
```
In order to provide key via existing secret, the following custom resource is used:
@ -248,7 +248,7 @@ spec:
name: vm-license
key: license
image:
tag: v1.94.0-enterprise
tag: v1.95.0-enterprise
```
Example secret with license key: