Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dashboard UX: custom outgoing clickeable icons (e.g. to loki, k8s ui) #3361

Open
gberche-orange opened this issue Feb 3, 2023 · 2 comments
Labels
type/enhancement New feature or request

Comments

@gberche-orange
Copy link

Problem

As a flux user
in order to further inspect K8S resources displayed in the flux dashboard
I need to be able to browse to the displayed k8s resources in 3rd party web uis such as:

  • related K8s log in grapha loki
  • related K8s resource in K8S web ui such as lens

Solution

A way to configure the dashboard deployment with a set of outgoing links for resources with:

flux-list-with-icons

The template could likely require to support conditionals (e.g. like json path / jq conditions) to allow conditional icons depending on their type: makes no sense to point logs of a K8S configmap as it generates no logs.

Additional context

@gberche-orange gberche-orange added the type/enhancement New feature or request label Feb 3, 2023
@JamWils
Copy link
Contributor

JamWils commented Feb 6, 2023

Thanks for filing this @gberche-orange. This needs a little more thought on our end. As a stop gap, you are able to add "metadata" to the top areas of these pages.

You do this by adding annotations to your Kustomization or Helm Release in the following format: metadata.weave.works/description: this is a test and you will see the metadata appear just below or above the labels section on the UI. Does that help out? You should be able to add URLs as metadata as well

https://docs.gitops.weave.works/docs/guides/displaying-custom-metadata/

@gberche-orange
Copy link
Author

Thanks @JamWils for considering this enhancement suggestion and for pointing me to the custom annotation that I had missed. While a requiring a bit manual work on each Kustomization/HelmRelease CR, I believe this could suit the purpose. I'll try it and see if I can manage to combine it with variable substitution as to avoir hard coding base Urls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants