Allow adding extra hosts in coredns (!9378) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

The aim of this MR is to allow the users to declare custom hosts into coredns configuration.

Under .Values.additional_dns_entries an end user could add custom host using following format <ip> <hosts>, both ipv4 and ipv6 are supported, but the cluster should have ipv6 integration in order to declare this type of entry.

As a testing part for this new feature I've introduce a chainsaw test called custom-dns-resolution which will test if the custom dns entries defined into values are correctly resolved.

CI deployment values MR: sylva-projects/sylva-elements/ci-tooling/ci-deployment-values!535 (merged)

Closes #2735 (closed).

Test coverage

Additional dns definition:

additional_dns_entries:
  "127.0.1.1": "sylva.example test.orange"
  "127.0.2.2": "sylva.orange"

Create a pod and check if the hostnames are properly resolved:

/ # nslookup sylva.orange
Server:         100.73.0.10
Address:        100.73.0.10:53


Name:   sylva.orange
Address: 127.0.2.2

/ # nslookup test.orange
Server:         100.73.0.10
Address:        100.73.0.10:53


Name:   test.orange
Address: 127.0.1.1

/ # nslookup rancher.sylva
Server:         100.73.0.10
Address:        100.73.0.10:53

Name:   rancher.sylva
Address: 192.168.19.234

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Oct 13, 2026 by Bogdan Antohe

Allow adding extra hosts in coredns

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports