-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
None
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
S
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Provide a way to configure an /etct/hosts files on the host that is used by CoreDNS for name resolution, so that names in that hosts file are resolved from within a pod running on MicroShift
Goals (aka. expected user outcomes)
The goal is to simplify DNS resolution. In edge deployments, access to DNS configuration is sometimes complicated. A quick and easy way would be an /etc/hosts files with addition entries. CoreDNS (used by MicroShift internally) has a "hosts plugin" which can respect/use such a hosts files.
Requirements (aka. Acceptance Criteria):
- Provide an optional config option in the MicroShift config file to point to a /etc/hosts file
- If the config option is set, configure CoreDNS to utilize that hosts file using the hosts plugin.
- A name in the hosts file must be resolved from within any pod, without any further configuration needed to the pod.
- Changes to the hosts file must be reflected immediately without any restarts
Questions to Answer (Optional):
1. do we need help/guidance from the networking team with the CoreDNS config part?
Out of Scope
n/a
Background
n/a
Customer Considerations
This is based on customer request - see linked RFE
Documentation Considerations
Needs documented in the networking secition
Interoperability Considerations
none expected - maybe networking due to coreDNS config
- is triggered by
-
RFE-7409 Add a hosts file from the RHEL to the MicroShift using the CoreDNS hosts plugin
-
- Approved
-
- links to