Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • thank you very much for the answer. However, my experience with registry and service discovery e.g. Netflix Eureka, falls short of my requirements. There are two major reasons, first, the systems you listed retain information ephemerally i.e. all information is lost following a shutdown. Secondly, asides the application metadata e.g. endpoints, it is important to have knowledge about deployment dates, test dates i.e. the information about the application's lifecycle. Therefore, I was hoping for a solution that aggregates all these disjointed pieces of information. Commented Aug 22, 2019 at 7:42
  • 1
    Maybe Helm could fill the role of providing the deployment dates and other lifecycle things? Commented Aug 22, 2019 at 14:43
  • @theOther can you briefly explain? I am not conversant with helm, a quick look at the documentation (helm.sh/docs/using_helm/#quickstart) gives me no clues. Commented Aug 22, 2019 at 16:55