This documentation does not include technical details about the operator itself. If you are interested in the operator, rather than the integration of HCC UI modules with it, please follow this link.
Please check the pre-requisites section first.
If your UI modules do not leverage the FEO integration features, please follow the migration guide.
Having the Chroming UI configuration defined in a centralized project is no longer viable solution. Though working and effective, centralized configuration is not efficient. In order to further scale the number of UI modules, the configuration of UI features has to be moved directly to the UI modules repositories.
Moving the UI module configuration directly to the source repositories, will enable individual teams to control and maintain relevant configuration, enabling self servicing the changes.
It will also offload significant work from the platform team and thus decreasing the deployment time of Chrome UI configuration changes.
The frontend operator provides the exact tooling necessary to decentralized the configuration and generate necessary data for the Chrome UI to operate in normal manner.
Each frontend module must have a k8s template that defines the Frontend resource. The Frontend resource is used by the operator to not only create deployments but also collect important data that are used to construct the HCC frontend and enhance the user experience.
The Frontend resource is by default located in the deploy/frontend.yaml file.
If your IDE supports validating yaml files from a json schema, you can reference it on this link:
https://raw.githubusercontent.com/RedHatInsights/frontend-components/refs/heads/master/packages/config-utils/src/feo/spec/frontend-crd.schema.jsonFor VSCode, you can add a following line to the top of the yaml
# yaml-language-server: $schema=https://raw.githubusercontent.com/RedHatInsights/frontend-components/refs/heads/master/packages/config-utils/src/feo/spec/frontend-crd.schema.json