Installing by helm-charts #
You can use one of the following official helm-charts with vmoperator
:
- victoria-metrics-operator helm-chart
- victoria-metrics-k8s-stack helm chart
(includes the
victoria-metrics-operator
helm-chart and other components for full-fledged k8s monitoring, is an alternative for kube-prometheus-stack).
For installing VictoriaMetrics operator with helm-chart follow the instructions from README of the corresponding helm-chart (this or this).
in addition, you can use quickstart guide for installing VictoriaMetrics operator with helm-chart.
Installing by Manifest #
Obtain release from releases page: https://github.com/VictoriaMetrics/operator/releases
We suggest use the latest release.
|
|
Operator use vm
namespace, but you can install it to specific namespace with command:
|
|
and apply it:
|
|
Check the status of operator
|
|
Installing by Kustomize #
You can install operator using Kustomize by pointing to the remote kustomization file.
|
|
You can change operator configuration, or use your custom namespace see kustomize-example.
Build template
|
|
Apply manifests
|
|
Check the status of operator
|
|
Installing by OLM #
Installing to K8s #
VictoriaMetrics operator OLM package is available at OperatorHub. Installation instructions are available there.
Installing to Openshift #
Create Subscription
manifest with installPlanApproval
set to Manual
to prevent unexpected upgrades.
|
|
Apply manifest
|
|
After some time operator should be up and running in vm
namespace
|
|
Run locally #
It’s possible to build and run OLM package locally on Kind K8s cluster using make deploy-kind-olm
.
Command builds operator image, bundle and index images, runs Kind with a local registry and deploys OLM package to Kind.
Installing to ARM #
There is no need in an additional configuration for ARM. Operator and VictoriaMetrics have full support for it.
Configuring #
You can read detailed instructions about operator configuring in this document.