extended flux runtime ui as runtime ui to also include other gitops controllers

[enekofb]

Closes #3741

What changed?

• Imported runtime from wego oss
• Duplicated runtime component in ee (as we did)
• configured runtime behaviour out of feature flag WEAVE_GITOPS_FEATURE_GITOPS_RUNTIME

Why was this change made?

• to extend current runtime experience beyond flux to includes other oss components like policy or tf-controllers

How was this change implemented?

• Duplicated api endpoints
• Duplicated ui components
• Added feature flag to control the behaviour

How did you validate the change?

• UI

We could see some WGE controllers in the UI

Release notes

• Runtime UI supports runtime WGE components. See documentation for more info https://docs.gitops.weave.works/docs/open-source/getting-started/ui-OSS/#the-flux-runtime-view

Documentation Changes

• Added via helm chart reference annotations and updated documentation

Follow up

• Complete doumentation and Add part-of weave-gitops label to all controllers during WGE release #3743

[enekofb]

opted-in for internal feedback

[enekofb]

controllers https://github.com/weaveworks/weave-gitops-enterprise/tree/main/docs/architecture#kubernetes-controllers

Flux is the core component for delivery gitops applications.

Flagger is the component within the Flux Ecosystem for providing advance deployment strategies or progressive delivery.

Terraform Controller is the controller that provides capabilities to manage terraform infrastructure within WGE.

Cluster Controller: provides the capability to integrate Kubernetes clusters for Weave GitOps Enterprise.

Cluster Bootstrap Controller: responsible for bootstrapping Kubernetes clusters joining Weave GitOps Enterprise with baseline capabilities like flux.

GitopsSet Controller: provides the capability to have a single definition for an application for multiple environments and a fleet of clusters.

Pipeline Controller: provides continuous delivery pipelines capabilities for Weave GitOps Enterprise.

Policy Agent: controller to enforces rego policies by controlling admission of violating resources.

[opudrovs]

The code LGTM, but I tried testing this branch and saw this error. I saw a similar error once while adding my suggestion for the OSS PR, but I could not reproduce it later. Can try making a clean build on a clean cluster.

[opudrovs]

Will rebuild node_modules now, maybe it will fix it.

[opudrovs]

Still see a similar error in Chrome and Firefox (to confirm it's not caching) after rebuilding:

Can try with a clean cluster.

[opudrovs]

Yeah, the same error with a fresh cluster created with the reboot script with nothing else added.

[enekofb]

Yeah, the same error with a fresh cluster created with the reboot script with nothing else added.

it should come due to https://github.com/weaveworks/weave-gitops-enterprise/compare/f31ae9c19d0f797bce754075af1a1c3d80195633..97115a319def0284b0ba3b9b6a12832a6b8cfd7b

checking and reverting that change

[enekofb]

Yeah, the same error with a fresh cluster created with the reboot script with nothing else added.

it should come due to https://github.com/weaveworks/weave-gitops-enterprise/compare/f31ae9c19d0f797bce754075af1a1c3d80195633..97115a319def0284b0ba3b9b6a12832a6b8cfd7b

checking and reverting that change

apologies @opudrovs

have pushed the changes that should address it

[opudrovs]

Great, rebulding.

[opudrovs]

Tested the UI with the flag on and off, I guess I can see two different views and labels. Not sure why there is one more controller displayed in the Runtime UI, but guess it's expected behavior.

⚠️ There is a minor issue with the UI: the Runtime menu item is not highlighted when the Runtime view is selected (unlike the Flux Runtime menu item which is highlighted as expected). I wonder if the same issue is happening in OSS.

[enekofb]

Tested the UI with the flag on and off, I guess I can see two different views and labels. Not sure why there is one more controller displayed in the Runtime UI, but guess it's expected behavior.

⚠️ There is a minor issue with the UI: the Runtime menu item is not highlighted when the Runtime view is selected (unlike the Flux Runtime menu item which is highlighted as expected). I wonder if the same issue is happening in OSS.

The new controller is the gitops enterprise app which is expected out of the labels. this ticket #3743 is the follow up to add the right labels to the controllers (which is WIP).

[enekofb]

@opudrovs any suggestion on where to look around the menu highlighting issue?

[opudrovs]

any suggestion on where to look around the menu highlighting issue?

@enekofb
I don't remember right now, need to look into it. There should be a check for the route matching somewhere (if it matches the current location, highlight it).

[enekofb]

any suggestion on where to look around the menu highlighting issue?

@enekofb I don't remember right now, need to look into it. There should be a check for the route matching somewhere (if it matches the current location, highlight it).

super, i look around!

[opudrovs]

@enekofb good luck! If this issue is happening in OSS too, I can approve the current PR and we can open a separate issue for nav item highlight.

[enekofb]

Updated to latest main oss 4f785b8

and the error also seems to be fixed

[opudrovs]

Tested it locally and can confirm, that the Runtime item is highlighted as expected:

Great job! ✨