v4.5.0

New features

• New devspace print command that prints the current loaded config (with all filled variables, applied configs etc.), profile and variables (#893)

Changes

• devspace sync will not sync to the root folder / anymore to prevent misconfiguration if the root folder is the current working directory. If you really need to sync the root folder you have to specify it now explicitly as the container path (e.g. devspace sync --container-path /).

Fixes

• Improve devspace ui 'Stack' view with actually loaded variables instead of just recently loaded variables
• Fixed an issue with devspace add provider that prevented users from adding new providers
• FIxed an issue in devspace render where helm templates were not shown correctly

v4.4.0

New Features

• devspace sync is now able to only upload or download files via the --upload-only and --download-only flags (#871)
• New sync options sync.*.onDownload & sync.*.onUpload to execute custom commands locally or in the container if a file / folder gets uploaded or downloaded (#849)
• devspace sync is now able to load a sync configuration from a devspace.yaml via the --config flag (#863)
• New global --config flag that allows you to specify the path of the devspace.yaml to use for the command

Fixes

• Fix an issue where devspace sync would not correctly reconnect (#885)
• Fix an issue where remote manifests could not be deployed via kubectl (#864)
• Fix an issue where variables in dependencies were not correctly resolved (#873)
• Some internal code refactorings

v4.3.5

Changes:

• New devspace render command that builds images and instead of deploying the defined resources prints them instead (#846)
• Fixed a nil pointer panic in certain devspace login scenarios (#857)
• Fixed a panic when image in config yaml is empty (#847)
• Fixed an issue where permissions where not set correctly during sync (#848)
• Fixed an issue in sync where file pipes would not be correctly cleaned up (#851)

v4.3.4

Changes

• Sync and portforwarding will now completely restart if an issue is encountered meanwhile (#835 & #833)
• Fixed an issue where the .dockerignore was ignored to decide if an image should be rebuild (#838)
• New config version v1beta6: renamed images[].build.custom.flags to images[].build.custom.args (#830). This is not a breaking change, older config versions will be converted in memory automatically.
• Fixed an issue where sometimes devspace deploy was not rebuilding, even though the image build context has changed
• Bump internal helm version to v3.0.1
• Some internal refactoring & improvements

v4.3.2

Changes

• Improved sync algorithm: the sync should be now more stable and will automatically retry to upload or download changes if a failure occurs midway (#820)
• Stable charts are now working out of the box with DevSpace and Helm v3 (#828)
• Fixed an issue where dependencies were not redeployed when the kube context has changed (#825)
• Fixed a potential nil pointer when using the labelSelector option in dev.terminal

v4.3.1

Changes

• Fixed a nil pointer that could occur during space creation

v4.3.0

New Features

• DevSpace now works with Helm v3. Helm v3 is now the default option for the new config version v1beta5. Older config versions such as v1beta4 (devspace < v4.3.0) will still use helm v2 by default and work as expected. DevSpace will as usual automatically upgrade the existing config to the newest version in memory. Helm v2 can still be used by setting the option deployments[*].helm.v2 to true. (#807)
• New helm options: deployments[*].helm.recreate, deployments[*].helm.atomic, deployments[*].helm.driver (helm v3 only) & deployments[*].helm.cleanupOnFail. These options mimic the command line flags helm provides (see helm upgrade flags for more information)

Changes

• DevSpace now allows all kubectl auth plugins (#794)
• Upgrade internal helm v2 version to 2.16.1
• Some internal refactorings

v4.2.1

Changes

• Updated internal kubernetes version to 1.16.2
• Updated internal helm version to 2.16.0
• Updated deployed tiller version to 2.16.0 (#792)
• Fix issue in npm installer where asking a question during uninstall could lead to problems in automated environments (#798)
• Fix an issue with autoscaling in the helm component chart (#789)
• UI: Add Github button

v4.2.0

Localhost UI

You are now able to start the UI (even without a devspace.yaml config) to inspect any namespace in any cluster. Just run devspace ui anywhere on your computer to open the UI.

During devspace dev or with devspace ui DevSpace will now start a local UI server, that you can access via your browser. This works with every cluster regardless of Devspace Cloud. The Web UI is able to stream logs, proxy terminals, forward ports, run devspace run commands and has some other useful features.

Find more details about the localhost UI in our latest blog post.

Other changes

• New --wait flag for devspace enter that will wait till the pods are ready
• Fix issue where devspace tries to always create a clusterrolebinding for gke clusters (#762)
• Fix issue where devspace couldn't be executed correctly in a pipeline (#763)
• Fix issue where devspace was not waiting long enough for pods to become running (#760)
• Fix issue where devspace could not be installed via yarn (#772)

v4.1.3

Changes

• devspace update config will now show a warning that profiles are not updated automatically
• new images[*].build.docker.useBuildKit option to build with docker buildkit (#756)
• bump helm version to v2.15.0 (will now also work correctly with kubernetes v1.16.0)

Fixes

• Fix an issue where old config versions were not loaded correctly
• Fix a potential nil pointer in devspace list ports
• Fix an issue where upgrading the config would print warnings that ignore the --silent flag