Timeline for Microservices Deployment Manager
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2019 at 16:55 | comment | added | SyCode | @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. | |
| Aug 22, 2019 at 14:43 | comment | added | Randy L | Maybe Helm could fill the role of providing the deployment dates and other lifecycle things? | |
| Aug 22, 2019 at 7:42 | comment | added | SyCode | 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. | |
| Aug 21, 2019 at 21:53 | history | answered | 030 | CC BY-SA 4.0 |