Loading...

XML

Word

Printable

Type: Spike
Resolution: Done
Priority: Normal
Fix Version/s: rhos-18.0 Feature Release 2 (Mar 2025)
Affects Version/s: None
Component/s: designate-operator
Labels:
None

Story Points:
3
Epic Link:
Designate bind pools
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Dev Approval:
?
Docs Approval:
?
Feature Link:
OSPRH-4410 - Designate support for RHOSO Greenfield Deployment (Target 18.0 FR3)
PM Approval:
?
QE Approval:
?
Git Pull Request:
https://github.com/openstack-k8s-operators/designate-operator/pull/230
Intelligence Requested:
Market:

Sprint:
VANS-005
Planning Target:

2024Q1

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

The pools.yaml file is populated using address details from currently deployed pods and admnistrator provided information. The standard templating mechanism we have been using for configuration is inappropriate, so we need to identify the best way to do this in go

is depended on by

OSPRH-416 Populating bind pool from generated pools.yaml

Review

is related to

OSPRH-10383 Generate predictable IPs for bind stateful set

Closed

OSPRH-3523 Add field to supply ns_records in pools.yaml

Closed

OSPRH-8134 Implement predictable IP generation for miniDNS service

Closed

Assignee:: Omer Schwartz

Reporter:: Brent Eagles

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

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024/01/16 11:40 AM

Updated:: 2024/10/10 9:48 AM

Resolved:: 2024/10/10 9:48 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates

PagerDuty