This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
Future of the Keptn Web UI #9051
oleg-nenashev
started this conversation in
General
Replies: 1 comment
-
I am all for moving towards a headless approach for a number of reasons:
I think this also offer the opportunity to develop solutions on top of Keptn components. Having said all this, we need to define a clear path for existing users, how they can keep getting the information they are getting today in headless mode. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As we discussed at the previous community meetings, there are concerns about long-term sustainability of the Keptn Bridge - a Web UI for Keptn.
In the previous conversations in the community, I believe we have a consensus that we would like to move to a headless solution with proper APIs and endpoints that would allow connecting an external interface, for example built on the top of Grafana or Backstage.
Any feedback from Keptn users and developers would be welcome!
Problems
Possible Solutions
Beta Was this translation helpful? Give feedback.
All reactions