DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
Full Changelog: https://github.com/loft-sh/devspace/compare/v6.2.0...v6.2.1
DevSpace now makes it even easier to start developing on Kubernetes. In many cases, it can be difficult to get started when you don't have an established way of pushing images between your local environment and a remote cluster. Setting up a registry when you're only evaluating Kubernetes and DevSpace is sometimes too much to ask.
DevSpace will detect whether you are using a local or remote cluster. When using a remote cluster DevSpace will check if you have push permissions to the image's registry. When you do not have push permissions, DevSpace will deploy an image registry to your cluster with a NodePort service, start port forwarding between your localhost and the registry pod, and update your image URLs to use the new localhost registry URL. The remote cluster will now resolve images from the deployed registry.
For cases when you are using a local Kubernetes cluster, or have push permissions to a remote registry, DevSpace will behave exactly as before. No additional configuration is needed in devspace.yaml, but if you wish to enabled persistence for the local registry, or use a custom registry image, configuration options are available.
Full Changelog: https://github.com/loft-sh/devspace/compare/v6.1.1...v6.2.0
DevSpace now makes it even easier to start developing on Kubernetes. In many cases, it can be difficult to get started when you don't have an established way of pushing images between your local environment and a remote cluster. Setting up a registry when you're only evaluating Kubernetes and DevSpace is sometimes too much to ask.
DevSpace will detect whether you are using a local or remote cluster. When using a remote cluster DevSpace will check if you have push permissions to the image's registry. When you do not have push permissions, DevSpace will deploy an image registry to your cluster with a NodePort service, start port forwarding between your localhost and the registry pod, and update your image URLs to use the new localhost registry URL. The remote cluster will now resolve images from the deployed registry.
For cases when you are using a local Kubernetes cluster, or have push permissions to a remote registry, DevSpace will behave exactly as before. No additional configuration is needed in devspace.yaml, but if you wish to enabled persistence for the local registry, or use a custom registry image, configuration options are available.
Full Changelog: https://github.com/loft-sh/devspace/compare/v6.1.1...v6.2.0-beta.0
DevSpace now makes it even easier to start developing on Kubernetes. In many cases, it can be difficult to get started when you don't have an established way of pushing images between your local environment and a remote cluster. Setting up a registry when you're only evaluating Kubernetes and DevSpace is sometimes too much to ask.
DevSpace will detect whether you are using a local or remote cluster. When using a remote cluster DevSpace will check if you have push permissions to the image's registry. When you do not have push permissions, DevSpace will deploy an image registry to your cluster with a NodePort service, start port forwarding between your localhost and the registry pod, and update your image URLs to use the new localhost registry URL. The remote cluster will now resolve images from the deployed registry.
For cases when you are using a local Kubernetes cluster, or have push permissions to a remote registry, DevSpace will behave exactly as before. No additional configuration is needed in devspace.yaml, but if you wish to enabled persistence for the local registry, or use a custom registry image, configuration options are available.
Full Changelog: https://github.com/loft-sh/devspace/compare/v6.1.2-alpha.0...v6.2.0-alpha.0
Full Changelog: https://github.com/loft-sh/devspace/compare/v6.1.1...v6.1.2-alpha.0
Full Changelog: https://github.com/loft-sh/devspace/compare/v5.18.5...v5.18.6-beta.0
Full Changelog: https://github.com/loft-sh/devspace/compare/v6.1.0...v6.1.1
Full Changelog: https://github.com/loft-sh/devspace/compare/v6.1.0...v6.1.1-beta.0
dev.sync.onUpload.exec.once to only execute a command a single time in a container's lifecyclexargs was sometimes not working correctly for non pipeline functions$$() to escape $() for config expressions\r in pipeline commands--tty flag for devspace enter to disable ttydev.terminal.disableTTY option to disable ttywait_pod function for pipelines that waits for pods / containers to become readyFull Changelog: https://github.com/loft-sh/devspace/compare/v6.0.1...v6.1.0-beta.0
dev.sync.onUpload.exec.once to only execute a command a single time in a container's lifecyclexargs was sometimes not working correctly for non pipeline functions$$() to escape $() for config expressions\r in pipeline commands--tty flag for devspace enter to disable ttydev.terminal.disableTTY option to disable ttywait_pod function for pipelines that waits for pods / containers to become readyFull Changelog: https://github.com/loft-sh/devspace/compare/v6.0.1...v6.1.0-beta.0