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

v4.1.2

Fixes:

• Fix an issue in devspace purge where devspace tried to delete the wrong deployment name

v4.1.1

v4.1.1 - Fix

• Fixes devspace enter -l label=value #751

v4.1.0

New Features

• New command devspace set var that allows the user to set a specific configuration variable
• New command devspace reset dependencies that erases the dependency cache
• New --terminal flag for devspace dev that only opens a terminal (and not overrides image entrypoints like -i does)
• New --no-watch flag for devspace sync that does sync the files from local and remote and then stops
• New --tag flag for devspace build

Changes

• New config version v1beta4, you can update your config with devspace update config
• deployments.component is now helm.componentChart: true, component configuration is now configured under deployments.helm.values
• The predefined variables ${DEVSPACE_SPACE_DOMAIN1...} are now deprecated
• devspace open now also works for wildcard domains such as *.my-domain.com
• Open policy agent gatekeeper & gatekeeper rules are now deployed on cluster connect
• devspace dev now fatals instead of showing an error if the forwarded port is already in use by a previous devspace dev instance
• Improve image name replacement logic during devspace dev & devspace deploy
• Devspace now shows an additional warning if a graphql query fails on an outdated version

Fixes

• Fix issue during devspace init where the port forwarding was not correctly written
• Fix issue during devspace init where the image name was not correctly written
• Fix a potential nil pointer in devspace update config
• devspace enter now shows an error immediately when trying to enter a pod with a label selector that does not exist

v4.1.0

New Features

• New command devspace set var that allows the user to set a specific configuration variable
• New command devspace reset dependencies that erases the dependency cache
• New --terminal flag for devspace dev that only opens a terminal (and not overrides image entrypoints like -i does)
• New --no-watch flag for devspace sync that does sync the files from local and remote and then stops
• New --tag flag for devspace build

Changes

• New config version v1beta4, you can update your config with devspace update config
• deployments.component is now helm.componentChart: true, component configuration is now configured under deployments.helm.values
• The predefined variables ${DEVSPACE_SPACE_DOMAIN1...} are now deprecated
• devspace open now also works for wildcard domains such as *.my-domain.com
• Open policy agent gatekeeper & gatekeeper rules are now deployed on cluster connect
• devspace dev now fatals instead of showing an error if the forwarded port is already in use by a previous devspace dev instance
• Improve image name replacement logic during devspace dev & devspace deploy
• Devspace now shows an additional warning if a graphql query fails on an outdated version

Fixes

• Fix issue during devspace init where the port forwarding was not correctly written
• Fix issue during devspace init where the image name was not correctly written
• Fix a potential nil pointer in devspace update config
• devspace enter now shows an error immediately when trying to enter a pod with a label selector that does not exist

v4.0.4

Changes / Fixes

• Add --download-on-initial-sync flag to devspace sync that is enabled by default (#732)
• Images will now be rebuilt during devspace dev if there is no sync path with the image name (#733). In addition, you can configure a labelSelector and imageName together for sync paths, port forwarding etc.
• If a local port is already taken during port forwarding a warning message is shown (#739)

For more details, see: https://devspace.cloud/blog/2019/10/11/release-devspace-v4.0.4

v4.0.3

Changes

• devspace init and add deployment --component=x will add helm deployments instead of component deployments now (makes it more understandable that a component is technically just a helm deployment)
• support for initContainers in component chart
• support for initContainers in devspace logs|attach|enter
• --option-ui flag for devspace connect cluster
• implementation for devspace list namespaces
• implementation for devspace list contexts

Fixes

• sync will not delete folders which contains files or folders matching ignore paths
• ignore paths ending with / will not only ignore the contents of the folder but also the folder itself
• fix possible panic in devspace remove deployment and in analytics util package
• fixes and improvements for command-line output and tests

v4.0.2

Changes:

• Allow use of config vars in custom commands
• New config option vars[*].password for variables (hides response to question with *)
• Don't download changes on initial sync (use new config option dev.sync[*].downloadOnInitialSync to explicitly enable downloading changes on initial sync)
• Delete remote files which are not existing locally on initial sync (does not apply to ignored files/paths)
• Error if flag -s used but no last context
• Add flag --host to specify provider host (DevSpace Cloud on-premise)

Fixes

• Disable flag parsing for devspace run
• Disable logging for devspace run
• Allow connecting clusters with private IP address (DevSpace Cloud on-premise)
• Minor improvements of log output