The property-based configuration approach here is way cleaner than mucking around with raw YAML. What's understated is how quarkus.kubernetes.image-pull-policy=Never combined with minikube image load eliminates the whole "where's my image" debugging cycle that kills productivity in local dev. The config map injection pattern is also solid, I've seen teams waste days fighting volume mounts when env var injection just works.
This example builds the OCI image using the OCI daemon on the host machine. Doing it in the minikube environment, using its OCI daemon, might improve the perf of the build cycle.
Yeah. But. I like to quickly spin them up locally anyway and there’s some challenges with podman. So, I don’t recommend this approach. At least on macOS.
The property-based configuration approach here is way cleaner than mucking around with raw YAML. What's understated is how quarkus.kubernetes.image-pull-policy=Never combined with minikube image load eliminates the whole "where's my image" debugging cycle that kills productivity in local dev. The config map injection pattern is also solid, I've seen teams waste days fighting volume mounts when env var injection just works.
This example builds the OCI image using the OCI daemon on the host machine. Doing it in the minikube environment, using its OCI daemon, might improve the perf of the build cycle.
Yeah. But. I like to quickly spin them up locally anyway and there’s some challenges with podman. So, I don’t recommend this approach. At least on macOS.