DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
What happened?
I have been successfully using kaniko to build images in k8s cluster. To improve performance, I see several options on kaniko to pre-warm the build cache of base images, separate mount directory for temporary files etc. However, there doesn't seem to be a way to configure these in devsoace kaniko build configuration.
I haven't used buildkit yet, but looking at documentation, I don't see how to mount volumes with buildkit either.
What did you expect to happen instead?
Some way to mount additional volumes in the build image for kaniko and buildkit.
How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
version: ...
...
Local Environment:
DevSpace Version: [use devspace --version]
Operating System: windows | linux | mac
ARCH of the OS: AMD64 | ARM64 | i386
Kubernetes Cluster:
Thanks for the report. This is more of a feature request than a bug as it would require a new configuration option. Would you be willing to submit a PR?
What happened?
I have been successfully using kaniko to build images in k8s cluster. To improve performance, I see several options on kaniko to pre-warm the build cache of base images, separate mount directory for temporary files etc. However, there doesn't seem to be a way to configure these in devsoace kaniko build configuration.
I haven't used buildkit yet, but looking at documentation, I don't see how to mount volumes with buildkit either.
What did you expect to happen instead?
Some way to mount additional volumes in the build image for kaniko and buildkit.
How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
Local Environment:
devspace --version
]kubectl version
]Anything else we need to know?