# What this PR does Add option to add additional pod labels. ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [ ] Documentation added (or `pr:no public docs` PR label added if not required) - [ ] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not required) - [x] It is manually tested in the internal environment --------- Co-authored-by: Marius Ensrud <marius.ensrud@skatteetaten.no> Co-authored-by: Joey Orlando <joey.orlando@grafana.com> Co-authored-by: Joey Orlando <joseph.t.orlando@gmail.com> Co-authored-by: Ildar Iskhakov <Ildar.iskhakov@grafana.com>
32 lines
754 B
YAML
32 lines
754 B
YAML
suite: test podlabels for deployments
|
|
templates:
|
|
- celery/deployment.yaml
|
|
- engine/deployment.yaml
|
|
- telegram-polling/deployment.yaml
|
|
release:
|
|
name: oncall
|
|
tests:
|
|
- it: podLabels={} -> should exclude podLabels
|
|
set:
|
|
telegramPolling:
|
|
enabled: true
|
|
asserts:
|
|
- notExists:
|
|
path: spec.template.metadata.labels.some-key
|
|
|
|
- it: podLabels -> should use custom podLabels
|
|
set:
|
|
engine:
|
|
podLabels:
|
|
some-key: some-value
|
|
celery:
|
|
podLabels:
|
|
some-key: some-value
|
|
telegramPolling:
|
|
enabled: true
|
|
podLabels:
|
|
some-key: some-value
|
|
asserts:
|
|
- equal:
|
|
path: spec.template.metadata.labels.some-key
|
|
value: some-value
|