sort | weight | title | menu | aliases | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
9 |
9 |
FAQ |
|
|
You can read about vmoperator monitoring in this document.
With Helm chart deployment:
- Update the PVCs manually
- Run
kubectl delete statefulset --cascade=orphan {vmstorage-sts}
which will delete the sts but keep the pods - Update helm chart with the new storage class in the volumeClaimTemplate
- Run the helm chart to recreate the sts with the updated value
With Operator deployment:
- Update the PVCs manually
- Run
kubectl delete vmcluster --cascade=orphan {cluster-name}
- Run
kubectl delete statefulset --cascade=orphan {vmstorage-sts}
- Update VMCluster spec to use new storage class
- Apply cluster configuration
You can use VM_CONTAINERREGISTRY
parameter for operator:
- See details about tuning operator settings here.
- See available operator settings here.
You can read about backups:
- for
VMSingle
: Backup automation - for
VMCluster
: Backup automation
You can read about migration from prometheus operator on this page.
You can read about it on this page.
You can read about it in following sections of "Migration from prometheus-operator" docs:
You can read about needed permissions for operator in this document.
See printDefaults mode.
In addition, you can use Release notes or CHANGELOG.
- that's where we describe default version of VictoriaMetrics components.
See this document for details: Configuration -> Namespaced mode.
How to configure VMAgent and VMServiceScrape for using with Istio Service Mesh and its mTLS?
See this example in operator repository: https://github.com/VictoriaMetrics/operator/blob/master/config/examples/vmagent-istio.yaml
Operator tested at kubernetes versions from 1.16 to 1.27.