Automatic update operator docs from VictoriaMetrics/operator@b3e19a2 (#7608)

Automated changes by
[create-pull-request](https://github.com/peter-evans/create-pull-request)
GitHub action

Signed-off-by: Github Actions <133988544+victoriametrics-bot@users.noreply.github.com>
Co-authored-by: f41gh7 <18450869+f41gh7@users.noreply.github.com>
This commit is contained in:
Github Actions 2024-11-21 00:48:14 -08:00 committed by GitHub
parent 689196048f
commit f07574a78e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 29 additions and 0 deletions

View file

@ -17,6 +17,8 @@ aliases:
- [vmoperator](https://docs.victoriametrics.com/operator/): bump default version of VictoriaMetrics components to [1.106.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.106.1).
- [vmoperator](https://docs.victoriametrics.com/operator/): add new variable `VM_VMSERVICESCRAPEDEFAULT_ENFORCEENDPOINTSLICES` to use `endpointslices` instead of `endpoints` as discovery role for VMServiceScrape when generate scrape config for VMAgent.
- [vmoperator](https://docs.victoriametrics.com/operator/): adds new flag `loggerJSONFields` to the operator logger configuration. It allows to change json encoder fields. See [this issue](https://github.com/VictoriaMetrics/operator/issues/1157) for details.
- [api](https://docs.victoriametrics.com/operator/api): adds new status field `observedGeneration`. See [this issue](https://github.com/VictoriaMetrics/operator/issues/1155) for details.
- [api](https://docs.victoriametrics.com/operator/api): unify `updateStatus` field for CRD objects. It replaces `status`, `clusterStatus` and `singleStatus` for `VLogs`, `VMCluster` and `VMSingle` with generic `updateStatus`.
## [v0.49.1](https://github.com/VictoriaMetrics/operator/releases/tag/v0.49.1) - 11 Nov 2024

View file

@ -1963,6 +1963,30 @@ _Appears in:_
| `urls` | URLs allows setting multiple urls for load-balancing at vmauth-side. | _string array_ | false |
#### StatusMetadata
StatusMetadata holds metadata of application update status
_Appears in:_
- [VLogsStatus](#vlogsstatus)
- [VMAgentStatus](#vmagentstatus)
- [VMAlertStatus](#vmalertstatus)
- [VMAlertmanagerStatus](#vmalertmanagerstatus)
- [VMAuthStatus](#vmauthstatus)
- [VMClusterStatus](#vmclusterstatus)
- [VMSingleStatus](#vmsinglestatus)
| Field | Description | Scheme | Required |
| --- | --- | --- | --- |
| `observedGeneration` | ObservedGeneration defines current generation picked by operator for the<br />reconcile | _integer_ | true |
| `reason` | Reason defines fail reason for reconcile process | _string_ | true |
| `updateStatus` | UpdateStatus defines a status for update rollout | _[UpdateStatus](#updatestatus)_ | true |
#### StorageSpec
@ -2368,6 +2392,8 @@ UpdateStatus defines status for application
_Appears in:_
- [StatusMetadata](#statusmetadata)
- [VLogsStatus](#vlogsstatus)
- [VMAgentStatus](#vmagentstatus)
- [VMAlertStatus](#vmalertstatus)
- [VMAlertmanagerStatus](#vmalertmanagerstatus)
@ -2407,6 +2433,7 @@ _Appears in:_
VLogs is fast, cost-effective and scalable logs database.
VLogs is the Schema for the vlogs API