VictoriaMetrics / VictoriaMetrics/operator
BUG: extraEnvsFrom: does not create environment variables as expected in vmanomaly
Open
@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
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.
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"
also the api doc for extraEnvs and extraEnvsFrom the doc link is broken.
also this fails silently.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.