Skip to content

vmanomaly: pass previously skipped extraEnvsFrom #2573

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AndrewChubatiuk merged 1 commit into from
Sep 4, 2026
Merged

vmanomaly: pass previously skipped extraEnvsFrom #2573

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,7 @@ aliases:
* BUGFIX: [vmcluster](https://docs.victoriametrics.com/operator/resources/vmcluster/), [vmalertmanager](https://docs.victoriametrics.com/operator/resources/vmalertmanager/): reject `spec.serviceSpec.type` overrides on `vmselect`, `vmstorage`, and `vmalertmanager` when `useAsDefault` is set, since their default `Service` must stay headless for cluster-native communication. `vminsert` is unaffected, as its default `Service` isn't headless. See [#2487](https://github.com/VictoriaMetrics/operator/issues/2487).
* BUGFIX: [vmauth](https://docs.victoriametrics.com/operator/resources/vmauth/): allow `spec.unauthorizedUserAccessSpec` with only `access_log` set, without requiring `url_map`, `url_prefix`, or `targetRefs`. See [#2551](https://github.com/VictoriaMetrics/operator/issues/2551).
* BUGFIX: [vmoperator](https://docs.victoriametrics.com/operator/): a `VolumeClaimTemplate` size decrease, which Kubernetes cannot apply in-place to a bound `PersistentVolumeClaim`, was only logged and otherwise reported as a fully successful, `operational` reconcile. It now surfaces as a failed reconcile with the decline reason in `status.reason`, so the divergence between spec and actual PVC size is queryable and can be alerted on. See [#2512](https://github.com/VictoriaMetrics/operator/issues/2512).
* BUGFIX: [vmanomaly](https://docs.victoriametrics.com/operator/resources/vmanomaly/): pass previously skipped spec.extraEnvsFrom to anomaly pods. See [#2567](https://github.com/VictoriaMetrics/operator/issues/2567).

## [v0.74.1](https://github.com/VictoriaMetrics/operator/releases/tag/v0.74.1)
**Release date:** 04 Aug 2026
Expand Down
1 change: 1 addition & 0 deletions internal/controller/operator/factory/vmanomaly/pod.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -175,6 +175,7 @@ func newPodSpec(cr *vmv1.VMAnomaly, ac *build.AssetsCache) (*corev1.PodSpec, err
VolumeMounts: volumeMounts,
Resources: cr.Spec.Resources,
Env: envs,
EnvFrom: cr.Spec.ExtraEnvsFrom,
TerminationMessagePolicy: corev1.TerminationMessageFallbackToLogsOnError,
}
build.Probe(&container, cr, &cr.Spec.CommonAppsParams)
Expand Down