DevSpace Changelog

What's new in DevSpace 6.3.12

Mar 1, 2024

What's Changed:
Treat pipeline flag defaults consistently when used as command flags or pipeline flags by @lizardruss in #2798
Do git pull for cached dependencies by @Andrioden in #2766
Update kaniko build image by @lizardruss in #2811
Remove reference to outdated command by @lizardruss in #2812

New in DevSpace 6.3.11 (Feb 17, 2024)

New in DevSpace 6.3.10 (Jan 25, 2024)

New in DevSpace 6.3.9 (Jan 18, 2024)

New in DevSpace 6.3.8 (Jan 2, 2024)

New in DevSpace 6.3.7 (Dec 12, 2023)

New in DevSpace 6.3.6 (Dec 6, 2023)

New in DevSpace 6.3.5 (Nov 16, 2023)

New in DevSpace 6.3.4 (Nov 4, 2023)

New in DevSpace 6.3.3 (Aug 31, 2023)

New in DevSpace 6.3.2 (Mar 28, 2023)

New in DevSpace 6.3.1 (Mar 10, 2023)

New in DevSpace 6.3.0 (Feb 23, 2023)

New in DevSpace 6.2.5 (Jan 28, 2023)

New in DevSpace 6.2.4 (Jan 10, 2023)

New in DevSpace 6.2.3 (Jan 4, 2023)

New in DevSpace 6.2.3 Beta 1 (Dec 29, 2022)

New in DevSpace 6.2.3 Beta 0 (Dec 20, 2022)

New in DevSpace 6.2.2 Pre-releasae (Dec 13, 2022)

New in DevSpace 6.2.1 (Nov 30, 2022)

New in DevSpace 6.2.0 (Nov 29, 2022)

Local Registry:
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.
What's Changed:
Add DEVSPACE_PROFILES variable and is_in command by @alexissellier in #2297
Specify a kubeClient when loading the devspace configuration by @alexissellier in #2306
Add dark-green color for completed state pods in UI by @mahendrabagul in #2335
Improve arch detection of pod when installing devspacehelper by @pratikjagrut in #2336 and @FabianKramm in #2381
Fallback to ssh if https doesn't work when cloning dependencies by @pratikjagrut in #2330 & #2355
Allow importing require statements and show all failures by @dtomasi in #2354
Add disabled flag for dependencies to avoid resolving all dependencies by @lizardruss in #2361
Add proper schema validation for vars by @mahendrabagul in #2343
Fix an issue when authenticating with Azure Container Registry (ACR) by @lizardruss in #2376
Local registry by @lizardruss in #2326
Support "~" (home) at the start of sync path by @matskiv in #2384
Add SIGINT syscall signal before SIGKILL by @mahendrabagul in #2388
Fixed improper parsing of volume name by @ryancharris in #2405
Use 'wss' protocol when DevSpace ui is loaded via 'https' by @lizardruss in #2410
Fixed building in Kaniko from Windows by @lizardruss in #2423
Improve output for pull secret creation by @FabianKramm in #2428
Pass DevSpace vars to plugin environment by @mahendrabagul in #2400
Add global flag for running dependencies sequentially by @pratikjagrut in #2424
Fix commands with predefined variables by @FabianKramm in #2429
Fix local registry failing with multiple dependencies by @lizardruss in #2425
Scale down replica sets to allow transfer of persistPaths persistent volume claims between pods by @lizardruss in #2431
Fix imported variables are not used in other variables by @pratikjagrut in #2432
Generate keys using ecdsa instead of rsa by @pratikjagrut in #2437
Other Changes:
Add is_in function docs by @alexissellier in #2307
Fix a tiny typo by @lianmakesthings in #2311
Hide deprecated printLogs & remoteExec configs in docs by @carlmontanari in #2312
Remove use profile command docs by @alexissellier in #2320
Replace chmod/mv with install command in docs by @tradel in #2327
Remove incorrect docs about environment variables with PowerShell by @lizardruss in #2340
Correct function return value docs by @pratikjagrut in #2347
Fix semantic error in docs example by @Kromtar in #2363
Add Hooks page in docs by @mahendrabagul in #2364
Fix typo in initialize project docs by @mahendrabagul in #2369
Fix typo in Select Dev Container By Pod Labels page by @shepda in #2350
Fix alwaysResolve flag's default value in docs by @mahendrabagul in #2378
Fix issue template labels by @matskiv in #2372
Add devspacehelper build details in contributing guide by @mahendrabagul in #2383
Add profiles for dependency to documentation by @alexissellier in #2396
Corrected documentation page title mistake by @matskiv in #2394
Remove incorrect statement about BuildKit deployment name in documentation by @lizardruss in #2413
Update dependencies by @FabianKramm in #2421
Update sync help msg and documentation by @pratikjagrut in #2438

New in DevSpace 6.2.0 Beta 0 (Nov 24, 2022)

What's Changed:
Add DEVSPACE_PROFILES variable and is_in command by @alexissellier in #2297
Specify a kubeClient when loading the devspace configuration by @alexissellier in #2306
Add dark-green color for completed state pods in UI by @mahendrabagul in #2335
Improve arch detection of pod when installing devspacehelper by @pratikjagrut in #2336 and @FabianKramm in #2381
Fallback to ssh if https doesn't work when cloning dependencies by @pratikjagrut in #2330 & #2355
Allow importing require statements and show all failures by @dtomasi in #2354
Add disabled flag for dependencies to avoid resolving all dependencies by @lizardruss in #2361
Add proper schema validation for vars by @mahendrabagul in #2343
Fix an issue when authenticating with Azure Container Registry (ACR) by @lizardruss in #2376
Local registry by @lizardruss in #2326
Support "~" (home) at the start of sync path by @matskiv in #2384
Add SIGINT syscall signal before SIGKILL by @mahendrabagul in #2388
Fixed improper parsing of volume name by @ryancharris in #2405
Use 'wss' protocol when DevSpace ui is loaded via 'https' by @lizardruss in #2410
Fixed building in Kaniko from Windows by @lizardruss in #2423
Improve output for pull secret creation by @FabianKramm in #2428
Pass DevSpace vars to plugin environment by @mahendrabagul in #2400
Add global flag for running dependencies sequentially by @pratikjagrut in #2424
Fix commands with predefined variables by @FabianKramm in #2429
Fix local registry failing with multiple dependencies by @lizardruss in #2425
Scale down replica sets to allow transfer of persistPaths persistent volume claims between pods by @lizardruss in #2431
Fix imported variables are not used in other variables by @pratikjagrut in #2432
Other Changes:
Add is_in function docs by @alexissellier in #2307
Fix a tiny typo by @lianmakesthings in #2311
Hide deprecated printLogs & remoteExec configs in docs by @carlmontanari in #2312
Remove use profile command docs by @alexissellier in #2320
Replace chmod/mv with install command in docs by @tradel in #2327
Remove incorrect docs about environment variables with PowerShell by @lizardruss in #2340
Correct function return value docs by @pratikjagrut in #2347
Fix semantic error in docs example by @Kromtar in #2363
Add Hooks page in docs by @mahendrabagul in #2364
Fix typo in initialize project docs by @mahendrabagul in #2369
Fix typo in Select Dev Container By Pod Labels page by @shepda in #2350
Fix alwaysResolve flag's default value in docs by @mahendrabagul in #2378
Fix issue template labels by @matskiv in #2372
Add devspacehelper build details in contributing guide by @mahendrabagul in #2383
Add profiles for dependency to documentation by @alexissellier in #2396
Corrected documentation page title mistake by @matskiv in #2394
Remove incorrect statement about BuildKit deployment name in documentation by @lizardruss in #2413
Update dependencies by @FabianKramm in #2421

New in DevSpace 6.1.2 Alpha 0 (Sep 23, 2022)

New in DevSpace 6.1.1 (Sep 13, 2022)

New in DevSpace 6.1.1 Beta 0 (Sep 12, 2022)

New in DevSpace 6.1.0 (Sep 9, 2022)

New in DevSpace 6.1.0 Beta 0 (Sep 9, 2022)

New in DevSpace 6.0.1 (Aug 26, 2022)

New in DevSpace 6.0.1 Beta 1 (Aug 26, 2022)

New in DevSpace 6.0.1 Beta 0 (Aug 25, 2022)

New in DevSpace 6.0.0 (Aug 23, 2022)

DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed Flags:
deployments was removed, use pipeline logic instead
skip-pipeline in devspace dev was removed, use pipeline logic instead
verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
interactive was removed from devspace dev, use pipeline logic instead
parent-profile was removed, use multiple --profile flags instead
restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
verbose-sync was removed, use --debug instead
exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
wait, --timeout was removed, use pipeline logic instead
container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables:
If you are using a variable like this, DevSpace will not ask anymore for its value:
deployments:
name: ...
helm:
values:
key: ${VARIABLE}
rather change it to
vars:
name: VARIABLE
deployments:
name: ...
helm:
values:
key: ${VARIABLE}
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore

New in DevSpace 6.0.0 Beta 9 (Aug 10, 2022)

New in DevSpace 6.0.0 Beta 7 (Jul 21, 2022)

New in DevSpace 6.0.0 Beta 6 (Jul 6, 2022)

With v6 a new config version v2beta1 was introduced, that restructures many parts of the DevSpace config, such as deployments, dev, commands and vars. Older config versions are still supported and will be converted automatically in memory by DevSpace to this new version. To see how the old config got converted, run devspace print, which can be a starting point on how to convert your older DevSpace config.
Pipelines:
DevSpace used a declarative approach to define its dev, build, deploy and purge pipeline, however we felt most of it was hardcoded and difficult to change. We introduced hooks to make these pipelines more adjustable, however in many cases this was difficult to understand as the pipeline was still implicit and through hooks scattered around the devspace.yaml.
With DevSpace v6 we introduce a pipelines concept that allows you to override DevSpace default behaviour and create more dynamic and powerful pipelines compared to what DevSpace offers you as a default. These pipelines are written similar to github actions and DevSpace provides custom commands that allow you to build images, deploy deployments as well as stop and start development. This also allows you to define concurrency a lot easier, so from now on you can easily build, deploy or start development in parallel as you desire.
Example: Simple Declarative Pipeline:
As configurations get more complex, you probably want to reuse config or define it in a separate place, here the declarative approach makes sense that you can reference in your pipeline
Imports:
You want DRY config and we heard you! With imports you can now merge different devspace.yaml's together and define your variables, deployments, commands and pipelines in a single repository or file and import them into other projects through git, urls or local paths. With the new pipelines you can then define what images to build, what deployments to deploy and what dev configurations to start and stop
SSH & Proxy Commands:
It is now possible to let DevSpace setup an SSH connection as well as proxy certain commands from the local host to the container:
With the configuration above you can run the following (proxyCommands also works with terminal or kubectl exec
Breaking Changes:
Removed Flags:
--deployments was removed, use pipeline logic instead
--skip-pipeline in devspace dev was removed, use pipeline logic instead
--verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
--interactive was removed from devspace dev, use pipeline logic instead
--parent-profile was removed, use multiple --profile flags instead
--restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
--verbose-sync was removed, use --debug instead
--exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
--wait, --timeout was removed, use pipeline logic instead
--container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
Devspace dev is not taking any arguments anymore

New in DevSpace 6.0.0 Beta 5 (Jul 6, 2022)

Config Version v2beta1:
With v6 a new config version v2beta1 was introduced, that restructures many parts of the DevSpace config, such as deployments, dev, commands and vars. Older config versions are still supported and will be converted automatically in memory by DevSpace to this new version. To see how the old config got converted, run devspace print, which can be a starting point on how to convert your older DevSpace config.
Pipelines:
DevSpace used a declarative approach to define its dev, build, deploy and purge pipeline, however we felt most of it was hardcoded and difficult to change. We introduced hooks to make these pipelines more adjustable, however in many cases this was difficult to understand as the pipeline was still implicit and through hooks scattered around the devspace.yaml.
With DevSpace v6 we introduce a pipelines concept that allows you to override DevSpace default behaviour and create more dynamic and powerful pipelines compared to what DevSpace offers you as a default. These pipelines are written similar to github actions and DevSpace provides custom commands that allow you to build images, deploy deployments as well as stop and start development. This also allows you to define concurrency a lot easier, so from now on you can easily build, deploy or start development in parallel as you desire.
Imports:
You want DRY config and we heard you! With imports you can now merge different devspace.yaml's together and define your variables, deployments, commands and pipelines in a single repository or file and import them into other projects through git, urls or local paths. With the new pipelines you can then define what images to build, what deployments to deploy and what dev configurations to start and stop
SSH & Proxy Commands:
It is now possible to let DevSpace setup an SSH connection as well as proxy certain commands from the local host to the containe
With the configuration above you can run the following (proxyCommands also works with terminal or kubectl exec):
ssh my-dev.devspace-project.devspace
# Run the following commands inside the container that are proxied to the local computer
$/ git
$/ devspace
$/ kubectl
Breaking Changes:
DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed Flags:
--deployments was removed, use pipeline logic instead
--skip-pipeline in devspace dev was removed, use pipeline logic instead
--verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
--interactive was removed from devspace dev, use pipeline logic instead
--parent-profile was removed, use multiple --profile flags instead
--restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
--verbose-sync was removed, use --debug instead
--exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
--wait, --timeout was removed, use pipeline logic instead
--container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables:
If you are using a variable like this, DevSpace will not ask anymore for its value
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore

New in DevSpace 6.0.0 Beta 4 (Jun 29, 2022)

Config Version v2beta1:
With v6 a new config version v2beta1 was introduced, that restructures many parts of the DevSpace config, such as deployments, dev, commands and vars. Older config versions are still supported and will be converted automatically in memory by DevSpace to this new version. To see how the old config got converted, run devspace print, which can be a starting point on how to convert your older DevSpace config.
Pipelines:
DevSpace used a declarative approach to define its dev, build, deploy and purge pipeline, however we felt most of it was hardcoded and difficult to change. We introduced hooks to make these pipelines more adjustable, however in many cases this was difficult to understand as the pipeline was still implicit and through hooks scattered around the devspace.yaml.
With DevSpace v6 we introduce a pipelines concept that allows you to override DevSpace default behaviour and create more dynamic and powerful pipelines compared to what DevSpace offers you as a default. These pipelines are written similar to github actions and DevSpace provides custom commands that allow you to build images, deploy deployments as well as stop and start development. This also allows you to define concurrency a lot easier, so from now on you can easily build, deploy or start development in parallel as you desire.
SSH & Proxy Commands:
It is now possible to let DevSpace setup an SSH connection as well as proxy certain commands from the local host to the container
With the configuration above you can run the following (proxyCommands also works with terminal or kubectl exec)
Breaking Changes:
DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed Flags:
--deployments was removed, use pipeline logic instead
--skip-pipeline in devspace dev was removed, use pipeline logic instead
--verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
--interactive was removed from devspace dev, use pipeline logic instead
--parent-profile was removed, use multiple --profile flags instead
--restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
--verbose-sync was removed, use --debug instead
--exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
--wait, --timeout was removed, use pipeline logic instead
--container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore
Many other changes:
There are many other improvements and changes that went into this new DevSpace version. We'll release full exhaustive release notes soon.

New in DevSpace 6.0.0 Beta 1 (Jun 23, 2022)

DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed Flags:
deployments was removed, use pipeline logic instead
skip-pipeline in devspace dev was removed, use pipeline logic instead
verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
interactive was removed from devspace dev, use pipeline logic instead
parent-profile was removed, use multiple --profile flags instead
restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
verbose-sync was removed, use --debug instead
exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
wait, --timeout was removed, use pipeline logic instead
container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables
If you are using a variable like this, DevSpace will not ask anymore for its value:
deployments:
name: ...
helm:
values:
key: ${VARIABLE}
rather change it to
vars:
name: VARIABLE
deployments:
name: ...
helm:
values:
key: ${VARIABLE}
Dependency names must be unique
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore

New in DevSpace 6.0.0 Beta 0 (Jun 21, 2022)

Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore
Pipelines:
DevSpace used a declarative approach to define its dev, build, deploy and purge pipeline, however we felt most of it was hardcoded and difficult to change. We introduced hooks to make these pipelines more adjustable, however in many cases this was difficult to understand as the pipeline was still implicit and through hooks scattered around the devspace.yaml.
With DevSpace v6 we introduce a pipelines concept that allows you to override DevSpace default behaviour and create more dynamic and powerful pipelines compared to what DevSpace offers you as a default. These pipelines are written similar to github actions and DevSpace provides custom commands that allow you to build images, deploy deployments as well as stop and start development. This also allows you to define concurrency a lot easier, so from now on you can easily build, deploy or start development in parallel as you desire.
Imports:
You want DRY config and we heard you! With imports you can now merge different devspace.yaml's together and define your variables, deployments, commands and pipelines in a single repository or file and import them into other projects through git, urls or local paths.
SSH & Proxy Commands:
It is now possible to let DevSpace setup an SSH connection as well as proxy certain commands from the local host to the container.
Removed Flags:
--deployments was removed, use pipeline logic instead
--skip-pipeline in devspace dev was removed, use pipeline logic instead
--verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
--interactive was removed from devspace dev, use pipeline logic instead
--parent-profile was removed, use multiple --profile flags instead
--restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
--verbose-sync was removed, use --debug instead
--exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
--wait, --timeout was removed, use pipeline logic instead
--container-path and --local-path were removed from devspace sync, please use --path instead
DevSpace will no longer ask for undefined variables:
If you are using a variable like this, DevSpace will not ask anymore for its value.
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.

New in DevSpace 6.0.0 Alpha 18 (May 14, 2022)

Breaking Changes:
DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed Flags:
deployments was removed, use pipeline logic instead
skip-pipeline in devspace dev was removed, use pipeline logic instead
verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
interactive was removed from devspace dev, use pipeline logic instead
parent-profile was removed, use multiple --profile flags instead
restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
verbose-sync was removed, use --debug instead
exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
wait, --timeout was removed, use pipeline logic instead
container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables:
If you are using a variable like this, DevSpace will not ask anymore for its value
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore

New in DevSpace 5.18.5 Beta 3 (May 13, 2022)

New in DevSpace 5.18.5 Beta 2 (May 13, 2022)

New in DevSpace 6.0.0 Alpha 17 (May 6, 2022)

New in DevSpace 6.0.0 Alpha 16 (Apr 28, 2022)

New in DevSpace 6.0.0 Alpha 15 (Apr 20, 2022)

Breaking Changes:
DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed Flags:
deployments was removed, use pipeline logic instead
skip-pipeline in devspace dev was removed, use pipeline logic instead
verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
interactive was removed from devspace dev, use pipeline logic instead
parent-profile was removed, use multiple --profile flags instead
restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
verbose-sync was removed, use --debug instead
exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
wait, --timeout was removed, use pipeline logic instead
container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables
If you are using a variable like this, DevSpace will not ask anymore for its value
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore

New in DevSpace 6.0.0 Alpha 14 (Apr 19, 2022)

New in DevSpace 6.0.0 Alpha 13 (Apr 16, 2022)

DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed Flags:
deployments was removed, use pipeline logic instead
skip-pipeline in devspace dev was removed, use pipeline logic instead
verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
interactive was removed from devspace dev, use pipeline logic instead
parent-profile was removed, use multiple --profile flags instead
restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
verbose-sync was removed, use --debug instead
exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
wait, --timeout was removed, use pipeline logic instead
container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables:
If you are using a variable like this, DevSpace will not ask anymore for its value
Dependency names must be unique
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore

New in DevSpace 6.0.0 Alpha 11 (Apr 12, 2022)

Config Version v2beta1:
With v6 a new config version v2beta1 was introduced, that restructures many parts of the DevSpace config, such as deployments, dev, commands and vars. Older config versions are still supported and will be converted automatically in memory by DevSpace to this new version. To see how the old config got converted, run devspace print, which can be a starting point on how to convert your older DevSpace config.
Pipelines:
DevSpace used a declarative approach to define its dev, build, deploy and purge pipeline, however we felt most of it was hardcoded and difficult to change. We introduced hooks to make these pipelines more adjustable, however in many cases this was difficult to understand as the pipeline was still implicit and through hooks scattered around the devspace.yaml.
With DevSpace v6 we introduce a pipelines concept that allows you to override DevSpace default behaviour and create more dynamic and powerful pipelines compared to what DevSpace offers you as a default. These pipelines are written similar to github actions and DevSpace provides custom commands that allow you to build images, deploy deployments as well as stop and start development. This also allows you to define concurrency a lot easier, so from now on you can easily build, deploy or start development in parallel as you desire.
Example: Simple Procedural Pipeline:
With pipelines you can decide if to use the declarative approach or define objects on the fly with the --set flag. A simple project that deploys an alpine container and then starts syncing to it can be purely written in the new pipeline form
Example: Simple Declarative Pipeline:
As configurations get more complex, you probably want to reuse config or define it in a separate place, here the declarative approach makes sense that you can reference in your pipeline
Imports:
You want DRY config and we heard you! With imports you can now merge different devspace.yaml's together and define your variables, deployments, commands and pipelines in a single repository or file and import them into other projects through git, urls or local paths. With the new pipelines you can then define what images to build, what deployments to deploy and what dev configurations to start and stop
It is now possible to let DevSpace setup an SSH connection as well as proxy certain commands from the local host to the container
With the configuration above you can run the following (proxyCommands also works with terminal or kubectl exec)
Breaking Changes:
DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables:
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore

New in DevSpace 6.0.0 Alpha 10 (Apr 8, 2022)

New in DevSpace 6.0.0 Alpha 9 (Apr 6, 2022)

New in DevSpace 6.0.0 Alpha 8 (Apr 5, 2022)

New in DevSpace 6.0.0 Alpha 7 (Apr 1, 2022)

New in DevSpace 6.0.0 Alpha 6 (Mar 31, 2022)

With v6 a new config version v2beta1 was introduced, that restructures many parts of the DevSpace config, such as deployments, dev, commands and vars. Older config versions are still supported and will be converted automatically in memory by DevSpace to this new version. To see how the old config got converted, run devspace print, which can be a starting point on how to convert your older DevSpace config.
Pipelines:
DevSpace used a declarative approach to define its dev, build, deploy and purge pipeline, however we felt most of it was hardcoded and difficult to change. We introduced hooks to make these pipelines more adjustable, however in many cases this was difficult to understand as the pipeline was still implicit and through hooks scattered around the devspace.yaml.
With DevSpace v6 we introduce a pipelines concept that allows you to override DevSpace default behaviour and create more dynamic and powerful pipelines compared to what DevSpace offers you as a default. These pipelines are written similar to github actions and DevSpace provides custom commands that allow you to build images, deploy deployments as well as stop and start development. This also allows you to define concurrency a lot easier, so from now on you can easily build, deploy or start development in parallel as you desire.
Example: Simple Procedural Pipeline
With pipelines you can decide if to use the declarative approach or define objects on the fly with the --set flag. A simple project that deploys an alpine container and then starts syncing to it can be purely written in the new pipeline form
Imports:
You want DRY config and we heard you! With imports you can now merge different devspace.yaml's together and define your variables, deployments, commands and pipelines in a single repository or file and import them into other projects through git, urls or local paths. With the new pipelines you can then define what images to build, what deployments to deploy and what dev configurations to start and stop
SSH & Proxy Commands:
It is now possible to let DevSpace setup an SSH connection as well as proxy certain commands from the local host to the container
Breaking Changes:
Removed Flags:
--deployments was removed, use pipeline logic instead
--skip-pipeline in devspace dev was removed, use pipeline logic instead
--verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
--interactive was removed from devspace dev, use pipeline logic instead
--parent-profile was removed, use multiple --profile flags instead
--restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
--verbose-sync was removed, use --debug instead
--exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
--wait, --timeout was removed, use pipeline logic instead
--container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables
If you are using a variable like this, DevSpace will not ask anymore for its value
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore

New in DevSpace 6.0.0 Alpha 3 (Mar 29, 2022)

New in DevSpace 6.0.0 Alpha 2 (Mar 25, 2022)

Pipelines:
DevSpace used a declarative approach to define its dev, build, deploy and purge pipeline, however we felt most of it was hardcoded and difficult to change. We introduced hooks to make these pipelines more adjustable, however in many cases this was difficult to understand as the pipeline was still implicit and through hooks scattered around the devspace.yaml.
With DevSpace v6 we introduce a pipelines concept that allows you to override DevSpace default behaviour and create more dynamic and powerful pipelines compared to what DevSpace offers you as a default. These pipelines are written similar to github actions and DevSpace provides custom commands that allow you to build images, deploy deployments as well as stop and start development. This also allows you to define concurrency a lot easier, so from now on you can easily build, deploy or start development in parallel as you desire.
Imports:
You want DRY config and we heard you! With imports you can now merge different devspace.yaml's together and define your variables, deployments, commands and pipelines in a single repository or file and import them into other projects through git, urls or local paths. With the new pipelines you can then define what images to build, what deployments to deploy and what dev configurations to start and stop
SSH & Proxy Commands:
It is now possible to let DevSpace setup an SSH connection as well as proxy certain commands from the local host to the container
With the configuration above you can run the following (proxyCommands also works with terminal or kubectl exec)
Breaking Changes:
DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed Flags:
--deployments was removed, use pipeline logic instead
--skip-pipeline in devspace dev was removed, use pipeline logic instead
--verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
--interactive was removed from devspace dev, use pipeline logic instead
--parent-profile was removed, use multiple --profile flags instead
--restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
--verbose-sync was removed, use --debug instead
--exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
--wait, --timeout was removed, use pipeline logic instead
--container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore
Many other changes:
There are many other improvements and changes that went into this new DevSpace version. We'll release full exhaustive release notes soon.

New in DevSpace 6.0.0 Alpha 0 (Mar 22, 2022)

Pipelines:
DevSpace used a declarative approach to define its dev, build, deploy and purge pipeline, however we felt most of it was hardcoded and difficult to change. We introduced hooks to make these pipelines more adjustable, however in many cases this was difficult to understand as the pipeline was still implicit and through hooks scattered around the devspace.yaml.
With DevSpace v6 we introduce a pipelines concept that allows you to override DevSpace default behaviour and create more dynamic and powerful pipelines compared to what DevSpace offers you as a default. These pipelines are written similar to github actions and DevSpace provides custom commands that allow you to build images, deploy deployments as well as stop and start development. This also allows you to define concurrency a lot easier, so from now on you can easily build, deploy or start development in parallel as you desire.
Example - Simple Procedural Pipeline:
With pipelines you can decide if to use the declarative approach or define objects on the fly with the --set flag. A simple project that deploys an alpine container and then starts syncing to it can be purely written in the new pipeline form:
Example - Simple Declarative Pipeline:
As configurations get more complex, you probably want to reuse config or define it in a separate place, here the declarative approach makes sense that you can reference in your pipeline:
Imports:
You want DRY config and we heard you! With imports you can now merge different devspace.yaml's together and define your variables, deployments, commands and pipelines in a single repository or file and import them into other projects through git, urls or local paths. With the new pipelines you can then define what images to build, what deployments to deploy and what dev configurations to start and stop:
SSH & Proxy Commands:
It is now possible to let DevSpace setup an SSH connection as well as proxy certain commands from the local host to the container
Breaking Changes:
DevSpace version 6 introduces some breaking changes to work efficiently with the new Pipelines feature. Almost all older devspace.yaml should still work as config is migrated automatically, however we removed some deprecated and older functionality that we felt is now either obsolete or unused.
Removed Flags:
--deployments was removed, use pipeline logic instead
--skip-pipeline in devspace dev was removed, use pipeline logic instead
--verbose-dependencies and --skip-dependencies was removed and dependencies will be pulled every run
--interactive was removed from devspace dev, use pipeline logic instead
--parent-profile was removed, use multiple --profile flags instead
--restore-vars, --vars-secret and --save-vars was removed. Use vars.MY_VAR.remote: true instead
--verbose-sync was removed, use --debug instead
--exit-after-deploy, --terminal-reconnect, --portforwarding and --sync was removed
--wait, --timeout was removed, use pipeline logic instead
--container-path and --local-path were removed from devspace sync, please use --path instead
Removed dev.autoReload:
This functionality was removed from DevSpace and will be replaced in future by automatically reloading pipelines
DevSpace will no longer ask for undefined variables
Dependency names must be unique:
DevSpace determines which dependency was deployed now solely based on the name, so multiple dependencies or nested dependencies with the same name will be resolved as the same dependency and deployed only once.
Other Breaking Changes:
Removed devspace use profile instead use profile activation instead
Removed dependencies[*].skipBuild
Removed dev.sync[*].onDownload
Removed deployments[*].helm.driver, deployments[*].helm.deleteArgs, deployments[*].kubectl.deleteArgs and deployments[*].helm.path
Removed deployments[*].helm.v2
Dependencies are now purged after deployments are deleted instead of before
Variables in commands will be resolved by default now
devspace dev is not taking any arguments anymore

New in DevSpace 5.18.4 Beta 1 (Feb 11, 2022)

New in DevSpace 5.18.4 Beta 0 (Feb 7, 2022)

New in DevSpace 5.18.3 (Feb 1, 2022)

New in DevSpace 5.18.3 Pre-release (Feb 1, 2022)

New in DevSpace 5.18.3 Beta 1 (Jan 31, 2022)

New in DevSpace 5.18.3 Beta 0 (Jan 24, 2022)

New in DevSpace 5.18.2 (Jan 12, 2022)

New in DevSpace 5.18.2 Beta 0 (Jan 7, 2022)

New in DevSpace 5.18.1 (Dec 16, 2021)

New in DevSpace 5.18.1 Beta 0 (Dec 16, 2021)

New in DevSpace 5.18.0 (Dec 15, 2021)

New Features:
Allow profiles to be defined by expressions:
profiles: $(cat profiles.yaml)
Allow items of profiles array to be defined by expressions:
profiles:
$(cat profile1.yaml)
Allow profile content to be defined by expressions:
profiles:
name: production
merge:
deployments: $(cat production.yaml)
Simplified custom builder commands:
images:
default:
image: myuser/image
build:
custom:
skipImageArg: true
command: |-
Also works on windows as this is executed in a golang shell
docker build -t ${runtime.images.default.image}:${runtime.images.default.tag} . -f custom/Dockerfile
onChange:
main.go
New options deployments.*.disabled, dependencies.*.disabled, pullSecrets.*.pullSecrets & hooks.*.disabled to make usage of those config areas easier to use with config expressions:
hooks:
name: load-into-kind
disabled: $( [ ${devspace.context} != "kind" ] && echo "true" || echo "false" )
command: |-
kind load docker-image ${runtime.images.app.image}:${runtime.images.app.tag}
events: ["before:deploy"]
New hook events before:resolveDependencies, after:resolveDependencies, error:resolveDependencies, before:buildDependencies, after:buildDependencies, error:buildDependencies, before:deployDependencies, after:deployDependencies, error:deployDependencies, before:purgeDependencies, after:purgeDependencies, error:purgeDependencies that also work for nested dependencies
DevSpace now detects docker-compose.yaml when running devspace init and provides an option to generate an initial devspace.yaml from docker compose
DevSpace now simulates docker compose volume behaviour by uploading local files to an init container with the relevant volumes mounted. Once uploads are complete the init container exits and the application continues as expected.
DevSpace now adds devspace.yaml configured commands to cobra command configuration and shows them in devspace --help and devspace run --help
Deprecated the -s flag and instead DevSpace will now ask if the Kube context or the namespace has changed
New --dependency flag for devspace print to show a loaded dependency config
New option deployments.helm.chart.git to deploy a helm chart from a git repository instead of helm registry
New option dev.replacePods.persistPaths.initConainter.resources to configure resources for the pre-populating init container (#1775)
Changes:
Renamed predefined variables to camelCase and using a .. The old predefined variable names can still be used, but are deprecated
DevSpace will now always try to list all helm releases in a namespace to find the correct deployment status (#1772)
DevSpace will now print by default why it is rebuilding an image
DevSpace will now print all filesystem events it receives for syncing files if --debug is specified and show if a file wasn't synced
Display stdout / stderr if downloading devspacehelper fails
Updated Helm v3 version that is downloaded if helm is not found (thanks @ragnarpa)
DevSpace will now use the replacePods[*].containerName if multiple containers are found within a replaced pod and no replacePods[*].persistPaths[*].containerName is defined
Improved sync change detection for folders
Improved logging why DevSpace is restarting sync or port-forwarding
Improved logging if DevSpace is waiting for a pod to become running
Fixes:
Fixed an issue where DevSpace would fail using new kubectl version v1.23 (#1813)
Fixed an issue where DevSpace would allow substring matches from activating profiles. For example: an expression test would match test123
Fixed an issue where DevSpace would hang starting the sync if a recursive symlink was found
Fixed an issue where sync exec name was not named correctly (#1789)
Fixed an issue where DevSpace would fail on arm64 systems during sync with too many files open (#1444)
Fixed an issue where DevSpace was showing dependency ids instead of names
Fixed an issue where DevSpace would create a failing pod if the persistence path would not exist in the target container
Fixed a nil pointer if replacing a path with an empty value (#1774)
Fixed an issue where devspace build would fail if there wasn't a valid kube context (thanks @wollowizard) (#1769)
Fixed an issue where DevSpace would use the wrong path for syncing (#1743)

New in DevSpace 5.18.0 RC 0 (Dec 14, 2021)

Profile Activation via DevSpace vars:
DevSpace now supports automatic profile activation via DevSpace variables. This allows you to auto activate profiles based on selected namespace, kube context or even custom commands
Runtime Variables:
Added runtime variables that are prefixed with ${runtime.} and replace the helper syntax image() and tag(). Those variables are useful to access certain runtime information, such as hook output or image tags, but can only be used in certain config areas that will be evaluated later on (such as deployments.*.helm.values)
New Features:
Allow profiles to be defined by expressions
Allow items of profiles array to be defined by expressions
Allow profile content to be defined by expressions
Simplified custom builder commands
New options deployments.*.disabled, dependencies.*.disabled, pullSecrets.*.pullSecrets & hooks.*.disabled to make usage of those config areas easier to use with config expressions
New hook events before:resolveDependencies, after:resolveDependencies, error:resolveDependencies, before:buildDependencies, after:buildDependencies, error:buildDependencies, before:deployDependencies, after:deployDependencies, error:deployDependencies, before:purgeDependencies, after:purgeDependencies, error:purgeDependencies that also work for nested dependencies
DevSpace now detects docker-compose.yaml when running devspace init and provides an option to generate an initial devspace.yaml from docker compose
DevSpace now simulates docker compose volume behaviour by uploading local files to an init container with the relevant volumes mounted. Once uploads are complete the init container exits and the application continues as expected.
DevSpace now adds devspace.yaml configured commands to cobra command configuration and shows them in devspace --help and devspace run --help
Deprecated the -s flag and instead DevSpace will now ask if the Kube context or the namespace has changed
New --dependency flag for devspace print to show a loaded dependency config
New option deployments.helm.chart.git to deploy a helm chart from a git repository instead of helm registry
New option dev.replacePods.persistPaths.initConainter.resources to configure resources for the pre-populating init container (#1775)
Changes:
Renamed predefined variables to camelCase and using a .. The old predefined variable names can still be used, but are deprecated
DevSpace will now always try to list all helm releases in a namespace to find the correct deployment status (#1772)
DevSpace will now print by default why it is rebuilding an image
DevSpace will now print all filesystem events it receives for syncing files if --debug is specified and show if a file wasn't synced
Display stdout / stderr if downloading devspacehelper fails
Updated Helm v3 version that is downloaded if helm is not found (thanks @ragnarpa)
DevSpace will now use the replacePods[*].containerName if multiple containers are found within a replaced pod and no replacePods[*].persistPaths[*].containerName is defined
Improved sync change detection for folders
Improved logging why DevSpace is restarting sync or port-forwarding
Improved logging if DevSpace is waiting for a pod to become running
Fixes:
Fixed an issue where DevSpace would fail using new kubectl version v1.23 (#1813)
Fixed an issue where DevSpace would allow substring matches from activating profiles. For example: an expression test would match test123
Fixed an issue where DevSpace would hang starting the sync if a recursive symlink was found
Fixed an issue where sync exec name was not named correctly (#1789)
Fixed an issue where DevSpace would fail on arm64 systems during sync with too many files open (#1444)
Fixed an issue where DevSpace was showing dependency ids instead of names
Fixed an issue where DevSpace would create a failing pod if the persistence path would not exist in the target container
Fixed a nil pointer if replacing a path with an empty value (#1774)
Fixed an issue where devspace build would fail if there wasn't a valid kube context (thanks @wollowizard) (#1769)
Fixed an issue where DevSpace would use the wrong path for syncing (#1743)

New in DevSpace 5.18.0 Beta 4 (Dec 7, 2021)

DevSpace now detects docker-compose.yaml when running devspace init and provides an option to generate an initial devspace.yaml from docker compose
DevSpace now simulates docker compose volume behaviour by uploading local files to an init container with the relevant volumes mounted. Once uploads are complete the init container exits and the application continues as expected.
DevSpace now adds devspace.yaml configured commands to cobra command configuration and shows them in devspace --help and devspace run --help
Deprecated the -s flag and instead DevSpace will now ask if the Kube context or the namespace has changed
New --dependency flag for devspace print to show a loaded dependency config
New option deployments.helm.chart.git to deploy a helm chart from a git repository instead of helm registry
New option dev.replacePods.persistPaths.initConainter.resources to configure resources for the pre-populating init container
DevSpace will now always try to list all helm releases in a namespace to find the correct deployment status
DevSpace will now print by default why it is rebuilding an image
DevSpace will now print all filesystem events it receives for syncing files if --debug is specified and show if a file wasn't synced
Display stdout / stderr if downloading devspacehelper fails
Updated Helm v3 version that is downloaded if helm is not found (thanks @ragnarpa)
DevSpace will now print by default why it is rebuilding an image
DevSpace will now use the replacePods[*].containerName if multiple containers are found within a replaced pod and no replacePods[*].persistPaths[*].containerName is defined
Improved sync change detection for folders
Fixed an issue where DevSpace would allow substring matches from activating profiles. For example: an expression test would match test123
Fixed an issue where DevSpace would hang starting the sync if a recursive symlink was found
Fixed an issue where sync exec name was not named correctly
Fixed an issue where DevSpace would fail on arm64 systems during sync with too many files open
Fixed an issue where DevSpace was showing dependency ids instead of names
Fixed an issue where DevSpace would create a failing pod if the persistence path would not exist in the target container
Fixed a nil pointer if replacing a path with an empty value
Fixed an issue where devspace build would fail if there wasn't a valid kube context (thanks @wollowizard)
Fixed an issue where DevSpace would use the wrong path for syncing

New in DevSpace 5.18.0 Beta 3 (Dec 7, 2021)

Changes:
DevSpace now detects docker-compose.yaml when running devspace init and provides an option to generate an initial devspace.yaml from docker compose
DevSpace now simulates docker compose volume behaviour by uploading local files to an init container with the relevant volumes mounted. Once uploads are complete the init container exits and the application continues as expected.
DevSpace now adds devspace.yaml configured commands to cobra command configuration and shows them in devspace --help and devspace run --help
Deprecated the -s flag and instead DevSpace will now ask if the Kube context or the namespace has changed
New --dependency flag for devspace print to show a loaded dependency config
New option deployments.helm.chart.git to deploy a helm chart from a git repository instead of helm registry
New option dev.replacePods.persistPaths.initConainter.resources to configure resources for the pre-populating init container (#1775)
DevSpace will now always try to list all helm releases in a namespace to find the correct deployment status (#1772)
DevSpace will now print by default why it is rebuilding an image
DevSpace will now print all filesystem events it receives for syncing files if --debug is specified and show if a file wasn't synced
Display stdout / stderr if downloading devspacehelper fails
Updated Helm v3 version that is downloaded if helm is not found (thanks @ragnarpa)
DevSpace will now print by default why it is rebuilding an image
DevSpace will now use the replacePods[*].containerName if multiple containers are found within a replaced pod and no replacePods[*].persistPaths[*].containerName is defined
Fixed an issue where sync exec name was not named correctly (#1789)
Fixed an issue where DevSpace would fail on arm64 systems during sync with too many files open (#1444)
Fixed an issue where DevSpace was showing dependency ids instead of names
Fixed an issue where DevSpace would create a failing pod if the persistence path would not exist in the target container
Fixed a nil pointer if replacing a path with an empty value (#1774)
Fixed an issue where devspace build would fail if there wasn't a valid kube context (thanks @wollowizard) (#1769)
Fixed an issue where DevSpace would use the wrong path for syncing (#1743)

New in DevSpace 5.18.0 Beta 1 (Nov 30, 2021)

New in DevSpace 5.18.0 Beta 0 (Nov 29, 2021)

New in DevSpace 5.17.0 (Nov 11, 2021)

New in DevSpace 5.17.0 Beta 11 (Nov 11, 2021)

Conditional Sync Commands:
New option dev.sync[*].onUpload.exec that allows you to define commands that are executed on certain file changes. DevSpace makes sure that these commands are only executed after initial sync has finished and before the container might be restarted.
Persistent Paths:
New option dev.replacePods[*].persistPaths that allows you to persist certain paths with PVCs within the replaced pod for quicker syncing.
Changes:
New option dev.replacePods[*].name to define a name for the replace pods configuration
New option dev.replacePods[*].persistenceOptions that allows you to define PVC options for the dev.replacePods[*].persistPaths feature
New flag --name for devspace restart to select a sync config
New option hooks[*].name to name hooks
Added support for Dockerfile.dockerignore
DevSpace will now ping the underlying connection during reverse port forwarding to detect hanging connections
DevSpace helper will now close automatically if multiple pings are missed
Improved initial sync startup time
DevSpace will now download and install kubectl or helm if those commands are used in a hook and not found locally
dev.replacePods are now replaced in parallel
dev.ports are now started in parallel
Fixed an issue where DevSpace would not rebuild even though the image would not be present in the local docker daemon
Removed Applied additional flags from environment message
Improved error message if no kube context was found
Improved config validation
Improved logging behaviour for dev.replacePods and dev.ports
Updated default kaniko version to v1.6.0; Added a warning for problematic exclude paths
Fixed an issue where klog v2 messages would be visible to the user
Fixed an issue where deployments[*].helm.timeout was a number instead of a string
Using devspace within a command or hook will now target the current executed binary
DevSpace will now try initially to download the devspacehelper in the container instead of uploading it (#1729)
Fixed an issue where DevSpace wouldn't sync files initially with newer timestamp locally
Improved local image lookup to consider all tags

New in DevSpace 5.17.0 Beta 10 (Nov 4, 2021)

New in DevSpace 5.17.0 Beta 8 (Nov 1, 2021)

Conditional Sync Commands:
New option dev.sync[*].onUpload.exec that allows you to define commands that are executed on certain file changes. DevSpace makes sure that these commands are only executed after initial sync has finished and before the container might be restarted.
Persistent Paths:
New option dev.replacePods[*].persistPaths that allows you to persist certain paths with PVCs within the replaced pod for quicker syncing.
Changes:
New option dev.replacePods[*].name to define a name for the replace pods configuration
New option dev.replacePods[*].persistenceOptions that allows you to define PVC options for the dev.replacePods[*].persistPaths feature
New flag --name for devspace restart to select a sync config
New option hooks[*].name to name hooks
DevSpace will now ping the underlying connection during reverse port forwarding to detect hanging connections
DevSpace helper will now close automatically if multiple pings are missed
Improved initial sync startup time
DevSpace will now download and install kubectl or helm if those commands are used in a hook and not found locally
dev.replacePods are now replaced in parallel
dev.ports are now started in parallel
Fixed an issue where DevSpace would not rebuild even though the image would not be present in the local docker daemon
Removed Applied additional flags from environment message
Improved error message if no kube context was found
Improved config validation
Improved logging behaviour for dev.replacePods and dev.ports
Updated default kaniko version to v1.6.0; Added a warning for problematic exclude paths
Fixed an issue where klog v2 messages would be visible to the user
Fixed an issue where deployments[*].helm.timeout was a number instead of a string
Using devspace within a command or hook will now target the current executed binary
DevSpace will now try initially to download the devspacehelper in the container instead of uploading it (#1729)
Fixed an issue where DevSpace wouldn't sync files initially with newer timestamp locally
Improved local image lookup to consider all tags

New in DevSpace 5.17.0 Beta 7 (Oct 27, 2021)

New in DevSpace 5.17.0 Beta 6 (Oct 22, 2021)

New in DevSpace 5.17.0 Beta 5 (Oct 20, 2021)

New in DevSpace 5.17.0 Beta 4 (Oct 12, 2021)

New in DevSpace 5.17.0 Beta 1 (Oct 6, 2021)

New in DevSpace 5.17.0 Beta 0 (Oct 6, 2021)

New in DevSpace 5.16.1 Beta 1 (Oct 4, 2021)

New in DevSpace 5.16.1 Beta 0 (Sep 29, 2021)

New in DevSpace 5.16.0 Beta 3 (Sep 23, 2021)

Config Expressions:
Config expressions are a powerful feature to load the devspace.yaml in a more dynamic way. A config expression works by specifying $( my bash expression ) instead of a field and the stdout of the bash expression is taken as value instead.
Load a deployment specification from file:
deployments:
$(cat deployment.yaml)
Change config based on devspace variables:
deployments:
Inline if-else
$( [ ${DEVSPACE_NAMESPACE} == "test" ] && cat deployment.yaml || echo "" )
Multiline if-else
if [ ${DEVSPACE_CONTEXT} == "minikube" ]; then
cat minikube.yaml
else
echo ""
Generate a complete section
dev: $(./my-script.sh ${DEVSPACE_NAMESPACE} ${DEVSPACE_CONTEXT} ${DEVSPACE_PROFILE})
Return JSON
images:
test:
image: my-image/image
build: '$( echo {"disabled": true} )'
New config version v1beta11:
Removed imageName as selector, please use imageSelector: image(name):tag(name) instead
Removed dev.logs.images, please use dev.logs.selectors instead
Renamed hooks.where.container to hooks.container
commands.appendArgs now defaults to false
dependencies[*].overrideVars now defaults to false
Renamed hooks.when to hooks.events, which is a string array now that supports the following events:
before:deploy, after:deploy, before:deploy:[name], after:deploy:[name], error:deploy:[name], skip:deploy:[name]: executed while DevSpace deploys deployments. [name] can be replaced with the config name of a deployment or * to match all.
before:render, after:render, before:render:[name], after:render:[name], error:render:[name]: executed while DevSpace renders deployments during devspace render. [name] can be replaced with the config name of a deployment or * to match all.
before:purge, after:purge, before:purge:[name], after:purge:[name], error:purge:[name]: executed while DevSpace purges deployments during devspace purge. [name] can be replaced with the config name of a deployment or * to match all.
before:build, after:build, before:build:[name], after:build:[name], error:build:[name], skip:build:[name]: executed while DevSpace builds images. [name] can be replaced with the config name of an image or * to match all.
start:sync:[name], stop:sync:[name], error:sync:[name], restart:sync:[name], before:initialSync:[name], after:initialSync:[name], error:initialSync:[name]: executed while DevSpace syncs files with dev.sync. [name] can be replaced with the config name of a sync configuration or * to match all.
start:portForwarding:[name], restart:portForwarding:[name], error:portForwarding:[name], stop:portForwarding:[name]: executed while DevSpace port forwards with dev.ports. [name] can be replaced with the config name of a port forwarding configuration or * to match all.
start:reversePortForwarding:[name], restart:reversePortForwarding:[name], error:reversePortForwarding:[name], stop:reversePortForwarding:[name]: executed while DevSpace reverse port forwards with dev.ports. [name] can be replaced with the config name of a port forwarding configuration or * to match all.
before:createPullSecrets, after:createPullSecrets, error:createPullSecrets: executed while DevSpace creates pullSecrets
devCommand:before:execute, devCommand:after:execute, devCommand:error, devCommand:interrupt, devCommand:before:sync, devCommand:after:sync, devCommand:before:portForwarding, devCommand:after:portForwarding, devCommand:before:replacePods, devCommand:after:replacePods, devCommand:before:runPipeline, devCommand:after:runPipeline, devCommand:before:deployDependencies, devCommand:after:deployDependencies, devCommand:before:build, devCommand:after:build, devCommand:before:deploy, devCommand:after:deploy, devCommand:before:openTerminal, devCommand:before:streamLogs: executed at certain lifecycle events during the devspace dev command
deployCommand:before:execute, deployCommand:after:execute, deployCommand:error, deployCommand:interrupt executed at different checkpoints when devspace deploy is executed
purgeCommand:before:execute, purgeCommand:after:execute, purgeCommand:error, purgeCommand:interrupt executed at different checkpoints when devspace purge is executed
buildCommand:before:execute, buildCommand:after:execute, buildCommand:error, buildCommand:interrupt executed at different checkpoints when devspace build is executed
Wildcard and filter paths for patches:
It is now possible to use filter paths and wildcards in profile & pod patches. For example:
images:
backend:
image: john/devbackend
backend-debugger:
image: john/debugger
deployments:
name: backend
helm:
componentChart: true
values:
containers:
image: john/devbackend
image: john/debugger
profiles:
name: staging
patches:
op: replace
path: ..[?(@.image=='john/devbackend')].image
value: john/stagingbackend
op: remove
path: deployments..[?(@.image=='john/debugger')]
For more informations take a look at the docs.
Other Changes:
You can now use image(default) and tag(default) in hook commands and args:
images:
test:
image: test/test
hooks:
command: |-
./custom-script image(test):tag(test) # -> Transformed to ./custom-script test/test:#####
when:
after:
images: all
Added new option hooks[*].container.once that will execute remote container command hooks only once during the lifetime of a container
DevSpace will now use a replica set instead of single pod as pod replacement
DevSpace will now set the statefulsets pod name as hostname in the replaced pods
DevSpace will now also write sync logs to .devspace/logs/sync.log even if shown in terminal
DevSpace will now try to restart the terminal if an unexpected exit code occurred during devspace dev. Can be disabled via the flag --terminal-reconnect=false
New flag --reconnect for command devspace enter to restart the terminal if an unexpected exit code was encountered
New flag --image-selector for commands devspace enter, devspace logs & devspace attach
Fixed an issue where pathType was not automatically set for newer ingress versions
Fixed an issue where namespace and context were wrong in UI commands
Fixed an issue where replacing pods with the same image selector across different devspace.yaml would target the same pods (#1633)
Renamed plugin hook names to match config hook names
Improved port forwarding & reverse port forwarding logging
Fixed an issue where paths that include a symlink would not sync correctly

New in DevSpace 5.16.0 Beta 2 (Sep 20, 2021)

Config Expressions:
Config expressions are a powerful feature to load the devspace.yaml in a more dynamic way. A config expression works by specifying $( my bash expression ) instead of a field and the stdout of the bash expression is taken as value instead.
Load a deployment specification from file:
deployments:
$(cat deployment.yaml)
Change config based on devspace variables:
deployments:
Inline if-else
$( [ ${DEVSPACE_NAMESPACE} == "test" ] && cat deployment.yaml || echo "" )
Multiline if-else
if [ ${DEVSPACE_CONTEXT} == "minikube" ]; then
cat minikube.yaml
else
echo ""
Generate a complete section
dev: $(./my-script.sh ${DEVSPACE_NAMESPACE} ${DEVSPACE_CONTEXT} ${DEVSPACE_PROFILE})
Return JSON:
images:
test:
image: my-image/image
build: '$( echo {"disabled": true} )'
New config version v1beta11:
Removed imageName as selector, please use imageSelector: image(name):tag(name) instead
Removed dev.logs.images, please use dev.logs.selectors instead
Renamed hooks.where.container to hooks.container
commands.appendArgs now defaults to false
dependencies[*].overrideVars now defaults to false
Renamed hooks.when to hooks.events, which is a string array now that supports the following events:
before:deploy, after:deploy, before:deploy:[name], after:deploy:[name], error:deploy:[name], skip:deploy:[name]: executed while DevSpace deploys deployments. [name] can be replaced with the config name of a deployment or * to match all.
before:render, after:render, before:render:[name], after:render:[name], error:render:[name]: executed while DevSpace renders deployments during devspace render. [name] can be replaced with the config name of a deployment or * to match all.
before:purge, after:purge, before:purge:[name], after:purge:[name], error:purge:[name]: executed while DevSpace purges deployments during devspace purge. [name] can be replaced with the config name of a deployment or * to match all.
before:build, after:build, before:build:[name], after:build:[name], error:build:[name], skip:build:[name]: executed while DevSpace builds images. [name] can be replaced with the config name of an image or * to match all.
start:sync:[name], stop:sync:[name], error:sync:[name], restart:sync:[name], before:initialSync:[name], after:initialSync:[name], error:initialSync:[name]: executed while DevSpace syncs files with dev.sync. [name] can be replaced with the config name of a sync configuration or * to match all.
start:portForwarding:[name], restart:portForwarding:[name], error:portForwarding:[name], stop:portForwarding:[name]: executed while DevSpace port forwards with dev.ports. [name] can be replaced with the config name of a port forwarding configuration or * to match all.
start:reversePortForwarding:[name], restart:reversePortForwarding:[name], error:reversePortForwarding:[name], stop:reversePortForwarding:[name]: executed while DevSpace reverse port forwards with dev.ports. [name] can be replaced with the config name of a port forwarding configuration or * to match all.
before:createPullSecrets, after:createPullSecrets, error:createPullSecrets: executed while DevSpace creates pullSecrets
devCommand:before:execute, devCommand:after:execute, devCommand:error, devCommand:interrupt, devCommand:before:sync, devCommand:after:sync, devCommand:before:portForwarding, devCommand:after:portForwarding, devCommand:before:replacePods, devCommand:after:replacePods, devCommand:before:runPipeline, devCommand:after:runPipeline, devCommand:before:deployDependencies, devCommand:after:deployDependencies, devCommand:before:build, devCommand:after:build, devCommand:before:deploy, devCommand:after:deploy, devCommand:before:openTerminal, devCommand:before:streamLogs: executed at certain lifecycle events during the devspace dev command
deployCommand:before:execute, deployCommand:after:execute, deployCommand:error, deployCommand:interrupt executed at different checkpoints when devspace deploy is executed
purgeCommand:before:execute, purgeCommand:after:execute, purgeCommand:error, purgeCommand:interrupt executed at different checkpoints when devspace purge is executed
buildCommand:before:execute, buildCommand:after:execute, buildCommand:error, buildCommand:interrupt executed at different checkpoints when devspace build is executed
Wildcard and filter paths for patches:
It is now possible to use filter paths and wildcards in profile & pod patches. For example:
images:
backend:
image: john/devbackend
backend-debugger:
image: john/debugger
deployments:
name: backend
helm:
componentChart: true
values:
containers:
image: john/devbackend
image: john/debugger
profiles:
name: staging
patches:
op: replace
path: ..[?(@.image=='john/devbackend')].image
value: john/stagingbackend
op: remove
path: deployments..[?(@.image=='john/debugger')]
For more informations take a look at the docs.
Other Changes:
You can now use image(default) and tag(default) in hook commands and args:
images:
test:
image: test/test
hooks:
command: |-
./custom-script image(test):tag(test) # -> Transformed to ./custom-script test/test:#####
when:
after:
images: all
DevSpace will now use a replica set instead of single pod as pod replacement
DevSpace will now try to restart the terminal if a non-zero exit code occurred during devspace dev. Can be disabled via the flag --terminal-restart=false
New flag --restart for command devspace enter to restart the terminal if a non-zero exit code was encountered
New flag --image-selector for commands devspace enter, devspace logs & devspace attach
Fixed an issue where pathType was not automatically set for newer ingress versions
Fixed an issue where namespace and context were wrong in UI commands
Fixed an issue where replacing pods with the same image selector across different devspace.yaml would target the same pods (#1633)
Renamed plugin hook names to match config hook names
Fixed an issue where paths that include a symlink would not sync correctly

New in DevSpace 5.16.0 Beta 1 (Sep 20, 2021)

New in DevSpace 5.16.0 Alpha 0 (Sep 10, 2021)

New in DevSpace 5.15.0 (Sep 4, 2021)

New Features:
Flag --profile can now be used multiple times to apply several profiles, flag --profile-parent is now deprecated
New option profiles[*].activate to automatically activate profiles based on environment variables
Added a lot of new plugin hooks (see devspace docs for more information)
New global flag --disable-profile-activation to disable automatic activation of profiles
New option dependencies[*].disableProfileActivation for dependencies to disable automatic activation of profiles in dependencies
New dev.logs.selectors[*].imageSelector option to select images that should be logged by image name
New excludeFile, downloadExcludeFile, and uploadExclude options for loading exclude paths from files using .gitignore syntax (#1562)
DevSpace will now run remote hook commands in a remote shell if no args are specified. For example this is now possible:
hooks:
command: |
echo 123
echo 456
echo 789
where:
container:
imageSelector: my-image
when:
after:
deployments: all
New hooks[*].when.before.initialSync and hooks[*].when.after.initialSync that executes a hook after or before a certain sync configuration's initial sync has started
New option name for dev.sync and dev.ports. This can be used as a steady identifier when using profile patches or initial sync hooks. (#1577)
New option noCache for variables that disables caching of variable input
New option dependencies[*].dev.replacePods to enable replace pods from dependencies
New flag --skip-dependency for devspace build, devspace dev, devspace purge, devspace deploy & devspace render
New option commands[*].appendArgs to prevent DevSpace from automatically appending arguments to a command (#1598)
Fixes:
Fixed an issue where devspace sync would exit immediately after initial sync and hooks
Fixed an issue where updating the local init language repository could fail during devspace init
Fixed an issue where devspace sync --config ... would use the current directory as base path instead of the config directory
Fixed an issue where using relative paths for plugin installation would fail
Fixed an issue where the sync would skip to upload files initially that were newer on the remote side
Fixed a problem where DevSpace's helper would show devspace-restart-helper in log messages
Fixed an issue where the image selector would sometimes look wrong
Fixed an issue where the sync watcher would exclude paths if the initial stat of them has failed
Fixed an issue where DevSpace would get stuck uploading or downloading files that would change frequently (#1576)
Fixed an issue where http was hardcoded as target domain in DevSpace UI (#1574)
Fixed an issue where multiple devspace.yaml in the same folder would lead to unwanted shared caches
Fixed an issue where excluding files on linux operating systems would also exclude files for other sync paths (#1595)
Fixed an issue where log streaming would terminate unexpectedly (#1596)
Fixed an issue where using $@, $# or $0 etc. in commands would not work correctly (#1598)
Other:
Updated the ktunnel reverse port forwarding code
Improved waiting output of DevSpace running in a pipeline
Removed the color red from the log streaming color palette to avoid confusion with errors (#1583)
Sync will now compare crc32 hashes initially for files that might not be needed to get synced
Updated component chart to v0.8.1

New in DevSpace 5.15.0 Beta 4 (Sep 3, 2021)

New Features:
New option profiles[*].activate to automatically activate profiles based on environment variables
Added a lot of new plugin hooks (see devspace docs for more information)
New global flag --disable-profile-activation to disable automatic activation of profiles
New option dependencies[*].disableProfileActivation for dependencies to disable automatic activation of profiles in dependencies
New dev.logs.selectors[*].imageSelector option to select images that should be logged by image name
New excludeFile, downloadExcludeFile, and uploadExclude options for loading exclude paths from files using .gitignore syntax (#1562)
DevSpace will now run remote hook commands in a remote shell if no args are specified. For example this is now possible:
hooks:
command: |
echo 123
echo 456
echo 789
where:
container:
imageSelector: my-image
when:
after:
deployments: all
New hooks[*].when.before.initialSync and hooks[*].when.after.initialSync that executes a hook after or before a certain sync configuration's initial sync has started
New option name for dev.sync and dev.ports. This can be used as a steady identifier when using profile patches or initial sync hooks. (#1577)
New option noCache for variables that disables caching of variable input
New option dependencies[*].dev.replacePods to enable replace pods from dependencies
New flag --skip-dependency for devspace build, devspace dev, devspace purge, devspace deploy & devspace render
New option commands[*].appendArgs to prevent DevSpace from automatically appending arguments to a command (#1598)
Fixes:
Fixed an issue where devspace sync would exit immediately after initial sync and hooks
Fixed an issue where updating the local init language repository could fail during devspace init
Fixed an issue where devspace sync --config ... would use the current directory as base path instead of the config directory
Fixed an issue where using relative paths for plugin installation would fail
Fixed an issue where the sync would skip to upload files initially that were newer on the remote side
Fixed a problem where DevSpace's helper would show devspace-restart-helper in log messages
Fixed an issue where the image selector would sometimes look wrong
Fixed an issue where the sync watcher would exclude paths if the initial stat of them has failed
Fixed an issue where DevSpace would get stuck uploading or downloading files that would change frequently (#1576)
Fixed an issue where http was hardcoded as target domain in DevSpace UI (#1574)
Fixed an issue where multiple devspace.yaml in the same folder would lead to unwanted shared caches
Fixed an issue where excluding files on linux operating systems would also exclude files for other sync paths (#1595)
Fixed an issue where log streaming would terminate unexpectedly (#1596)
Fixed an issue where using $@, $# or $0 etc. in commands would not work correctly (#1598)
Other:
Updated the ktunnel reverse port forwarding code
Improved waiting output of DevSpace running in a pipeline
Removed the color red from the log streaming color palette to avoid confusion with errors (#1583)
Sync will now compare crc32 hashes initially for files that might not be needed to get synced
Updated component chart to v0.8.1

New in DevSpace 5.15.0 Beta 3 (Sep 1, 2021)

New Features:
New option profiles[*].activate to automatically activate profiles based on environment variables
New global flag --disable-profile-activation to disable automatic activation of profiles
New option dependencies[*].disableProfileActivation for dependencies to disable automatic activation of profiles in dependencies
New dev.logs.selectors[*].imageSelector option to select images that should be logged by image name
DevSpace will now run remote hook commands in a remote shell if no args are specified. For example this is now possible:
New hooks[*].when.before.initialSync and hooks[*].when.after.initialSync that executes a hook after or before a certain sync configuration's initial sync has started
New option name for dev.sync and dev.ports. This can be used as a steady identifier when using profile patches or initial sync hooks. (#1577)
New option noCache for variables that disables caching of variable input
New option dependencies[*].dev.replacePods to enable replace pods from dependencies
New flag --skip-dependency for devspace build, devspace dev, devspace purge, devspace deploy & devspace render
New option commands[*].appendArgs to prevent DevSpace from automatically appending arguments to a command (#1598)
Fixes:
Fixed an issue where devspace sync --config ... would use the current directory as base path instead of the config directory
Fixed an issue where using relative paths for plugin installation would fail
Fixed an issue where the sync would skip to upload files initially that were newer on the remote side
Fixed a problem where DevSpace's helper would show devspace-restart-helper in log messages
Fixed an issue where the image selector would sometimes look wrong
Fixed an issue where the sync watcher would exclude paths if the initial stat of them has failed
Fixed an issue where DevSpace would get stuck uploading or downloading files that would change frequently (#1576)
Fixed an issue where http was hardcoded as target domain in DevSpace UI (#1574)
Fixed an issue where multiple devspace.yaml in the same folder would lead to unwanted shared caches
Fixed an issue where excluding files on linux operating systems would also exclude files for other sync paths (#1595)
Fixed an issue where log streaming would terminate unexpectedly (#1596)
Fixed an issue where using $@, $# or $0 etc. in commands would not work correctly (#1598)
Other:
Improved waiting output of DevSpace running in a pipeline
Removed the color red from the log streaming color palette to avoid confusion with errors (#1583)
Sync will now compare crc32 hashes initially for files that might not be needed to get synced
Updated component chart to v0.8.1

New in DevSpace 5.15.0 Beta 2 (Aug 27, 2021)

New in DevSpace 5.15.0 Beta 1 (Aug 25, 2021)

New in DevSpace 5.14.4 (Jul 20, 2021)

New in DevSpace 5.14.4 Beta 3 (Jul 20, 2021)

New in DevSpace 5.14.4 Beta 2 (Jul 19, 2021)

New in DevSpace 5.14.4 Beta 1 (Jul 15, 2021)

New in DevSpace 5.14.4 Beta 0 (Jul 12, 2021)

New in DevSpace 5.14.3 (Jul 7, 2021)

New in DevSpace 5.14.3 Beta 1 (Jul 5, 2021)

New in DevSpace 5.14.3 Beta 0 (Jun 29, 2021)

New in DevSpace 5.14.2 (Jun 17, 2021)

New in DevSpace 5.14.1 (Jun 16, 2021)

New in DevSpace 5.14.1 Beta 2 (Jun 15, 2021)

New in DevSpace 5.14.1 Beta 1 (Jun 11, 2021)

New in DevSpace 5.14.1 Beta 0 (Jun 10, 2021)

New in DevSpace 5.14.0 (Jun 3, 2021)

Changes:
New require section that allows you to define certain requirements that must be met to use DevSpace for a project. This is useful for example if you want to ensure that all developers that use DevSpace in a project have a certain DevSpace version, specific plugins or commands installed (please take a look at the DevSpace documentation for more information). For example:
require:
Will require that at least DevSpace version 5.0.0 is installed but not higher than 6.0.0
devspace: '>= 5.0.0, < 6.0.0'
Will require that the loft plugin is installed in version 1.12.0
plugins:
name: loft
version: '1.12.0'
Will require that helm is installed with at least version 3.5.0
commands:
name: helm
versionArgs: ["version"]
versionRegEx: 'Version:"([^"]+)"'
version: '>= 3.5.0'
New option imageSelector for dev.sync, dev.ports, dev.terminal and dev.replacePods that allows you to select containers directly by their container image instead of specifying the config name as in imageName. This makes it easier for certain use cases as you can now omit the images section sometimes completely:
version: v1beta10
vars:
name: IMAGE
value: registry.com/production:latest
deployments:
name: my-chart
helm:
chart:
name: my-application
values:
image: ${IMAGE}
dev:
terminal:
imageSelector: ${IMAGE}
replacePods:
imageSelector: ${IMAGE}
replaceImage: registry.com/dev:latest
patches:
op: replace
path: spec.containers[0].workingDir
value: /app
op: replace
path: spec.containers[0].command
value: ["sleep"]
op: replace
path: spec.containers[0].args
value: ["9999999999"]
ports:
imageSelector: ${IMAGE}
forward:
port: 3000
sync:
imageSelector: ${IMAGE}
uploadExcludePaths:
node_modules
Removed the flag --show-logs in devspace render, devspace render will now show the log output by default. If you want to hide the log output please use devspace render --silent instead
devspace reset pods will now reset scaled down deployments, statefulsets & replicasets even though no resettable pod could be found
devspace init now uses imageSelector instead of imageName to generate a getting started configuration
DevSpace will now use the original tag (if there was one specified) during tag rewriting if the image was never built
DevSpace will now also delete the replaced pods created through dev.replacePods during devspace purge
Removed the wrong context / namespace warnings for devspace enter, devspace attach and devspace logs as these commands are usually used without a devspace.yaml and the warning can be confusing especially if used together with profiles
devspace update plugin will now allow you to install older plugin versions as well when --version is specified

New in DevSpace 5.14.0 Beta 2 (Jun 2, 2021)

New in DevSpace 5.14.0 Beta 1 (Jun 2, 2021)

New in DevSpace 5.14.0 Beta 0 (May 31, 2021)

New in DevSpace 5.13.1 Beta 0 (May 27, 2021)

New in DevSpace 5.13.0 (May 17, 2021)

New in DevSpace 5.13.0 Beta 1 (May 14, 2021)

New in DevSpace 5.13.0 Beta 0 (May 11, 2021)

New in DevSpace 5.12.2 (May 6, 2021)

New in DevSpace 5.12.2 Pre-release (May 5, 2021)

New in DevSpace 5.12.1 (Apr 24, 2021)

New in DevSpace 5.12.1 Beta 0 (Apr 22, 2021)

New in DevSpace 5.12.0 (Apr 21, 2021)

New Feature: Pod Replacing:
With dev.replacePods we introduced a new feature that gives you the option to exchange an already running or just deployed pod with a modified version. This is especially useful if you:
Need to configure or disable an option on a pod which is not configurable via your helm chart or manifests
Do not want to use DevSpace for your pipeline and instead only want to use DevSpace for development
Want to debug a setup with an already deployed app by exchanging a single pod temporarily with modifications
Dependency Changes:
With v5.12.0, we greatly improved dependencies and you are now able to reference dependency images and reuse dependency dev configuration. This makes it possible to create much more flexible pipelines and enables you to outsource parts of your devspace.yaml enterly.
For example, you can now reference dependency images in every imageName field via dependency1.image1. In deployment values, you can now use image(dependency1.image1):tag(dependency1.image1) to insert an image that was built within a dependency. You can even reference dependencies of dependencies via depdency1.dependency2.image1. You can also run a command of a dependency with devspace run dependency1.command now.
New Config Version v1beta10:
With the new config version v1beta10 we cleaned up some options that were now deprecated for a while (especially dev.interactive was changed). Older config versions will still continue to work as expected and there are no breaking changes as DevSpace will convert them automatically in memory, you can see how DevSpace translates your current config by running devspace print. We changed the following options with v1beta10:
Removed dev.interactive completely. We also removed all related documentation regarding interactive mode and encourage users to use dev.terminal instead, which opens a terminal without touching the Dockerfile and is much easier to understand. If you need to exchange the entrypoint of the container with DevSpace, we encourage you to use either images[*].entrypoint & images[*].cmd, set command & args in your deployment (if thats supported by your helm chart or manifests) or use the new feature dev.replacePods to modify the pod's spec.containers[*].command & spec.containers[*].args
New section dev.terminal which if set, will tell DevSpace to open a terminal by default instead of printing logs.
dev.sync[*].waitInitialSync is now true by default
Removed images[*].tagsAppendRandom & images[*].preferSyncOverRebuild
dependencies[*].name is now required (for older config versions, the array index will be used as dependency name)
New section dependencies[*].dev to specify which dev config should be reused from the dependency (currently only ports and sync are supported)
Removal of deprecated commands:
We removed the deprecated commands devspace add deployment, devspace add image, devspace add port, devspace add sync, devspace remove deployment, devspace remove image, devspace remove port, devspace remove sync, devspace status sync and devspace update config.
Other New Features:
You can now execute hooks or variables with source: command via the integrated golang shell. The advantage of this shell is that it works cross platform and you can use logical expressions such as echo 123 && echo 456. DevSpace will use the shell if no hooks[*].args or vars[*].args are provided and only a hooks[*].command or vars[*].command is configured.
New vars[*].value that is a shortcut for using vars[*].source: none and vars[*].default
New command devspace reset pods to reset changes made by dev.replacePods
New commands[*].args that if defined will execute the command directly instead of in a golang shell
The helpers image() and tag() that can be used within helm deployment values or kubectl manifests can now also be used to reference an image key in images.* or in a dependency. If naming of an image key name and the actual image collide, the image key has precedence.
New flag --all/-a for devspace purge to purge dependencies as well (the old flag --dependencies is now deprecated)
New predefined variable ${DEVSPACE_USER_HOME} that holds the user's home directory
OTHER CHANGES:
Completely refactored devspace init: more options to choose how you want to initialize your devspace.yaml. We also by default set dev.replacePods with dev.terminal now instead of configuring printing logs and reloading the container process.
profiles[*].patches and dev.replacePods[*].patches with op: replace patches do not fail if the target path does not exist anymore and behave like a op: add instead
profiles[*].patches and dev.replacePods[*].patches with op: remove patches do not fail if the target path does not exist anymore and do nothing instead
Fixed an issue where image build caching of dependencies was sometimes not working correctly
Fixed an issue where hooks[*].when.before.images was triggered even though the image was not built
Updated kaniko to v1.5.2
Updated internal kubernetes version to v1.20.4
Improvements to dependency execution and output

New in DevSpace 5.12.0 Alpha 0 (Apr 17, 2021)

New Feature: Pod Replacing:
With dev.replacePods we introduced a new feature that gives you the option to exchange an already running or just deployed pod with a modified version. This is especially useful if you:
Need to configure or disable an option on a pod which is not configurable via your helm chart or manifests
Do not want to use DevSpace for your pipeline and instead only want to use DevSpace for development
Want to debug a setup with an already deployed app by exchanging a single pod temporarily with modifications
For example:
version: v1beta10
deployments:
name: my-app
helm:
componentChart: true
values:
containers:
name: my-container
image: idonotexist:neverexisted # this will create a failing pod
dev:
DevSpace will try to find a pod with the given label selector. If found (even if its currently in a failed state)
DevSpace will copy the pod, scale down the owning ReplicaSet, Deployment or StatefulSet
and create the new modified pod in the cluster. (Reset via devspace reset pods)
replacePods:
labelSelector:
app.kubernetes.io/component: my-app
replaceImage: ubuntu:latest
patches:
op: add
path: spec.containers.name=my-container.command
value: ["sleep"]
op: add
path: spec.containers.name=my-container.args
value: ["9999999999"]
op: add
path: spec.containers.name=my-container.workingDir
value: "/workdir"
This will create a terminal to the replaced pod
terminal:
labelSelector:
app.kubernetes.io/component: my-app
This will sync to the replaced pod's working directory
sync:
labelSelector:
app.kubernetes.io/component: my-app
For more informations take a look at the devspace docs
Dependency Changes:
With v5.12.0, we greatly improved dependencies and you are now able to reference dependency images and reuse dependency dev configuration. This makes it possible to create much more flexible pipelines and enables you to outsource parts of your devspace.yaml enterly.
For example, you can now reference dependency images in every imageName field via dependency1.image1. In deployment values, you can now use imageName(dependency1.image1) to insert an image that was built within a dependency. You can even reference dependencies of dependencies via depdency1.dependency2.image1. You can also run a command of a dependency with devspace run dependency1.command now.
For example ./devspace.yaml:
version: v1beta10
dependencies:
name: dep1
source:
path: ./dep1
dev:
ports: true
deployments:
name: quickstart
helm:
componentChart: true
values:
containers:
image: imageName(dep1.image1)
dev:
Will open a terminal to the pod with the
image from dep1
terminal:
imageName: dep1.image1
Then the dependency ./dep1/devspace.yaml could look like this:
version: v1beta10
images:
image1:
image: myrepo/image
dev:
ports:
imageName: image1
forward:
port: 3000
This makes it a lot easier to divide your devspace.yaml into multiple parts or to build a much complexer pipeline with multiple build and deploy steps.
For more informations take a look at the devspace docs
New Config Version v1beta10:
With the new config version v1beta10 we cleaned up some options that were now deprecated for a while (especially dev.interactive was changed). Older config versions will still continue to work as expected and there are no breaking changes as DevSpace will convert them automatically in memory, you can see how DevSpace translates your current config by running devspace print. We changed the following options with v1beta10:
Removed dev.interactive completely. We also removed all related documentation regarding interactive mode and encourage users to use dev.terminal instead, which opens a terminal without touching the Dockerfile and is much easier to understand. If you need to exchange the entrypoint of the container with DevSpace, we encourage you to use either images[*].entrypoint & images[*].cmd, set command & args in your deployment (if thats supported by your helm chart or manifests) or use the new feature dev.replacePods to modify the pod's spec.containers[*].command & spec.containers[*].args
New section dev.terminal which if set, will tell DevSpace to open a terminal by default instead of printing logs.
dev.sync[*].waitInitialSync is now true by default
Removed images[*].tagsAppendRandom & images[*].preferSyncOverRebuild
dependencies[*].name is now required (for older config versions, the array index will be used as dependency name)
New section dependencies[*].dev to specify which dev config should be reused from the dependency (currently only ports and sync are supported)
Removal of deprecated commands:
We removed the deprecated commands devspace add deployment, devspace add image, devspace add port, devspace add sync, devspace remove deployment, devspace remove image, devspace remove port, devspace remove sync, devspace status sync and devspace update config.
Other New Features:
You can now execute hooks or variables with source: command via the integrated golang shell. The advantage of this shell is that it works cross platform and you can use logical expressions such as echo 123 && echo 456. DevSpace will use the shell if no hooks[*].args or vars[*].args are provided and only a hooks[*].command or vars[*].command is configured:
vars:
name: MY_VAR_FROM_SHELL
command: "echo value"
name: MY_VAR_DIRECT
command: "echo"
args: ["value"]
hooks:
command: "echo 123 && echo 456"
when:
before:
images: all
New vars[*].value that is a shortcut for using vars[*].source: none and vars[*].default
New command devspace reset pods to reset changes made by dev.replacePods
New commands[*].args that if defined will execute the command directly instead of in a golang shell
New helpers imageName(), imageNameImage() and imageNameTag() that can be used within helm deployment values or kubectl manifests to reference an image defined in images or in a dependency
New flag --all/-a for devspace purge to purge dependencies as well (the old flag --dependencies is now deprecated)
New predefined variable ${DEVSPACE_USER_HOME} that holds the user's home directory
Other Changes:
Fixed an issue where image build caching of dependencies was sometimes not working correctly
Fixed an issue where hooks[*].when.before.images was triggered even though the image was not built
Updated kaniko to v1.5.2
Updated internal kubernetes version to v1.20.4
Improvements to dependency execution and output

New in DevSpace 5.11.0 (Apr 9, 2021)

New in DevSpace 5.11.0 Beta 1 (Apr 8, 2021)

New in DevSpace 5.11.0 Beta 0 (Apr 7, 2021)

New in DevSpace 5.10.0 (Mar 27, 2021)

Deprecation:
Deprecation of commands devspace add deployment, devspace add image, devspace add port, devspace add sync, devspace remove deployment, devspace remove image, devspace remove port, devspace remove sync, devspace status sync and devspace update config. We feel these commands are rarely used, mostly outdated in terms of config options and are an increasing maintenance burden. The commands are still available, however DevSpace will now print a warning if you use them. The commands will be removed in a future DevSpace version.
New Features:
DevSpace now allows you to specify variables within other variables default values, which makes it possible to compose variables of other variables. To use a variable in a default value, the variable that is used needs to be specified prior or needs to be a predefined variable. For example:
version: v1beta9
images:
default:
image: ${IMAGE}
vars:
name: IMAGE_REPOSITORY
default: myrepository
source: none
name: IMAGE_NAME
default: devspace
source: none
name: IMAGE
default: ${IMAGE_REPOSITORY}/${IMAGE_NAME}
source: none
name: NAMESPACE
default: ${DEVSPACE_NAMESPACE}
source: none
New option images.*.rebuildStrategy that can either take always or ignoreContextChanges to specify when DevSpace should rebuild an image (#1353)
New flag --max-concurrent-builds that limits the amount of concurrent image during devspace build, devspace dev, devspace render or devspace deploy (#1347)
New option images.*.build.kaniko.envFrom that allows you to specify environment variables from a config map or secret for the kaniko build pod (#1348)
Added support for devspace.dockerignore that will take precedence over a regular .dockerignore during image build (#1356)
New --output flag for devspace list vars that accepts the values keyvalue or json
New --overwrite flag for devspace set var that if set to false will not overwrite the variable when found in cache
Other Changes:
Flags such as --sequential-build, --max-concurrent-builds and --skip-push-local-kube will now also apply to dependency builds
Fixed an issue where devspace set var would fail with base64 encoded strings
Fixed an issue where a nil pointer could occur if using a hooks.when.after.purgeDeployments hook (#1361)
DevSpace will now not return a fatal error if devspace update plugin cannot update the plugin because it is the newest version (#1352)
devspace list vars will now print all resolved variables of the current applied config instead of only all cached variables

New in DevSpace 5.10.0 Beta 2 (Mar 26, 2021)

New in DevSpace 5.10.0 Beta 1 (Mar 26, 2021)

Deprecation:
Deprecation of commands devspace add deployment, devspace add image, devspace add port, devspace add sync, devspace remove deployment, devspace remove image, devspace remove port, devspace remove sync, devspace status sync and devspace update config. We feel these commands are rarely used, mostly outdated in terms of config options and are an increasing maintenance burden. The commands are still available, however DevSpace will now print a warning if you use them. The commands will be removed in a future DevSpace version.
New Features:
DevSpace now allows you to specify variables within other variables default values, which makes it possible to compose variables of other variables. To use a variable in a default value, the variable that is used needs to be specified prior or needs to be a predefined variable. For example:
version: v1beta9
images:
default:
image: ${IMAGE}
vars:
name: IMAGE_REPOSITORY
default: myrepository
source: none
name: IMAGE_NAME
default: devspace
source: none
name: IMAGE
default: ${IMAGE_REPOSITORY}/${IMAGE_NAME}
source: none
name: NAMESPACE
default: ${DEVSPACE_NAMESPACE}
source: none
New option images.*.rebuildStrategy that can either take always or ignoreContextChanges to specify when DevSpace should rebuild an image (#1353)
New flag --max-concurrent-builds that limits the amount of concurrent image during devspace build, devspace dev, devspace render or devspace deploy (#1347)
New option images.*.build.kaniko.envFrom that allows you to specify environment variables from a config map or secret for the kaniko build pod (#1348)
Added support for devspace.dockerignore that will take precedence over a regular .dockerignore during image build (#1356)
New --output flag for devspace list vars that accepts the values keyvalue or json
New --overwrite flag for devspace set var that if set to false will not overwrite the variable when found in cache
Other Changes:
Flags such as --sequential-build, --max-concurrent-builds and --skip-push-local-kube will now also apply to dependency builds
Fixed an issue where devspace set var would fail with base64 encoded strings
Fixed an issue where a nil pointer could occur if using a hooks.when.after.purgeDeployments hook (#1361)
DevSpace will now not return a fatal error if devspace update plugin cannot update the plugin because it is the newest version (#1352)
devspace list vars will now print all resolved variables of the current applied config instead of only all cached variables

New in DevSpace 5.9.0 Pre-release (Mar 15, 2021)

New in DevSpace 5.9.0 Beta 1 (Mar 12, 2021)

New in DevSpace 5.9.0 Beta 0 (Mar 12, 2021)

New in DevSpace 5.8.4 (Mar 8, 2021)

New in DevSpace 5.8.3 Beta 0 (Mar 5, 2021)

New in DevSpace 5.8.2 Beta 0 (Mar 1, 2021)

New in DevSpace 5.8.1 (Feb 24, 2021)

New in DevSpace 5.8.1 Beta 0 (Feb 19, 2021)

New in DevSpace 5.8.0 (Feb 17, 2021)

New in DevSpace 5.7.6 (Feb 12, 2021)

New in DevSpace 5.7.5 Pre-release (Feb 2, 2021)

New in DevSpace 5.7.5 Alpha 0 (Jan 27, 2021)

New in DevSpace 5.7.4 (Jan 25, 2021)

New in DevSpace 5.7.3 (Jan 22, 2021)

New in DevSpace 5.7.2 Pre-release (Jan 22, 2021)

New in DevSpace 5.7.2 Alpha 0 (Jan 16, 2021)

New in DevSpace 5.7.1 (Jan 12, 2021)

New Features:
New flag --parent-profile to apply multiple profiles with flags:
Applies the profiles profile1, profile2, profile3 and profile4 in this order
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3 --profile=profile4
You can also leave out the --profile flag and only the profiles
profile1, profile2 and profile3 are appied
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3
New options upload and download for hooks to upload or download files from a container:
hooks:
Upload the complete local bin folder to the container path ./bin
upload:
localPath: bin
containerPath: bin
where:
container:
imageName: default
when:
after:
deployments: deployment-1
Download a single file from the container to the local path
download:
localPath: build/artifact.jar
containerPath: build/artifact-test.jar
where:
container:
imageName: java
when:
after:
deployments: deployment-2
New predefined variable ${DEVSPACE_VERSION}
New options hooks.when.before.purgeDeployments, hooks.when.after.purgeDeployments andhooks.when.onError.purgeDeployments to execute hooks on devspace purge
New option dev.interactive.terminal.workDir to specify a working directory to open the terminal in
New flag --workdir for devspace enter and devspace dev to specify a working directory to open the terminal in or execute a command in
Other:
Profiles can now be used to change the commands section. It is now possible to have commands that are only available or change with specific profiles. A profile can be used with devspace run by supplying the flag before the run: devspace --profile my-special-command-profile run profile-command
Removed several options in devspace init that would lead to an incomplete devspace.yaml
The flags --save-vars and --restore-vars are now global
Fixed an issue where replacing certain fields with profiles.replace would lead to a yaml error
Fixed an issue where deployment within a cluster kube-context was not possible
Fixed an issue where the namespace was wrong when executing devspace within a cluster
Fixed a potential race during initial sync upload
Fixed a potential endless loop during initial sync if upstream was disabled

New in DevSpace 5.7.1 Beta 0 (Jan 11, 2021)

New Features:
New predefined variable ${DEVSPACE_VERSION}
New options hooks.when.before.purgeDeployments, hooks.when.after.purgeDeployments andhooks.when.onError.purgeDeployments to execute hooks on devspace purge
New option dev.interactive.terminal.workDir to specify a working directory to open the terminal in
New flag --workdir for devspace enter and devspace dev to specify a working directory to open the terminal in or execute a command in
New flag --parent-profile to apply multiple profiles with flags:
# Applies the profiles profile1, profile2, profile3 and profile4 in this order
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3 --profile=profile4
# You can also leave out the --profile flag and only the profiles
# profile1, profile2 and profile3 are appied
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3
New options upload and download for hooks to upload or download files from a container:
hooks:
# Upload the complete local bin folder to the container path ./bin
- upload:
localPath: bin
containerPath: bin
where:
container:
imageName: default
when:
after:
deployments: deployment-1
# Download a single file from the container to the local path
- download:
localPath: build/artifact.jar
containerPath: build/artifact-test.jar
where:
container:
imageName: java
when:
after:
deployments: deployment-2
Other:
Profiles can now be used to change the commands section. It is now possible to have commands that are only available or change with specific profiles. A profile can be used with devspace run by supplying the flag before the run: devspace --profile my-special-command-profile run profile-command
Removed several options in devspace init that would lead to an incomplete devspace.yaml
The flags --save-vars and --restore-vars are now global
Fixed an issue where replacing certain fields with profiles.replace would lead to a yaml error
Fixed an issue where deployment within a cluster kube-context was not possible
Fixed an issue where the namespace was wrong when executing devspace within a cluster
Fixed a potential race during initial sync upload
Fixed a potential endless loop during initial sync if upstream was disabled

New in DevSpace 5.7.0 Beta 2 (Jan 9, 2021)

New Features:
New flag --parent-profile to apply multiple profiles with flags:
Applies the profiles profile1, profile2, profile3 and profile4 in this order
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3 --profile=profile4
You can also leave out the --profile flag and only the profiles
profile1, profile2 and profile3 are appied
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3
New options upload and download for hooks to upload or download files from a container:
hooks:
Upload the complete local bin folder to the container path ./bin
upload:
localPath: bin
containerPath: bin
where:
container:
imageName: default
when:
after:
deployments: deployment-1
Download a single file from the container to the local path
download:
localPath: build/artifact.jar
containerPath: build/artifact-test.jar
where:
container:
imageName: java
when:
after:
deployments: deployment-2
New predefined variable ${DEVSPACE_VERSION}
New options hooks.when.before.purgeDeployments, hooks.when.after.purgeDeployments andhooks.when.onError.purgeDeployments to execute hooks on devspace purge
New option dev.interactive.terminal.workDir to specify a working directory to open the terminal in
New flag --workdir for devspace enter and devspace dev to specify a working directory to open the terminal in or execute an command in
Other:
Profiles can now be used to change the commands section. It is now possible to have commands that are only available or change with specific profiles. A profile can be used with devspace run by supplying the flag before the run: devspace --profile my-special-command-profile run profile-command
Removed several options in devspace init that would lead to an incomplete devspace.yaml
The flags --save-vars and --restore-vars are now global
Fixed an issue where replacing certain fields with profiles.replace would lead to an yaml error
Fixed an issue where deployment within an cluster kube context was not possible
Fixed an issue where the namespace was wrong when executing devspace within a cluster
Fixed a potential race during initial sync upload

New in DevSpace 5.7.0 Beta 1 (Jan 7, 2021)

New in DevSpace 5.7.0 Beta 0 (Jan 5, 2021)

New in DevSpace 5.6.5 (Jan 5, 2021)

New in DevSpace 5.6.5 Pre-release (Jan 4, 2021)

New in DevSpace 5.6.4 (Dec 21, 2020)

New in DevSpace 5.6.3 (Dec 18, 2020)

New in DevSpace 5.6.2 (Dec 17, 2020)

New in DevSpace 5.6.1 (Dec 15, 2020)

New in DevSpace 5.6.1 Beta 0 (Dec 15, 2020)

New in DevSpace 5.6.0 (Dec 15, 2020)

New in DevSpace 5.6.0 Beta 1 (Dec 15, 2020)

New Features:
DevSpace will now replace '#' in image tags with random characters, which gives you more freedom to specify image tags with random components (#1188):
images:
app:
tags:
Each single hashtag will be replaced with a random character
my-###-latest
${DEVSPACE_GIT_BRANCH}-#####
${USER}-#####
'############'
DevSpace now allows you to specify tag(registry/repo/image) and image(registry/repo/image) in helm values to only insert a tag or the image name without any modification. This is useful for helm charts that split image and tag (#1188):
images:
default:
image: registry/repo/image
tags:
random-#####
deployments:
name: my-deployment
helm:
chart: ...
values:
Will be replaced by devspace to -> imageWithTag: registry/repo/image:random-xAhgW
imageWithTag: registry/repo/image
Will be replaced by devspace to -> image: registry/repo/image
image: image(registry/repo/image)
Will be replaced by devspace to -> tag: random-xAhgW
tag: tag(registry/repo/image)
New dev.logs.selectors option that allows you to specify additional label selectors to select pods you want to stream logs from:
images:
default:
image: registry/repo/image
dev:
logs:
images:
Selects all pods that use the image default (registry/repo/image)
default
selectors:
Selects all pods with the given label selector and streams the logs to the console
labelSelector:
abc: def
container: optional
namespace: optional
Hooks can now be executed in a container by specifying hooks.*.where.container:
...
hooks:
command: "echo"
args: ["Hello from within the container!"]
where:
container:
imageName: default
Or select via labelSelector etc.
labelSelector: ...
when:
after:
deployments: my-deployment
...
Hooks for images can now be specified for specific images instead of only "all":
images:
image-1:
image: registry/repo/image
image-2:
image: registry/repo/image
hooks:
command: "echo"
args: ["before", "all"]
when:
before:
images: all
command: "echo"
args: ["before", "image-1"]
when:
before:
images: image-1
command: "echo"
args: ["before", "image-2"]
when:
before:
images: image-2
New flags --container, --pod, --label-selector and --pick for command devspace restart
New config option hooks.*.background and hooks.*.silent to execute hooks without output or in the background.
Other Changes:
log streaming was greatly improved and should now automatically reconnect and recognize new upcoming pods that match the specified selectors. (#1149)
The sync output is now merged by default with the log output to make it clearer what DevSpace is doing in the background. You can disable this new behaviour and restore the old by specifying dev.logs.sync: false in the devspace.yaml
Improved the way DevSpace will select pods and containers for sync, port-forwarding and terminal
Updated the internal kubectl and helm versions that will be downloaded if there couldn't be any found in the PATH.
Fixed an issue where dev.autoReload.deployments would not correctly watch for changes to manifest folders and values files (#1255)
Fixed an issue where devspace init would create a failing devspace.yaml if the Dockerfile was missing ENTRYPOINT and CMD (#1252)
Fixed an issue where switching the profile would not redeploy, if it was deployed before with another profile
Fixed an issue on older windows systems where the terminal output was corrupted.
Fixed an issue where some .dockerignore statements were not correctly working with kaniko builder

New in DevSpace 5.6.0 Beta 0 (Dec 11, 2020)

New in DevSpace 5.5.0 (Dec 9, 2020)

New in DevSpace 5.4.1 (Nov 30, 2020)

New in DevSpace 5.4.0 (Nov 28, 2020)

New in DevSpace 5.4.0 Beta 0 (Nov 25, 2020)

New in DevSpace 5.3.0 Pre-release (Nov 20, 2020)

New in DevSpace 5.3.0 Beta 0 (Nov 18, 2020)

New in DevSpace 5.2.2 (Nov 10, 2020)

New in DevSpace 5.2.2 Beta 0 (Nov 10, 2020)

New in DevSpace 5.2.1 (Nov 7, 2020)

New in DevSpace 5.2.1 Pre-release (Nov 6, 2020)

New in DevSpace 5.2.0 (Oct 24, 2020)

New in DevSpace 5.1.2 (Oct 14, 2020)

New in DevSpace 5.1.1 (Oct 13, 2020)

New in DevSpace 5.1.0 (Oct 2, 2020)

New in DevSpace 5.0.3 (Sep 8, 2020)

New in DevSpace 5.0.2 (Aug 11, 2020)

New in DevSpace 5.0.2 Dev (Aug 10, 2020)

New in DevSpace 5.0.1 (Aug 10, 2020)

New in DevSpace 5.0.0 (Aug 6, 2020)

New in DevSpace 5.0.0 Beta 0 (Jul 30, 2020)

New in DevSpace 4.14.0 (Jul 17, 2020)

New in DevSpace 4.14.0 Pre-release (Jul 16, 2020)

New in DevSpace 4.13.1 Pre-release (Jul 1, 2020)

New in DevSpace 4.13.0 (Jun 20, 2020)

New in DevSpace 4.13.0 Beta 1 (Jun 19, 2020)

New in DevSpace 4.12.5 (May 17, 2020)

New in DevSpace 4.12.3 (May 12, 2020)

New in DevSpace 4.12.2 (Apr 23, 2020)

New in DevSpace 4.12.1 (Apr 18, 2020)

New in DevSpace 4.12.1 Pre-release (Apr 17, 2020)

New in DevSpace 4.12.0 (Apr 16, 2020)

New in DevSpace 4.12.0 Beta 1 (Apr 15, 2020)

New in DevSpace 4.11.1 (Apr 8, 2020)

New in DevSpace 4.11.0 Beta 2 (Apr 7, 2020)

New in DevSpace 4.11.0 Beta 1 (Apr 6, 2020)

Automatic Container Restart:
In compiled programming languages such as golang it is cumbersome to build a container that is able to automatically reload on a file change. With v4.11.0 and config version v1beta9, DevSpace is able to do the heavy lifting for you and simplifies the process drastically in a non invasive way. You only have to set 2 config options in the devspace.yaml and it should work for most Dockerfiles and applications out of the box.
Other Changes:
New config version v1beta9 (old config versions will get converted in memory automatically as always):
new images.*.injectRestartHelper: if this option is true DevSpace injects a small restart script into the container and wraps the entrypoint of that container with this script, so DevSpace is able to restart the main container process during the sync process. Only works if there is either an Entrypoint defined in the DevSpace config or in the dockerfile for this image, otherwise DevSpace will fail. See Container Restart above for more information.
new dev.sync.*.onUpload.restartContainer: if this option is true DevSpace will try to restart the container main process after a change has been made. Only works if images.*.injectRestartHelper is enabled for the container that should be restarted or the devspace-restart-helper script is present in the container root folder. See Container Restart above for more information.
new dev.sync.*.onUpload.execRemote.onBatch: executes the given command after a batch of changes has been processed. DevSpace will wait for the command to finish and then will continue execution. This is useful for commands that shouldn't be executed after every single change that may take a little bit longer like recompiling etc.
new images.*.preferSyncOverRebuild: if enabled, DevSpace will not rebuild the image even though files have changed within the building context if a syncpath for this image is defined. Since this was the default behavior for all images before this change, older config versions will convert this to be enabled so that this is a non breaking change.
DevSpace now prefers docker over kaniko if both are set in the config

New in DevSpace 4.10.0 Pre-release (Apr 3, 2020)

New in DevSpace 4.9.4 (Apr 2, 2020)

New in DevSpace 4.9.3 (Apr 1, 2020)

New in DevSpace 4.9.3 Beta 1 (Apr 1, 2020)

New in DevSpace 4.9.1 (Mar 28, 2020)

New in DevSpace 4.9.0 (Mar 27, 2020)

New in DevSpace 4.8.0 (Mar 23, 2020)

New in DevSpace 4.8.0 Beta 1 (Mar 20, 2020)

New in DevSpace 4.7.0 (Mar 18, 2020)

New in DevSpace 4.6.2 (Mar 13, 2020)

New in DevSpace 4.6.1 (Mar 4, 2020)

New in DevSpace 4.6.0 (Mar 4, 2020)

New Features:
Profile Inheritance: introduced a new option profiles.*.parent that specifies a parent profile that is applied before the actual specified profile. This allows you to specify base profiles that contain common patches or replacements and reduce profile boilerplate (#862)
New config version v1beta7:
like always, DevSpace will automatically convert old config versions up to v1beta7 in memory
dev.sync.downloadOnInitialSync is removed in favor of dev.sync.initalSync which specifies one of the following initialSync strategies (#903):
mirrorLocal (default): will upload all missing files in the container and delete all files that are not present locally
mirrorRemote: will download all missing files locally and delete all files locally that are not present in the container
preferLocal: will not delete any files, but download and upload missing files and if a file exists on both sides prefer the local file if they differ
preferRemote: same as preferLocal but the remote file takes precedence
preferNewest: will not delete any files, but download and upload missing files and if a file exists on both sides prefer the newer one
keepAll: will not delete any files, but download and upload missing files and leave files that exist in both places untouched
images.tag is renamed to images.tags to allow multiple tags to be specified (#972)
New option for vars.source none, that can only be filled from the default value (#951)
devspace sync: new flag --initial-sync that takes an initialSync strategy as argument. The flag --download-on-initial-sync has been deprecated.
devspace build: the flag --tag can be now applied multiple times, which results in multiple tags built & pushed for the given images
devspace dev/deploy: new --wait and --timeout flag that will wait after deploying for all pods to become ready in the namespace (#954)
devspace analyze: new --patient flag that will ignore errors until the given timeout is reached or return when no problems were found (#954)
New deployments.*.helm.path option that specifies where the v2 cli can be found
Changes:
Deploying with helm v2 now will download the helm cli automatically (if no v2 binary is found in the path) and deploy through the cli instead of an integrated version in DevSpace (#971)
devspace build/dev/deploy: since this caused a lot of confusion, --force-dependencies is now defaulting to true
Updated helm version to v3.1.1
Updated kubernetes version to v1.17.2
Updated kaniko version to v0.17.1
Fixes:
Fixes a nil pointer in devspace use namespace that occured if the kube config couldn't be loaded correctly (#961)
Fixes an issue where devspace purge --dependency could hang (#964)
Improved the error message when a question couldn't be asked due to the logger being silenced (#975)

New in DevSpace 4.6.0 Pre-release (Mar 3, 2020)

NEW FEATURES:
Profile Inheritance: introduced a new option profiles.*.parent that specifies a parent profile that is applied before the actual specified profile. This allows you to specify base profiles that contain common patches or replacements and reduce profile boilerplate (#862)
New config version v1beta7:
like always, DevSpace will automatically convert old config versions up to v1beta7 in memory
dev.sync.downloadOnInitialSync is removed in favor of dev.sync.initalSync which specifies one of the following initialSync strategies (#903):
mirrorLocal (default): will upload all missing files in the container and delete all files that are not present locally
mirrorRemote: will download all missing files locally and delete all files locally that are not present in the container
preferLocal: will not delete any files, but download and upload missing files and if a file exists on both sides prefer the local file if they differ
preferRemote: same as preferLocal but the remote file takes precedence
preferNewest: will not delete any files, but download and upload missing files and if a file exists on both sides prefer the newer one
keepAll: will not delete any files, but download and upload missing files and leave files that exist in both places untouched
images.tag is renamed to images.tags to allow multiple tags to be specified (#972)
New option for vars.source none, that can only be filled from the default value (#951)
devspace sync: new flag --initial-sync that takes an initialSync strategy as argument. The flag --download-on-initial-sync has been deprecated.
devspace build: the flag --tag can be now applied multiple times, which results in multiple tags built & pushed for the given images
devspace dev/deploy: new --wait and --timeout flag that will wait after deploying for all pods to become ready in the namespace (#954)
devspace analyze: new --patient flag that will ignore errors until the given timeout is reached or return when no problems were found (#954)
New deployments.*.helm.path option that specifies where the v2 cli can be found
CHANGES:
Deploying with helm v2 now will download the helm cli automatically (if no v2 binary is found in the path) and deploy through the cli instead of an integrated version in DevSpace (#971)
devspace build/dev/deploy: since this caused a lot of confusion, --force-dependencies is now defaulting to true
Updated helm version to v3.1.1
Updated kubernetes version to v1.17.2
Updated kaniko version to v0.17.1
FIXES:
Fixes a nil pointer in devspace use namespace that occured if the kube config couldn't be loaded correctly (#961)
Fixes an issue where devspace purge --dependency could hang (#964)
Improved the error message when a question couldn't be asked due to the logger being silenced (#975)

New in DevSpace 4.5.4 (Feb 20, 2020)

New in DevSpace 4.5.3 (Feb 18, 2020)

New in DevSpace 4.5.2 (Feb 14, 2020)

New in DevSpace 4.5.0 (Jan 30, 2020)

New in DevSpace 4.4.0 (Jan 21, 2020)

New in DevSpace 4.3.4 (Dec 18, 2019)

New in DevSpace 4.3.2 (Dec 13, 2019)

New in DevSpace 4.3.2 Pre-release (Dec 3, 2019)

New in DevSpace 4.3.1 (Nov 28, 2019)

New in DevSpace 4.3.0 (Nov 26, 2019)

New in DevSpace 4.2.1 (Nov 12, 2019)

New in DevSpace 4.2.0 (Nov 8, 2019)

New in DevSpace 4.2.0 Beta 1 (Oct 29, 2019)

New in DevSpace 4.1.3 (Oct 22, 2019)

New in DevSpace 4.1.2 (Oct 22, 2019)

New in DevSpace 4.1.1 (Oct 22, 2019)

New in DevSpace 4.1.0 Pre-release (Oct 18, 2019)

New in DevSpace 4.0.4 (Oct 11, 2019)

New in DevSpace 4.0.3 (Oct 1, 2019)

New in DevSpace 4.0.2 (Sep 24, 2019)

New in DevSpace 4.0.1 (Sep 19, 2019)

New in DevSpace 4.0.0 RC2 (Sep 13, 2019)

Removed devspace-configs.yaml:
Profiles instead of multiple configs: We reworked how multiple configs in devspace are handled because we felt that it was currently too complicated and inflexible. Instead of creating a separate file besides devspace.yaml, you can now define different 'profiles' directly in the devspace.yaml instead of having different configs (see profiles).
Config patches instead of overrides: We removed the config override mechanism. Instead of overriding the config in the old way, you are now able to either completely replace parts of the config (the top level keys like images,deployments etc.) or patch specific fields in the config by providing 1) a jsonpath or xpath to the config option, 2) an operation (replace, add, remove) and 3) a value. We believe this gives the user more power of how values can be overridden (especially for alterations of arrays). At the same time, patches seem easier to use and understand than the previous override system although they might require more lines of config.
Other breaking changes:
Removed the config option cluster.kubeContext and cluster.namespace since this caused some confusion which kube-context and namespace were used during deployment. Instead DevSpace will now always use the current kube-context (or the context passed via the --kube-context flag) and remember the most recently used kube-context and namespace. If the user starts the deployment process using devspace dev or devspace deploy, DevSpace will print a warning if the current kube-context is different than the previously used one and wait a couple of seconds to give the user the chance to abort the command and prevent that the user accidentally deploys to the wrong cluster or namespace.
Removed devspace install since this command is no longer needed
Renamed devspace use/list config(s) into devspace use/list profile(s)
Removed devspace add/list/remove selector
devspace dev will not rebuild images if there were changes in the image context path
The shortcut flag for --pick -p was removed. -p is not used as --profile shortcut flag
The config option dev.overrideImages.dockerfile and dev.overrideImages.context were removed. dev.overrideImages was renamed to dev.interactive. The config will be automatically converted via devspace update config
New Features:
New config version v1beta3 (run devspace update config to convert your current config automatically)
Shared commands: The idea of shared commands is that the more experienced developers on your team define a set of useful commands and store them in the devspace.yaml, commit and push this config to the code repository via git and then, let other team mates run them without having to remember all the details or having to read through endless pages of internal workflow documentation.
Profiles: you are now able to specify multiple profiles in devspace.yaml and switch between those profiles via the devspace use profile command or the --profile / -p flag. See multiple profiles for an example how to use profiles.
Config Patches: you are now able to specify config patches in profiles to override certain parts of the config (see multiple profiles for an example). This makes it easy to reuse most of the config and exchange only small parts.
devspace dev is now able to log multiple pods to the console. To enable this behavior by default strip the config option dev.interactive from your devspace.yaml.
Interactive mode: when using devspace dev -i you can choose an image which should be started in interactive mode. This means that the image entrypoint will be overriden by a sleep command and a terminal to that image will be openend. Interactive mode can be configured as default to mimic old behaviour with the config option dev.interactive.enabled and dev.interactive.images. dev.terminal was moved to dev.interactive.terminal.
New config option dev.sync[*].imageName and dev.sync[*].imageName as an alternative to labelSelector. With imageName DevSpace will automatically find the pods in which the image is used and start sync or port-forwarding. For a working example take a look at quickstart
New config option dev.open: you can DevSpace now automatically open the browser to a certain webpage like http://localhost:8080.
New command devspace use context to switch the current kube-context and devspace use namespace to switch the current configured default namespace in the kube-context
New command devspace attach that allows users to attach to a specific pod and container (behaves like kubectl attach but has a picker to select pods)
New flag --verbose-dependencies in devspace dev/deploy/purge/build to print the output of dependency deployment
New config option dev.logs: you can specify if DevSpace should display image logs on devspace dev and what images should be logged
New config option images[*].entrypoint & images[*].cmd which allows you to specify an entrypoint and cmd that will be used during deployment (also works with multi stage build)
New config option deployments[*].kubectl.replaceImageTags, deployments[*].helm.replaceImageTags & deployments[*].component.options.replaceImageTags to prevent automatic replacement of image tags for deployments
Changes & Fixes:
Renamed config option dependencies[*].config into dependencies[*].profile
Removed config option dev.selectors (will be converted automatically), use imageName where possible instead
Removed config options .selector and --selector flags, use imageName where possible instead
Fixed issue in dependency resolving where dependency variables were not correctly used
Show warning if current built tag is the same as last built tag
Overriding image entrypoints now also works with multi staged builds
DevSpace now prefers the git cli for git dependencies if the cli is installed locally

New in DevSpace 4.0.0 Beta 2 (Sep 10, 2019)

Removed devspace-configs.yaml:
Profiles instead of multiple configs: We reworked how multiple configs in devspace are handled because we felt that it was currently too complicated and inflexible. Instead of creating a separate file besides devspace.yaml, you can now define different 'profiles' directly in the devspace.yaml instead of having different configs (see profiles).
Config patches instead of overrides: We removed the config override mechanism. Instead of overriding the config in the old way, you are now able to either completely replace parts of the config (the top level keys like images,deployments etc.) or patch specific fields in the config by providing 1) a jsonpath or xpath to the config option, 2) an operation (replace, add, remove) and 3) a value. We believe this gives the user more power of how values can be overridden (especially for alterations of arrays). At the same time, patches seem easier to use and understand than the previous override system although they might require more lines of config.
Other breaking changes:
Removed the config option cluster.kubeContext and cluster.namespace since this caused some confusion which kube-context and namespace were used during deployment. Instead DevSpace will now always use the current kube-context (or the context passed via the --kube-context flag) and remember the most recently used kube-context and namespace. If the user starts the deployment process using devspace dev or devspace deploy, DevSpace will print a warning if the current kube-context is different than the previously used one and wait a couple of seconds to give the user the chance to abort the command and prevent that the user accidentally deploys to the wrong cluster or namespace.
Removed devspace install since this command is no longer needed
Renamed devspace use/list config(s) into devspace use/list profile(s)
Renamed config option dependencies[*].config into dependencies[*].profile
devspace dev will now only rebuild images if they were not built before or the flag --force-build / -b is set
The shortcut flag for --pick -p was removed. -p is not used as --profile shortcut flag
The config option dev.overrideImages.dockerfile and dev.overrideImages.context were removed. dev.overrideImages was renamed to dev.interactive. The config will be automatically converted via devspace update config
New Features:
New config version v1beta3
Profiles: you are now able to specify multiple profiles in devspace.yaml and switch between those profiles via the devspace use profile command or the --profile / -p flag. See multiple profiles for an example how to use profiles.
Config Patches: you are now able to specify config patches in profiles to override certain parts of the config (see multiple profiles for an example). This makes it easy to reuse most of the config and exchange only small parts.
devspace dev is now able to log multiple pods to the console. To enable this behavior by default strip the config option dev.interactive from your devspace.yaml.
Interactive mode: when using devspace dev -i you can choose an image which should be started in interactive mode. This means that the image entrypoint will be overriden by a sleep command and a terminal to that image will be openend. Interactive mode can be configured as default to mimic old behaviour with the config option dev.interactive.enabled and dev.interactive.images. dev.terminal was moved to dev.interactive.terminal.
New config option dev.sync[*].imageName and dev.sync[*].imageName as an alternative to labelSelector. With imageName DevSpace will automatically find the pods in which the image is used and start sync or port-forwarding. Take a look at quickstart for an example
New config option dev.open: you can DevSpace now automatically open the browser to a certain webpage like http://localhost:8080.
New command devspace use context to switch the current kube-context and devspace use namespace to switch the current configured default namespace in the kube-context
New flag --verbose-dependencies in devspace dev/deploy/purge/build to print the output of dependency deployment
Fixes:
Fixed issue in dependency resolving where dependency variables were not correctly used
Show warning if current built tag is the same as last built tag
Overriding image entrypoints now also works with multi staged builds

New in DevSpace 3.5.18 (Aug 23, 2019)

New in DevSpace 3.5.17 (Aug 22, 2019)

New in DevSpace 3.5.16 (Aug 16, 2019)

New in DevSpace 3.5.15 (Aug 8, 2019)

New in DevSpace 3.5.14 (Aug 6, 2019)

New in DevSpace 3.5.12 (Jul 25, 2019)

New in DevSpace 3.5.11 Pre-release (Jul 24, 2019)

New in DevSpace 3.5.10 (Jul 2, 2019)

New in DevSpace 3.5.8 (Jun 8, 2019)

New in DevSpace 3.5.7 (Jun 5, 2019)

New in DevSpace 3.5.7 Pre-release (Jun 3, 2019)

New in DevSpace 3.5.6 Pre-release (May 31, 2019)

New in DevSpace 3.5.5 (May 30, 2019)

New in DevSpace 3.5.4 Beta 2 (May 28, 2019)

New in DevSpace 3.5.3 (May 18, 2019)

New in DevSpace 3.5.2 (May 17, 2019)

New in DevSpace 3.5.1 (May 14, 2019)

New Features:
Dependencies: You are now able to specify other devspace projects as dependencies, which will be built and deployed before the current project is deployed. Take a look at the examples for more information.
Custom Builder: You are now able to build images with custom user-defined commands. See examples for an example. (#534)
Parallel Image Building: As soon as there are 2 or more images defined in the devspace.yaml, devspace will build the images in parallel. You can still tell devspace to build sequentially with the flag build-sequential (#533)
Hooks: You are now able to define custom commands that are executed at certain points during the devspace pipeline execution. Currently supported is before / after image building and deploying. In addition it is also possible to execute custom commands directly before or after a certain deployment. See examples for an example. (#535)
New predefined variables: You are now able to use these predefined variables in your devspace.yaml:
DEVSPACE_RANDOM: A random string, that will be different every time the devspace.yaml is loaded (useful as tag for an image)
DEVSPACE_TIMESTAMP: The current unix timestamp in seconds when the config was loaded by devspace
DEVSPACE_GIT_COMMIT: The current git head short hash (useful as tag for an image)
New flag --deployments for devspace deploy and devspace dev to only deploy a specific deployment
Changes:
If the docker daemon cannot be reached but builder is docker, devspace will fallback to building with kaniko instead. If you want devspace to fail instead, you can set the config option images.your_image.build.docker.disableFallback to true.
New config version v1beta2, you can update your current config with devspace update config
Devspace dev, devspace deploy and devspace purge have an --namespace flag that let's you redirect devspace to another kubectl namespace
Fixes & Improvements:
Fixed an issue where the image name was not correctly replaced, if the image has never been built.
Fixed an issue with internal caching mechanism which sometimes could lead to unnecessary redeploys
Fixed an issue when you switched spaces the cached hashes where not erased (#527)
Devspace init doesn't write kube context anymore
Devspace init now always asks how you would like to initialize your project

New in DevSpace 3.4.0 (Apr 30, 2019)

New in DevSpace 3.3.1 (Apr 18, 2019)

New in DevSpace 3.3.0 (Apr 10, 2019)

New in DevSpace 3.3.0 Pre-release (Apr 5, 2019)

New in DevSpace 3.2.1 (Apr 1, 2019)

New in DevSpace 3.0.0 (Feb 26, 2019)

BREAKING CHANGES:
Removed internalRegistry from config
Removed registries.auth from config
Removed overwrite.yaml in favor of configs.yaml (more details below)
Removed --config-overwrite flags for devspace commands
Renamed devspace add service / devspace remove service / devspace list services to selector
devspace up does not run devspace init anymore if devspace project was not configured already
Major changes:
New helm chart (for more informations see https://devspace.cloud/docs/charts/devspace-chart)
New devspace analyze command - analyzes a namespace for potential problems, like pods/containers not starting and warning events and prints a small report (for more informations see https://devspace.cloud/docs/cli/analyze)
Overriding docker image entrypoints in memory: (for more information see https://devspace.cloud/docs/development/entrypoint-overwrites)
Devspace is now able to override docker image entrypoints during docker build time. It will append an ENTRYPOINT and CMD command to the Dockerfile in memory and leverage existing cached layers. This makes it possible to have a reliable and easy to understand way of overwriting a container image entrypoint for development, independent of the deployment strategy
Helm deploying:
Devspace now replaces an image in the overwrite values and values.yaml for helm. New configs.yaml (more information on https://devspace.cloud/docs/configuration/multiple-configs):
You are now able to specify multiple configurations in the configs.yaml. If configs.yaml does not exist it will just use the old config.yaml.
Config variables (more information on https://devspace.cloud/docs/configuration/variables):
You are now able to specify variables within the config to make it more dynamic
Complete rework of the devspace cloud: (more information on https://devspace.cloud)
devspace.cloud provisions private hosted kubernetes namespaces for your application. You are also now able to use a private docker registry for your docker images at (dscr.io). In addition you are now also able to connect custom domains and monitor your namespaces within devspace.cloud.
Other changes:
Command Changes:
devspace analyze - analyzes the current namespace for problems
devspace logs - prints the logs and attaches to the specified terminal pod
devspace update config - converts the config into the newest version
devspace dev - renamed devspace up command (up still works but is now deprecated)
devspace purge - renamed devspace down command (down still works but is not deprecated)
devspace login - login to devspace.cloud
devspace create/use/remove space - create/use/delete a private namespace within devspace.cloud as target for deployment
devspace list configs/spaces/vars
Config Changes:
Introduced new config version v1alpha2 (old version is automatically converted, you can also update the config via devspace update config)
devspace is now dev
moved deployments out of devspace to highest level
registries are now prepended to the image in the official form (e.g. myreg.io/myusername/myreponame) instead of defining them separately at the registry level
tiller namespace was moved from top level to the helm configuration in deployments, so you are able to deploy to different tiller namespaces
it is now possible to specify multiple helm override value files in the config under deployments[].helm.overrides
Smaller changes:
devspace now detects an active devspace in the parent folders if in the starting working directory no devspace configuration is found
devspace tries to rollback the helm chart after a failed deployment
reworked the devspace output
devspace purge/down now deletes the deployments in reverse order

New in DevSpace 3.0.0 Beta 2 (Feb 25, 2019)

BREAKING CHANGES:
Removed internalRegistry from config
Removed registries.auth from config
Removed overwrite.yaml in favor of configs.yaml (more details below)
Removed --config-overwrite flags for devspace commands
Renamed devspace add service / devspace remove service / devspace list services to selector
devspace up does not run devspace init anymore if devspace project was not configured already
Other changes:
Command Changes:
devspace analyze - analyzes the current namespace for problems
devspace logs - prints the logs and attaches to the specified terminal pod
devspace update config - converts the config into the newest version
devspace dev - renamed devspace up command (up still works but is now deprecated)
devspace purge - renamed devspace down command (down still works but is not deprecated)
devspace login - login to devspace.cloud
devspace create/use/remove space - create/use/delete a private namespace within devspace.cloud as target for deployment
devspace list configs/spaces/vars
Config Changes:
New helm chart (for more informations see https://devspace.cloud/docs/charts/devspace-chart)
New devspace analyze command - analyzes a namespace for potential problems, like pods/containers not starting and warning events and prints a small report (for more informations see https://devspace.cloud/docs/cli/analyze)
Overriding docker image entrypoints in memory: (for more information see https://devspace.cloud/docs/development/entrypoint-overwrites)
Devspace is now able to override docker image entrypoints during docker build time. It will append an ENTRYPOINT and CMD command to the Dockerfile in memory and leverage existing cached layers. This makes it possible to have a reliable and easy to understand way of overwriting a container image entrypoint for development, independent of the deployment strategy
Helm deploying:
Devspace now replaces an image in the overwrite values and values.yaml for helm.
New configs.yaml (more information on https://devspace.cloud/docs/configuration/multiple-configs):
You are now able to specify multiple configurations in the configs.yaml. If configs.yaml does not exist it will just use the old config.yaml.
Config variables (more information on https://devspace.cloud/docs/configuration/variables):
You are now able to specify variables within the config to make it more dynamic.
Complete rework of the devspace cloud: (more information on https://devspace.cloud)
devspace.cloud provisions private hosted kubernetes namespaces for your application. You are also now able to use a private docker registry for your docker images at (dscr.io). In addition you are now also able to connect custom domains and monitor your namespaces within devspace.cloud.
Introduced new config version v1alpha2 (old version is automatically converted, you can also update the config via devspace update config)
devspace is now dev
moved deployments out of devspace to highest level
registries are now prepended to the image in the official form (e.g. myreg.io/myusername/myreponame) instead of defining them separately at the registry level
tiller namespace was moved from top level to the helm configuration in deployments, so you are able to deploy to different tiller namespaces
it is now possible to specify multiple helm override value files in the config under deployments[].helm.overrides
Smaller changes:
devspace now detects an active devspace in the parent folders if in the starting working directory no devspace configuration is found
devspace tries to rollback the helm chart after a failed deployment
reworked the devspace output
devspace purge/down now deletes the deployments in reverse order
Major changes: