devspace icon indicating copy to clipboard operation
devspace copied to clipboard

DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.

Results 356 devspace issues
Sort by recently updated
recently updated
newest added

**What happened?** Getting error "No space left on device" in case, when trying to sync large directories (over 700mb) from local machine to kubernetes pod. **What did you expect to...

kind/enhancement
area/sync
needs-information

**What happened?** After updating my project's dependency from 4.10.0 to 4.12.2, starting devspace sync causes an "install loop". I've tried removing the globally installed DevSpace package, removing/reinstalling my project dependencies,...

**What happened?** When running the arm64 build of `devspace` on an M1 Apple MacBook with our application (~13,000 files), the file sync will fail to start with an `too many...

kind/bug
area/sync

Hi guys. Would be great if devspace provided the json schema generated by the Go struct for the config. Quick googled this [https://github.com/alecthomas/jsonschema](https://github.com/alecthomas/jsonschema) Having json schema allows to import it...

kind/feature
area/config

If you have a helm deployment that sets a namespace different from the namespace used on the command line, ``` deployments: - name: keda namespace: keda helm: chart: name: keda...

kind/bug
area/chart-deployment

**Is your feature request related to a problem?** I'd like to make optimised build contexts for my container images, and I'd like devspace to be able to use them. Right...

I really excited to hear there is an automation deployment ! 1. I tried to deploy a clean laravel project, I doing same as [documentation laravel deployment](https://devspace.cloud/blog/2019/10/16/deploy-laravel-to-kubernetes) but i change...

kind/documentation

**Is your feature request related to a problem?** I've been using `dev.replacePods` to add local env variables to my containers. My only issue with this approach is that it scales...

kind/feature
area/config
area/dev

**What issue type does this pull request address?** (keep at least one, remove the others) /kind enhancement

**What happened?** Deployment failed **What did you expect to happen instead?** Expected successful deployment **How can we reproduce the bug?** (as minimally and precisely as possible) Set multiple deployments to...

kind/bug
area/chart-deployment