Files
cozystack/packages/system/external-dns/values.yaml
T
Matthieu 7f72e7bbe8 [external-dns] Set resources requests/limits on external-dns container
The upstream external-dns chart ships with resources: {}, which triggers
a 'no CPU limit' conformance warning on the external-dns Deployment.
Override the package values.yaml to set limits 100m/128Mi and requests
10m/64Mi — modest sizing for a controller that just watches Service /
Ingress objects and pushes DNS records to the provider.

Signed-off-by: Matthieu <matthieu@hidora.com>
2026-07-03 19:14:15 +03:00

32 lines
1.1 KiB
YAML

external-dns:
# -- How DNS records are synchronized between sources and providers; available values are `sync` & `upsert-only`.
policy: upsert-only
# -- Specify the registry for storing ownership and labels.
# Valid values are `txt`, `aws-sd`, `dynamodb` & `noop`.
registry: txt
# -- (string) Specify an identifier for this instance of _ExternalDNS_ wWhen using a registry other than `noop`.
txtOwnerId:
# -- (string) Specify a prefix for the domain names of TXT records created for the `txt` registry.
# Mutually exclusive with `txtSuffix`.
txtPrefix:
# -- (string) Specify a suffix for the domain names of TXT records created for the `txt` registry.
# Mutually exclusive with `txtPrefix`.
txtSuffix:
## - Limit possible target zones by domain suffixes.
domainFilters: []
## -- Intentionally exclude domains from being managed.
excludeDomains: []
# -- Specify the DNS provider (e.g., "aws", "google", "azure", etc.)
provider:
name: ""
resources:
limits:
cpu: 100m
memory: 128Mi
requests:
cpu: 10m
memory: 64Mi