Hacker News Reader

maybe I'm misunderstanding the concept here - aren't all the dependencies and conflicts taken care at during the docker image creation phase?

Or are you talking about running dependent sidecars or something like that?

View on HN

We are taking care of dependencies of other cloud native packages. For example the new Kubernetes dashboards has a dependency on cert-manager to generate certificates, or apps that have dependencies on databases or requirements for logging, monitoring or backups. All these dependencies point other cloud native packages that shouldn't / can't be installed in the same docker image.

right - in my experience that's probably the most insignificant thing to workout, but I guess if there's demand for it good luck.

Thanks!

Reply on news.ycombinator.com