Automatic update operator docs from VictoriaMetrics/operator@26d1b3b (#5130)

docs/operator/CHANGELOG.md

@@ -2,6 +2,11 @@
 sort: 10
 weight: 10
 title: CHANGELOG
+menu:
+  docs:
+    parent: "operator"
+    weight: 10
+    identifier: "operator-changelog"
 ---
 
 # CHANGELOG

docs/operator/FAQ.md

@@ -2,6 +2,11 @@
 sort: 9
 weight: 9
 title: FAQ
+menu:
+  docs:
+    parent: "operator"
+    weight: 9
+    identifier: "operator-faq"
 ---
 
 # FAQ (Frequency Asked Questions)

docs/operator/README.md

@@ -2,6 +2,10 @@
 sort: 0
 weight: 0
 title: VictoriaMetrics Operator
+menu:
+  docs:
+    parent: "operator"
+    weight: 0
 ---
 
 # VictoriaMetrics Operator

docs/operator/api.md

@@ -2,6 +2,10 @@
 sort: 12
 weight: 12
 title: API Docs
+menu:
+  docs:
+    parent: "operator"
+    weight: 12
 ---
 
 <!-- this doc autogenerated - don't edit it manually -->

docs/operator/auth.md

@@ -2,6 +2,10 @@
 sort: 7
 weight: 7
 title: Authorization and exposing components
+menu:
+  docs:
+    parent: "operator"
+    weight: 7
 ---
 
 # Authorization and exposing components

docs/operator/configuration.md

@@ -2,6 +2,10 @@
 sort: 4
 weight: 4
 title: Configuration
+menu:
+  docs:
+    parent: "operator"
+    weight: 4
 ---
 
 # Configuration

docs/operator/enterprise.md

@@ -2,6 +2,10 @@
 sort: 13
 weight: 13
 title: Enterprise features
+menu:
+  docs:
+    parent: "operator"
+    weight: 13
 ---
 
 # Using operator with enterprise features 

docs/operator/high-availability.md

@@ -2,6 +2,10 @@
 sort: 8
 weight: 8
 title: High Availability
+menu:
+  docs:
+    parent: "operator"
+    weight: 8
 ---
 
 # High Availability

docs/operator/migration.md

@@ -2,6 +2,10 @@
 sort: 5
 weight: 5
 title: Migration from Prometheus
+menu:
+  docs:
+    parent: "operator"
+    weight: 5
 ---
 
 # Migration from prometheus-operator

docs/operator/monitoring.md

@@ -2,6 +2,10 @@
 sort: 6
 weight: 6
 title: Monitoring
+menu:
+  docs:
+    parent: "operator"
+    weight: 6
 ---
 
 # Monitoring of VictoriaMetrics Operator
@@ -14,7 +18,7 @@ These metrics can be scraped via [vmagent](./resources/vmagent.md) or Prometheus
 
 Official Grafana dashboard available for [vmoperator](https://grafana.com/grafana/dashboards/17869-victoriametrics-operator/).
 
-<img src="monitoring_operator-dashboard.jpeg" width=1200>
+<img src="monitoring_operator-dashboard.png" width=1200>
 
 Graphs on the dashboards contain useful hints - hover the `i` icon in the top left corner of each graph to read it.
 

docs/operator/quick-start.md

@@ -2,6 +2,10 @@
 sort: 1
 weight: 1
 title: QuickStart
+menu:
+  docs:
+    parent: "operator"
+    weight: 1
 ---
 
 # VictoriaMetrics Operator QuickStart

docs/operator/resources/README.md

@@ -2,6 +2,11 @@
 sort: 14
 weight: 14
 title: Custom resources
+menu:
+  docs:
+    identifier: operator-custom-resources
+    parent: "operator"
+    weight: 14
 ---
 
 #  Custom resource kinds

docs/operator/resources/vmagent.md

@@ -1,3 +1,13 @@
+---
+sort: 1
+weight: 1
+title: VMAgent
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 1
+---
+
 # VMAgent
 
 `VMAgent` represents agent, which helps you collect metrics from various sources and stores them in VictoriaMetrics.

docs/operator/resources/vmalert.md

@@ -1,3 +1,13 @@
+---
+sort: 2
+weight: 2
+title: VMAlert
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 2
+---
+
 # VMAlert
 
 `VMAlert` - executes a list of given [alerting](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) 

docs/operator/resources/vmalertmanager.md

@@ -1,3 +1,13 @@
+---
+sort: 3
+weight: 3
+title: VMAlertmanager
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 3
+---
+
 # VMAlertmanager
 
 `VMAlertmanager` - represents [alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) configuration.

docs/operator/resources/vmalertmanagerconfig.md

@@ -1,3 +1,13 @@
+---
+sort: 4
+weight: 4
+title: VMAlertmanagerConfig
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 4
+---
+
 # VMAlertmanagerConfig
 
 The `VMAlertmanagerConfig` provides way to configure [VMAlertmanager](./vmalertmanager.md) 

docs/operator/resources/vmauth.md

@@ -1,3 +1,13 @@
+---
+sort: 5
+weight: 5
+title: VMAuth
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 5
+---
+
 # VMAuth
 
 The `VMAuth` CRD provides mechanism for exposing application with authorization to outside world or to other applications inside kubernetes cluster.

docs/operator/resources/vmcluster.md

@@ -1,3 +1,13 @@
+---
+sort: 6
+weight: 6
+title: VMCluster
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 6
+---
+
 # VMCluster
 
 `VMCluster` represents a high-available and fault-tolerant version of VictoriaMetrics database.

docs/operator/resources/vmnodescrape.md

@@ -1,3 +1,13 @@
+---
+sort: 7
+weight: 7
+title: VMNodeScrape
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 7
+---
+
 # VMNodeScrape
 
 The `VMNodeScrape` CRD provides discovery mechanism for scraping metrics kubernetes nodes,

docs/operator/resources/vmpodscrape.md

@@ -1,3 +1,13 @@
+---
+sort: 8
+weight: 8
+title: VMPodScrape
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 8
+---
+
 # VMPodScrape
 
 The `VMPodScrape` CRD allows to declaratively define how a dynamic set of pods should be monitored.

docs/operator/resources/vmprobe.md

@@ -1,3 +1,13 @@
+---
+sort: 9
+weight: 9
+title: VMProbe
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 9
+---
+
 # VMProbe
 
 The `VMProbe` CRD provides probing target ability with some external prober. 

docs/operator/resources/vmrule.md

@@ -1,3 +1,13 @@
+---
+sort: 10
+weight: 10
+title: VMRule
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 10
+---
+
 # VMRule
 
 `VMRule` represents [alerting](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/)

docs/operator/resources/vmservicescrape.md

@@ -1,3 +1,13 @@
+---
+sort: 11
+weight: 11
+title: VMServiceScrape
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 11
+---
+
 # VMServiceScrape
 
 The `VMServiceScrape` CRD allows to define a dynamic set of services for monitoring. Services

docs/operator/resources/vmsingle.md

@@ -1,3 +1,13 @@
+---
+sort: 12
+weight: 12
+title: VMSingle
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 12
+---
+
 # VMSingle
 
 `VMSingle` represents database for storing metrics.

docs/operator/resources/vmstaticscrape.md

@@ -1,3 +1,13 @@
+---
+sort: 13
+weight: 13
+title: VMStaticScrape
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 13
+---
+
 # VMStaticScrape
 
 The `VMStaticScrape` CRD provides mechanism for scraping metrics from static targets, configured by CRD targets.

docs/operator/resources/vmuser.md

@@ -1,3 +1,13 @@
+---
+sort: 14
+weight: 14
+title: VMUser
+menu:
+  docs:
+    parent: "operator-custom-resources"
+    weight: 14
+---
+
 # VMUser
 
 The `VMUser` CRD describes user configuration, its authentication methods `basic auth` or `Authorization` header. 

docs/operator/security.md

@@ -2,6 +2,10 @@
 sort: 3
 weight: 3
 title: Security
+menu:
+  docs:
+    parent: "operator"
+    weight: 3
 ---
 
 # Security

docs/operator/setup.md

@@ -2,6 +2,10 @@
 sort: 2
 weight: 2
 title: Setup
+menu:
+  docs:
+    parent: "operator"
+    weight: 2
 ---
 
 # VictoriaMetrics Operator Setup

docs/operator/vars.md

@@ -2,11 +2,15 @@
 sort: 11
 weight: 11
 title: Variables
+menu:
+  docs:
+    parent: "operator"
+    weight: 11
 ---
 
 <!-- this doc autogenerated - don't edit it manually -->
 # Auto Generated vars for package config 
- updated at Wed Oct  4 16:46:39 UTC 2023 
+ updated at Thu Oct  5 10:42:38 UTC 2023 
 
 
 | varible name | variable default value | variable required | variable description |