-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
None
-
False
-
No
-
MGDSRVS-145 - RHOSAK Enterprise Plan: RHOSAK on customer-owned OSD/ROSA/ARO
-
---
-
---
-
-
WHAT
A public kafka should be an option for private ROSAs.
WHY
<Why is this task being done?>
HOW
If the private ROSA is not configured to have a public DNS, then the DNS entries created by the control plane need to be based upon the NLB hostname, and not the ingresscontroller... name - as that will not be publicly resolvable.
Considerations with using the NLB host name:
- We're assuming the NLB is mostly stable. However we know that if it's deleted, it will come back with a different name. The control plane I believe only validates existing dns entries. It would need to update them if we want to account for this.
- we could use this approach always, rather than using the ingresscontroller hostname. This will be preferred if we switch to a strategy of using load-balancer services, or using Kubernetes Ingress backed by an ALB.
cc gryan@redhat.com keithbwall rhn-engineering-rareddy mchitimb-1
- blocks
-
MGDSTRM-10232 Add data plane support for private kafka instances
- Closed
- is cloned by
-
MGDSTRM-10397 Allow for non-cluster domain routes
- New
-
MGDSTRM-10466 Allow control plane to update Route 53 entries
- New
-
MGDSTRM-10467 Support private dns entries for private kafka
- New