Open Iryna-Kaplun opened 11 months ago
Comment from Steven Barre on Sep 12, 2023 when Iryna checked with him if this epic is still relevant: Still relevant. There is some metadata in the namespace object in the Emerald / klab2 that would be nice to expose back into the Registry.
Olena said: to check with Steven and if Steven says it's still relevant, check with Ryan Loiselle
https://digital.gov.bc.ca/cloud/services/private/internal-resources/emerald/
In the section How to find the internal CIDR /26 assigned to pods for my namespace
there is a manual process to get the subnet assigned to a namespace after its created. It may be helpful if the Registry could connect to the Kube API and query this info and display it so product owners are able to easily find it without having to use the CLI.
Apps hosted in the Emerald Cluster had /24 subnet information generated for them at the time of provisioning namespaces as described in this document (IDIR protected). This information resides in Openshift as part of the namespace meta information. Product teams would like to see this information displayed on the product detail page in the Registry UI.
At this moment the information is only passed from the Registry app to the provisioner to Openshift. This feature requires building the second communication line where information can be passed from Openshift to the provisioner to the Registry app.
UPDATE: Please see a comment from Steven below.
DoD: