From 577a7a247d8be40f9a1936a039ec34d2373f6f00 Mon Sep 17 00:00:00 2001 From: Zakhar Bessarab Date: Tue, 5 Nov 2024 14:40:13 -0300 Subject: [PATCH] {docker,docs}: update references to latest release Update references to latest release - v1.106.0. --------- Signed-off-by: Zakhar Bessarab (cherry picked from commit be677065bc9d99a276f50bbc309dfbe206942c2a) --- deployment/docker/docker-compose-cluster.yml | 16 +++++++------- .../docker/docker-compose-victorialogs.yml | 6 ++--- deployment/docker/docker-compose.yml | 6 ++--- .../docker/victorialogs/compose-base.yml | 2 +- .../vmanomaly-integration/docker-compose.yml | 6 ++--- deployment/logs-benchmark/docker-compose.yml | 2 +- .../guides/guide-vmanomaly-vmalert/README.md | 12 +++++----- docs/enterprise.md | 22 +++++++++---------- .../README.md | 16 +++++++------- docs/scrape_config_examples.md | 8 +++---- 10 files changed, 48 insertions(+), 48 deletions(-) diff --git a/deployment/docker/docker-compose-cluster.yml b/deployment/docker/docker-compose-cluster.yml index 0ebe2e757..92d67ac8a 100644 --- a/deployment/docker/docker-compose-cluster.yml +++ b/deployment/docker/docker-compose-cluster.yml @@ -4,7 +4,7 @@ services: # And forward them to --remoteWrite.url vmagent: container_name: vmagent - image: victoriametrics/vmagent:v1.105.0 + image: victoriametrics/vmagent:v1.106.0 depends_on: - "vminsert" ports: @@ -39,7 +39,7 @@ services: # where N is number of vmstorages (2 in this case). vmstorage-1: container_name: vmstorage-1 - image: victoriametrics/vmstorage:v1.105.0-cluster + image: victoriametrics/vmstorage:v1.106.0-cluster ports: - 8482 - 8400 @@ -51,7 +51,7 @@ services: restart: always vmstorage-2: container_name: vmstorage-2 - image: victoriametrics/vmstorage:v1.105.0-cluster + image: victoriametrics/vmstorage:v1.106.0-cluster ports: - 8482 - 8400 @@ -66,7 +66,7 @@ services: # pre-process them and distributes across configured vmstorage shards. vminsert: container_name: vminsert - image: victoriametrics/vminsert:v1.105.0-cluster + image: victoriametrics/vminsert:v1.106.0-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -81,7 +81,7 @@ services: # vmselect collects results from configured `--storageNode` shards. vmselect-1: container_name: vmselect-1 - image: victoriametrics/vmselect:v1.105.0-cluster + image: victoriametrics/vmselect:v1.106.0-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -94,7 +94,7 @@ services: restart: always vmselect-2: container_name: vmselect-2 - image: victoriametrics/vmselect:v1.105.0-cluster + image: victoriametrics/vmselect:v1.106.0-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -112,7 +112,7 @@ services: # It can be used as an authentication proxy. vmauth: container_name: vmauth - image: victoriametrics/vmauth:v1.105.0 + image: victoriametrics/vmauth:v1.106.0 depends_on: - "vmselect-1" - "vmselect-2" @@ -127,7 +127,7 @@ services: # vmalert executes alerting and recording rules vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.105.0 + image: victoriametrics/vmalert:v1.106.0 depends_on: - "vmauth" ports: diff --git a/deployment/docker/docker-compose-victorialogs.yml b/deployment/docker/docker-compose-victorialogs.yml index 48a5c2add..6c329872f 100644 --- a/deployment/docker/docker-compose-victorialogs.yml +++ b/deployment/docker/docker-compose-victorialogs.yml @@ -55,7 +55,7 @@ services: # scraping, storing metrics and serve read requests. victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.105.0 + image: victoriametrics/victoria-metrics:v1.106.0 ports: - 8428:8428 volumes: @@ -74,7 +74,7 @@ services: # depending on the requested path. vmauth: container_name: vmauth - image: victoriametrics/vmauth:v1.105.0 + image: victoriametrics/vmauth:v1.106.0 depends_on: - "victoriametrics" - "victorialogs" @@ -91,7 +91,7 @@ services: # vmalert executes alerting and recording rules according to given rule type. vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.105.0 + image: victoriametrics/vmalert:v1.106.0 depends_on: - "vmauth" - "alertmanager" diff --git a/deployment/docker/docker-compose.yml b/deployment/docker/docker-compose.yml index 8d279fba1..da7a58a5e 100644 --- a/deployment/docker/docker-compose.yml +++ b/deployment/docker/docker-compose.yml @@ -4,7 +4,7 @@ services: # And forward them to --remoteWrite.url vmagent: container_name: vmagent - image: victoriametrics/vmagent:v1.105.0 + image: victoriametrics/vmagent:v1.106.0 depends_on: - "victoriametrics" ports: @@ -22,7 +22,7 @@ services: # storing metrics and serve read requests. victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.105.0 + image: victoriametrics/victoria-metrics:v1.106.0 ports: - 8428:8428 - 8089:8089 @@ -65,7 +65,7 @@ services: # vmalert executes alerting and recording rules vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.105.0 + image: victoriametrics/vmalert:v1.106.0 depends_on: - "victoriametrics" - "alertmanager" diff --git a/deployment/docker/victorialogs/compose-base.yml b/deployment/docker/victorialogs/compose-base.yml index 6d481ab30..27ec04a9c 100644 --- a/deployment/docker/victorialogs/compose-base.yml +++ b/deployment/docker/victorialogs/compose-base.yml @@ -18,7 +18,7 @@ services: retries: 10 dd-logs: - image: docker.io/victoriametrics/vmauth:v1.105.0 + image: docker.io/victoriametrics/vmauth:v1.106.0 restart: on-failure volumes: - ./:/etc/vmauth diff --git a/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml b/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml index 5d8189f1a..00571d8c9 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.105.0 + image: victoriametrics/vmagent:v1.106.0 depends_on: - "victoriametrics" ports: @@ -18,7 +18,7 @@ services: victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.105.0 + image: victoriametrics/victoria-metrics:v1.106.0 ports: - 8428:8428 volumes: @@ -50,7 +50,7 @@ services: vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.105.0 + image: victoriametrics/vmalert:v1.106.0 depends_on: - "victoriametrics" ports: diff --git a/deployment/logs-benchmark/docker-compose.yml b/deployment/logs-benchmark/docker-compose.yml index 4a4f49d56..bf02a3a71 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.105.0 + image: victoriametrics/victoria-metrics:v1.106.0 ports: - "8428:8428" command: diff --git a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md index fd012a386..fb47b7795 100644 --- a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md +++ b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md @@ -2,9 +2,9 @@ - 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) (v1.105.0) - - [vmalert](https://docs.victoriametrics.com/vmalert/) (v1.105.0) - - [vmagent](https://docs.victoriametrics.com/vmagent/) (v1.105.0) + - [VictoriaMetrics Single-Node](https://docs.victoriametrics.com/single-server-victoriametrics) (v1.106.0) + - [vmalert](https://docs.victoriametrics.com/vmalert/) (v1.106.0) + - [vmagent](https://docs.victoriametrics.com/vmagent/) (v1.106.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.27.0) @@ -313,7 +313,7 @@ Let's wrap it all up together into the `docker-compose.yml` file. services: vmagent: container_name: vmagent - image: victoriametrics/vmagent:v1.105.0 + image: victoriametrics/vmagent:v1.106.0 depends_on: - "victoriametrics" ports: @@ -330,7 +330,7 @@ services: victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.105.0 + image: victoriametrics/victoria-metrics:v1.106.0 ports: - 8428:8428 volumes: @@ -363,7 +363,7 @@ services: vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.105.0 + image: victoriametrics/vmalert:v1.106.0 depends_on: - "victoriametrics" ports: diff --git a/docs/enterprise.md b/docs/enterprise.md index ee9f758eb..b60849fa0 100644 --- a/docs/enterprise.md +++ b/docs/enterprise.md @@ -82,7 +82,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.105.0-enterprise.tar.gz`. +Enterprise binaries and packages have `enterprise` suffix in their names. For example, `victoria-metrics-linux-amd64-v1.106.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/): ```sh -wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.105.0/victoria-metrics-linux-amd64-v1.105.0-enterprise.tar.gz -tar -xzf victoria-metrics-linux-amd64-v1.105.0-enterprise.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.106.0/victoria-metrics-linux-amd64-v1.106.0-enterprise.tar.gz +tar -xzf victoria-metrics-linux-amd64-v1.106.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.105.0-enterprise`. +Enterprise docker images have `enterprise` suffix in their names. For example, `victoriametrics/victoria-metrics:v1.106.0-enterprise`. 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: ```sh -docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.105.0-enterprise -license=BASE64_ENCODED_LICENSE_KEY +docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.106.0-enterprise -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.105.0-enterprise -licenseFile=/path/to/vm-license +docker run --name=victoria-metrics -v /vm-license:/vm-license victoriametrics/victoria-metrics:v1.106.0-enterprise -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.105.0 + image: victoriametrics/victoria-metrics:v1.106.0 ports: - 8428:8428 volumes: @@ -173,7 +173,7 @@ is used to provide key in plain-text: ```yaml server: image: - tag: v1.105.0-enterprise + tag: v1.106.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.105.0-enterprise + tag: v1.106.0-enterprise license: secret: @@ -233,7 +233,7 @@ spec: license: key: {BASE64_ENCODED_LICENSE_KEY} image: - tag: v1.105.0-enterprise + tag: v1.106.0-enterprise ``` In order to provide key via existing secret, the following custom resource is used: @@ -250,7 +250,7 @@ spec: name: vm-license key: license image: - tag: v1.105.0-enterprise + tag: v1.106.0-enterprise ``` Example secret with license key: diff --git a/docs/guides/grafana-vmgateway-openid-configuration/README.md b/docs/guides/grafana-vmgateway-openid-configuration/README.md index 063d9b701..fed8e844c 100644 --- a/docs/guides/grafana-vmgateway-openid-configuration/README.md +++ b/docs/guides/grafana-vmgateway-openid-configuration/README.md @@ -236,27 +236,27 @@ services: - grafana_data:/var/lib/grafana/ vmsingle: - image: victoriametrics/victoria-metrics:v1.105.0 + image: victoriametrics/victoria-metrics:v1.106.0 command: - -httpListenAddr=0.0.0.0:8429 vmstorage: - image: victoriametrics/vmstorage:v1.105.0-cluster + image: victoriametrics/vmstorage:v1.106.0-cluster vminsert: - image: victoriametrics/vminsert:v1.105.0-cluster + image: victoriametrics/vminsert:v1.106.0-cluster command: - -storageNode=vmstorage:8400 - -httpListenAddr=0.0.0.0:8480 vmselect: - image: victoriametrics/vmselect:v1.105.0-cluster + image: victoriametrics/vmselect:v1.106.0-cluster command: - -storageNode=vmstorage:8401 - -httpListenAddr=0.0.0.0:8481 vmagent: - image: victoriametrics/vmagent:v1.105.0 + image: victoriametrics/vmagent:v1.106.0 volumes: - ./scrape.yaml:/etc/vmagent/config.yaml command: @@ -265,7 +265,7 @@ services: - -remoteWrite.url=http://vmsingle:8429/api/v1/write vmgateway-cluster: - image: victoriametrics/vmgateway:v1.105.0-enterprise + image: victoriametrics/vmgateway:v1.106.0-enterprise ports: - 8431:8431 volumes: @@ -281,7 +281,7 @@ services: - -auth.oidcDiscoveryEndpoints=http://keycloak:8080/realms/master/.well-known/openid-configuration vmgateway-single: - image: victoriametrics/vmgateway:v1.105.0-enterprise + image: victoriametrics/vmgateway:v1.106.0-enterprise ports: - 8432:8431 volumes: @@ -393,7 +393,7 @@ Once iDP configuration is done, vmagent configuration needs to be updated to use ```yaml vmagent: - image: victoriametrics/vmagent:v1.105.0 + image: victoriametrics/vmagent:v1.106.0 volumes: - ./scrape.yaml:/etc/vmagent/config.yaml - ./vmagent-client-secret:/etc/vmagent/oauth2-client-secret diff --git a/docs/scrape_config_examples.md b/docs/scrape_config_examples.md index c198760f2..be2bad2f1 100644 --- a/docs/scrape_config_examples.md +++ b/docs/scrape_config_examples.md @@ -30,8 +30,8 @@ scrape_configs: After you created the `scrape.yaml` file, download and unpack [single-node VictoriaMetrics](https://docs.victoriametrics.com/) to the same directory: ``` -wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.105.0/victoria-metrics-linux-amd64-v1.105.0.tar.gz -tar xzf victoria-metrics-linux-amd64-v1.105.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.106.0/victoria-metrics-linux-amd64-v1.106.0.tar.gz +tar xzf victoria-metrics-linux-amd64-v1.106.0.tar.gz ``` Then start VictoriaMetrics and instruct it to scrape targets defined in `scrape.yaml` and save scraped metrics @@ -146,8 +146,8 @@ Then start [single-node VictoriaMetrics](https://docs.victoriametrics.com/) acco ```yaml # Download and unpack single-node VictoriaMetrics -wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.105.0/victoria-metrics-linux-amd64-v1.105.0.tar.gz -tar xzf victoria-metrics-linux-amd64-v1.105.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.106.0/victoria-metrics-linux-amd64-v1.106.0.tar.gz +tar xzf victoria-metrics-linux-amd64-v1.106.0.tar.gz # Run single-node VictoriaMetrics with the given scrape.yaml ./victoria-metrics-prod -promscrape.config=scrape.yaml