-
Story
-
Resolution: Done
-
Minor
-
None
-
None
-
False
-
False
-
Undefined
-
-
CFE Sprint 210, CFE Sprint 211
Related tickets:
CFEPLAN-21
RFE-1181
previous work by luzuccar@redhat.com done in CFE-112
Contacts:
luzuccar@redhat.com & tjungblu@redhat.com
PM stakeholder: anachand
other tech contacts: David Eads, Stefan Schimanski, Maciej Szulik
Find somebody on the team that wants to tag along with you, set them as the additional assignee.
Create a new doc from the template:
https://docs.google.com/document/d/1nkhVz6zekqOJjn1JRiUe-ixpjKktG3zuZ2m5FuNFRik/template/preview
Save this in the CFE Google Drive under the "Brainstorming" folder and fill the respective sections.
You can find more information about the process in the CFE Tech Discovery Process doc.
AC:
- Fill the design document to outline caveats, findings and any other relevant info
- If feasible, provide a breakdown of tasks and high level estimates
Additional information:
Scope was clarified on a meeting on Monday and changed to:
- just ship it as an OLM and make it functionally work (Day2)
- no other integration into OpenShift necessary
- support for ROSA/AWS
Some questions we need to answer in this R&D:
- kubectl-hns plugin, could it work with oc krew plugins that's in the making for 4.11? (ie. can you install it today with Krew?)
- does the HNC work when installed on ROSA/AWS? https://github.com/kubernetes-sigs/hierarchical-namespaces
- is it feasible to ship this as an operator? how could a configuration CRD look like?
- clones
-
CFE-185 Template - R&D Spike
- To Do