Dynamically unifying disparate user interface applications in a cloud native environment
Methods, apparatus, and processor-readable storage media for dynamically unifying disparate UI applications in a cloud native environment are provided herein. An example computer-implemented method includes obtaining information pertaining to a container-orchestration system operating within at least one cloud native environment; configuring, based on the obtained information, a single sign-on authentication mechanism for multiple user interface applications in the container-orchestration system; configuring, based on the obtained information, at least one ingress route for two or more of the multiple user interface applications in the container-orchestration system; configuring and rendering, based on information pertaining to the at least one ingress route, a common header in at least each of the two or more user interface applications; and performing one or more automated actions based on the configured single sign-on authentication mechanism, the at least one configured ingress route, and the configured and rendered common header.
1. A computer-implemented method comprising:
obtaining information pertaining to a container-orchestration system operating within at least one cloud native environment;
configuring, based at least in part on the obtained information, a single sign-on authentication mechanism for multiple user interface applications in the container-orchestration system;
configuring, based at least in part on the obtained information, at least one ingress route for two or more of the multiple user interface applications in the container-orchestration system, wherein configuring at least one ingress route comprises automatically defining one or more reverse proxy rules and one or more transport layer security techniques for encrypting traffic for the at least one ingress route in the container-orchestration system;
configuring and rendering, based at least in part on information pertaining to the at least one ingress route, a common header in each of the two or more user interface applications, wherein configuring the common header is based at least in part on metadata pertaining to the at least one ingress route derived from at least one container-orchestration system configuration map, and wherein configuring the common header comprises reading at least a portion of the metadata pertaining to the at least one ingress route derived from the at least one container-orchestration system configuration map; returning a navigation map, at page load time, to one or more code segments in a programming language, the one or more code segments included in each of the two or more user interface applications; and replacing at least one hypertext markup language placeholder in the one or more code segments; and
performing one or more automated actions based at least in part on the configured single sign-on authentication mechanism, the at least one configured ingress route, and the configured and rendered common header;
wherein the method is performed by at least one processing device comprising a processor coupled to a memory.
2. The computer-implemented method of claim 1 , wherein performing the one or more automated actions comprises transforming at least the two or more user interface applications into a unified user interface framework.
3. The computer-implemented method of claim 1 , wherein configuring the single sign-on authentication mechanism comprises determining one or more single sign-on authentication mechanism parameters by parsing at least a portion of the obtained information pertaining to the container-orchestration system.
4. The computer-implemented method of claim 1 , wherein configuring the common header comprises configuring one or more navigation uniform resource locators for the common header.
5. The computer-implemented method of claim 1 , wherein obtaining the information pertaining to the container-orchestration system comprises processing at least one notification from the container-orchestration system when a custom resource definition is at least one of created, updated, and deleted.
6. The computer-implemented method of claim 1 , wherein performing the one or more automated actions comprises implementing a single-page application as a front-end user interface application, and generating, using the single-page application, at least one navigation of routes across at least the two or more user interface applications.
7. A non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device causes the at least one processing device:
to obtain information pertaining to a container-orchestration system operating within at least one cloud native environment;
to configure, based at least in part on the obtained information, a single sign-on authentication mechanism for multiple user interface applications in the container-orchestration system;
to configure, based at least in part on the obtained information, at least one ingress route for two or more of the multiple user interface applications in the container-orchestration system, wherein configuring at least one ingress route comprises automatically defining one or more reverse proxy rules and one or more transport layer security techniques for encrypting traffic for the at least one ingress route in the container-orchestration system;
to configure and render, based at least in part on information pertaining to the at least one ingress route, a common header in each of the two or more user interface applications, wherein configuring the common header is based at least in part on metadata pertaining to the at least one ingress route derived from at least one container-orchestration system configuration map, and wherein configuring the common header comprises reading at least a portion of the metadata pertaining to the at least one ingress route derived from the at least one container-orchestration system configuration map; returning a navigation map, at page load time, to one or more code segments in a programming language, the one or more code segments included in each of the two or more user interface applications; and replacing at least one hypertext markup language placeholder in the one or more code segments; and
to perform one or more automated actions based at least in part on the configured single sign-on authentication mechanism, the at least one configured ingress route, and the configured and rendered common header.
8. The non-transitory processor-readable storage medium of claim 7 , wherein performing the one or more automated actions comprises transforming at least the two or more user interface applications into a unified user interface framework.
9. The non-transitory processor-readable storage medium of claim 7 , wherein configuring the single sign-on authentication mechanism comprises determining one or more single sign-on authentication mechanism parameters by parsing at least a portion of the obtained information pertaining to the container-orchestration system.
10. The non-transitory processor-readable storage medium of claim 7 , wherein configuring the common header comprises configuring one or more navigation uniform resource locators for the common header.
11. The non-transitory processor-readable storage medium of claim 7 , wherein performing the one or more automated actions comprises implementing a single-page application as a front-end user interface application, and generating, using the single-page application, at least one navigation of routes across at least the two or more user interface applications.
12. The non-transitory processor-readable storage medium of claim 7 , wherein obtaining the information pertaining to the container-orchestration system comprises processing at least one notification from the container-orchestration system when a custom resource definition is created.
13. The non-transitory processor-readable storage medium of claim 7 , wherein obtaining the information pertaining to the container-orchestration system comprises processing at least one notification from the container-orchestration system when a custom resource definition is updated.
14. The non-transitory processor-readable storage medium of claim 7 , wherein obtaining the information pertaining to the container-orchestration system comprises processing at least one notification from the container-orchestration system when a custom resource definition is deleted.
15. An apparatus comprising:
at least one processing device comprising a processor coupled to a memory;
the at least one processing device being configured:
to obtain information pertaining to a container-orchestration system operating within at least one cloud native environment;
to configure, based at least in part on the obtained information, a single sign-on authentication mechanism for multiple user interface applications in the container-orchestration system;
to configure, based at least in part on the obtained information, at least one ingress route for two or more of the multiple user interface applications in the container-orchestration system, wherein configuring at least one ingress route comprises automatically defining one or more reverse proxy rules and one or more transport layer security techniques for encrypting traffic for the at least one ingress route in the container-orchestration system;
to configure and render, based at least in part on information pertaining to the at least one ingress route, a common header in each of the two or more user interface applications, wherein configuring the common header is based at least in part on metadata pertaining to the at least one ingress route derived from at least one container-orchestration system configuration map, and wherein configuring the common header comprises reading at least a portion of the metadata pertaining to the at least one ingress route derived from the at least one container-orchestration system configuration map; returning a navigation map, at page load time, to one or more code segments in a programming language, the one or more code segments included in each of the two or more user interface applications; and replacing at least one hypertext markup language placeholder in the one or more code segments; and
to perform one or more automated actions based at least in part on the configured single sign-on authentication mechanism, the at least one configured ingress route, and the configured and rendered common header.
16. The apparatus of claim 15 , wherein performing the one or more automated actions comprises transforming at least the two or more user interface applications into a unified user interface framework.
17. The apparatus of claim 15 , wherein configuring the single sign-on authentication mechanism comprises determining one or more single sign-on authentication mechanism parameters by parsing at least a portion of the obtained information pertaining to the container-orchestration system.
18. The apparatus of claim 15 , wherein configuring the common header comprises configuring one or more navigation uniform resource locators for the common header.
19. The apparatus of claim 15 , wherein obtaining the information pertaining to the container-orchestration system comprises processing at least one notification from the container-orchestration system when a custom resource definition is at least one of created, updated, and deleted.
20. The apparatus of claim 15 , wherein performing the one or more automated actions comprises implementing a single-page application as a front-end user interface application, and generating, using the single-page application, at least one navigation of routes across at least the two or more user interface applications.