Releases: devspace-sh/devspace
Releases · devspace-sh/devspace
v4.5.2
Enhancements:
- Add optional new config option
dependencies.*.nameto identify dependencies - Adds new flag
--dependencytodevspace render,devspace purgeanddevspace deployto individually handle dependency deployment / deletion (#906) devspace renderis now able to render dependencies aswell- New config option
images.*.build.docker.argsto specify custom cli flags (as soon as args are defined, DevSpace will build images via the command line instead of using the internal docker library) (#884) - Allows config patches to patch parts of the config
varssection (#904) - Added a new question to
devspace initto allow skipping registry selection for local kubernetes clusters (#907) - Updated the component helm chart to v0.1.3 (#913, #912, #900)
- Switches component chart helm repository from charts.devspace.cloud to charts.devspace.sh (#889)
Fixes:
- Fixes an issue in devspace render, where 2 successive helm templates where not rendered correctly (#943)
- Fixes an issue where the command
devspace status syncwas not working correctly (#921) - Fixed an issue where the
localSubPathof the sync config is not correctly applied whendevspace sync --config(#933) - Fixed a nil pointer in
devspace render(#927) - Fixed a possible nil pointer in
devspace login - Improved cannot sync root path error message (#915)
v4.5.0
New features
- New
devspace printcommand that prints the current loaded config (with all filled variables, applied configs etc.), profile and variables (#893)
Changes
devspace syncwill 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 providerthat prevented users from adding new providers - FIxed an issue in
devspace renderwhere helm templates were not shown correctly
v4.4.0
New Features
devspace syncis now able to only upload or download files via the--upload-onlyand--download-onlyflags (#871)- New sync options
sync.*.onDownload&sync.*.onUploadto execute custom commands locally or in the container if a file / folder gets uploaded or downloaded (#849) devspace syncis now able to load a sync configuration from adevspace.yamlvia the--configflag (#863)- New global
--configflag that allows you to specify the path of thedevspace.yamlto use for the command
Fixes
v4.3.5
Changes:
- New
devspace rendercommand that builds images and instead of deploying the defined resources prints them instead (#846) - Fixed a nil pointer panic in certain
devspace loginscenarios (#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.flagstoimages[].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 deploywas 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
--waitflag fordevspace enterthat 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)
