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

topology: read ConfigMap colcated with Kuadrant instance (currently hard-coded) #48

Closed
jasonmadigan opened this issue Sep 9, 2024 · 3 comments · Fixed by Kuadrant/kuadrant-operator#920 or #93
Assignees
Labels
bug Something isn't working

Comments

@jasonmadigan
Copy link
Member

jasonmadigan commented Sep 9, 2024

In the topology view, read the DOT from the secret ConfigMap in the same NS as the Kuadrant instance. Currently, this is hard-coded

@jasonmadigan jasonmadigan added enhancement New feature or request bug Something isn't working and removed enhancement New feature or request labels Sep 9, 2024
@jasonmadigan jasonmadigan self-assigned this Sep 11, 2024
@Boomatang
Copy link

If it can hep to get around the hardcoded namespace the configmap is labelled with kuadrant.io/topology=true

@jasonmadigan
Copy link
Member Author

thanks @Boomatang - that does help.

Thinking we'll go down a route like this:

  • Add some env-vars to our deployment with the name/ns of the CM
  • Create a custom startup script as part of our asset image that injects these env-vars into a JS file
  • Plugin reads this JS, and knows where to locate the topology CM

Follow on issue: we need to document that users need read access to this resource for the topology view to work.

@jasonmadigan
Copy link
Member Author

jasonmadigan commented Oct 8, 2024

PRs:

#93
Kuadrant/kuadrant-operator#920

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
2 participants