Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Done
Priority: Undefined
Fix Version/s: kasFleetShard-0.33.0
Affects Version/s: None
Component/s: None
Labels:
None

Epic Link:
Networking for RHOSAK Enterprise
Blocked:
False
Blocked Reason:
None
Ready:
False
Discussed with Team:
No
Feature Link:
MGDSRVS-145 - RHOSAK Enterprise Plan: RHOSAK on customer-owned OSD/ROSA/ARO
Git Pull Request:
https://github.com/bf2fc6cc711aee1a0c2a/kas-fleetshard/pull/840
[QE] How to address?:
---
[QE] Why QE missed?:
---
Intelligence Requested:
Market:

Sprint:
MK - Sprint 230, MK - Sprint 231, MK - Sprint 232

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

We need a mechanism to differentiate private kafka clusters.

This can be configured:

on the ManagedKafkaAgent - initially required because of the use of shared IngressControllers.
on the ManagedKafka - such that we plan on eventually making the access highly configurable down to an individual instance - even potentially allowing the exposure of both public and private endpoints

blocks

MGDSTRM-10286 Capture whether customer wants public or private kafka instances

Closed

is blocked by

MGDSTRM-10301 Support public kafkas on private ROSAs

In Progress

is related to

MGDSTRM-9652 Make deployment of Kafka LB/Ingress optional

To Do

Assignee:: Steven Hawkins

Reporter:: Steven Hawkins

Team:: Kafka Fleet Services

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2022/12/05 3:50 PM

Updated:: 2023/02/15 9:53 AM

Resolved:: 2023/02/15 9:53 AM