Loading...

XML

Word

Printable

Type: Story
Resolution: Unresolved
Priority: Major
Fix Version/s: rhos-18.0.4 (Feature Release 1)
Affects Version/s: None
Component/s: designate-operator
Labels:
None

Story Points:
8
Epic Link:
Exposing designate DNS services
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Dev Approval:
?
Docs Approval:
?
Feature Link:
OSPRH-4410 - Designate support for RHOSO (Target 18.0 FR1)
PM Approval:
?
QE Approval:
?
Intelligence Requested:
Market:

Severity:
Important

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

The unbound resolver in the podified control plane must be accessible to VMs in the openstack cloud

blocks

OSPRH-8127 Document how the services are exposed

Backlog

is blocked by

OSPRH-8125 What to do about making the unbound resolver accessible?

Backlog

is depended on by

OSPRH-4129 Configure access control CIDRs

Refinement

Assignee:: Gregory Thiemonge

Reporter:: Brent Eagles

Team:: rhos-dfg-networking-squad-vans

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2024/06/29 6:21 PM

Updated:: 2024/07/02 12:48 PM