VictoriaMetrics / VictoriaMetrics/operator

BUG: extraEnvsFrom: does not create environment variables as expected in vmanomaly

Open
#2,567 2 comments 0 reactions 1 assignee View on GitHub

@AndrewChubatiuk is already working on this.

Since Sep 4, 2026.

bug waiting for release
Dominant language
Go
Stars
589
Forks
229
Avg merge
1d 9h
Merged PRs (30d)
77

Description

Found in operator 0.73.1

extraEnvs:
    - name: TEST
      value: FLUBBER
  #extraEnvsFrom:
  #  - configMapRef:
  #      name: vmanomaly-test-cm
  #  - secretRef:
  #      name: vmanomaly-test-secret

works as expected

Image
spec:
  replicaCount: 1
  shardCount: 1
  extraEnvs:
    - name: TEST
      value: FLUBBER
  extraEnvsFrom:
    - configMapRef:
        name: vmanomaly-test-cm
    - secretRef:
        name: vmanomaly-test-secret

results in no envs from the secret or configmap, however they do show up in the config.

Image

Contests of configmap and secret

brentteal@Brents-MBP tm % cat test-cm.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: vmanomaly-test-cm
data:
  TEST_CM_VAR: "hello-from-configmap"

brentteal@Brents-MBP tm % cat test-sec.yaml
apiVersion: v1
kind: Secret
metadata:
  name: vmanomaly-test-secret
type: Opaque
stringData:
  TEST_SECRET_VAR: "hello-from-secret"

Image

also the api doc for extraEnvs and extraEnvsFrom the doc link is broken.

also this fails silently.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.