Goal
Allow VMs connected through their secondary networks to be addressable by their domain names.
User Stories
- As a developer,
I want to address machines in the network using their domain names,
so I don't rely on IP addresses specific to given environment.
For example, something like ping -4 interfacename.vmname.namespace.vm.clustername.domainname should resolve to the relevant IP address.
I would not mind if ping -4 interfacename.podname.namespace.pods.clustername.domainname works, too.
- As a developer,
I want this feature to be opt-in per interface,
since not all interfaces are available from the outside, or meant to be used by clients.
Non-Requirements
- <List of things not included in this epic, to alleviate any doubt raised during the grooming process.>
Notes
Owners
| Role |
Contact |
| PM |
TBD |
| Documentation Owner |
TBD |
| Delivery Owner |
(See assignee) |
| Quality Engineer |
(See QE Assignee) |
Done Checklist
| Who |
What |
Reference |
| DEV |
Upstream roadmap issue |
<link to GitHub Issue> It is unclear whether this would be OpenShift only or not |
| DEV |
Upstream code and tests merged |
<link to meaningful PR or GitHub Issue> |
| DEV |
Upstream documentation merged |
<link to meaningful PR or GitHub Issue> |
| DEV |
gap doc updated |
<name sheet and cell> |
| DEV |
Upgrade consideration |
<link to upgrade-related test or design doc> |
| DEV |
CEE/PX summary presentation |
label epic with cee-training and add a <link to your support-facing preso> |
| QE |
Test plans in Polarion |
<link or reference to test plans> |
| QE |
Automated tests merged |
<link or reference to automated tests> |
| DOC |
Downstream documentation merged |
<link to meaningful PR> |
Epic
Undefined
