Since at least 5 years i have this discussion about health endpoints in every damn project. Everyone just wires the actuator/health (spring) or q/health (quarkus) endpoint to the kubernetes probes and some people are so locked in into this idea that you have to spend an hour or more going through specific scenarios to show them why it's a bad idea. So strange. Same goes for the memory topic and other topics in this presentation, i encountered so much resistance and lack of knowledge in these areas that i started to wonder if i was wrong (i guess it's called gaslighting nowadays). So thanks.
One advantage of Jib is that it does not require a Docker daemon. This is useful for situations where you can't run docker-in-docker. Is there a way to use buildpacks without a docker daemon?
Since at least 5 years i have this discussion about health endpoints in every damn project. Everyone just wires the actuator/health (spring) or q/health (quarkus) endpoint to the kubernetes probes and some people are so locked in into this idea that you have to spend an hour or more going through specific scenarios to show them why it's a bad idea. So strange.
Same goes for the memory topic and other topics in this presentation, i encountered so much resistance and lack of knowledge in these areas that i started to wonder if i was wrong (i guess it's called gaslighting nowadays). So thanks.
One advantage of Jib is that it does not require a Docker daemon. This is useful for situations where you can't run docker-in-docker.
Is there a way to use buildpacks without a docker daemon?
yes, buildpacks working without docker daemon whould be great 👍🏻
Buildpacks is the spec. Some implementations such as kpack and Tanzu Build Service don’t require a local Docker daemon.