Releases: devspace-sh/devspace
Releases · devspace-sh/devspace
v3.5.7
v3.5.6
Changes:
- Skip domain question on
devspace cluster connect
(We will implement a feature soon where a devspace.host domain will be automatically provisioned for the cluster) - Fixes an issue where it was not possible to enter a custom registry with port during
devspace init
(#557) - Fixes an issue where sync was not closing correctly on windows
- Fixes an issue where wrongly configured docker environment variables lead to an error
- Automatically append the
.devspace/
folder to dockerignore during build - Fixes an issue where the selected language none during
devspace init
would result in a wrong Dockerfile
v3.5.5
Changes
- The sync mechanism was changed and behaves now differently. We inject a small binary into the container that replaces the shell script we used in previous versions, this has several advantages: it uses less bandwidth in exchanging changes, it is more stable, it only requires the
tar
command to be present in the container. (#542, #441) - You can now specify options for component deployments (#547)
- Updates kubernetes dependencies to 1.14
- Updates helm dependencies to 2.14.0
- Fixes an issue where the KUBECONFIG environment variable was ignored
v3.5.3
Fixes:
- Fixed an issue where multiple connected clusters could lead to problems during cluster connect
v3.5.2
Fixes:
- Fixed an issue, where
dev.selectors
could lead to a nil pointer panic
v3.5.1
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
fordevspace deploy
anddevspace 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
anddevspace 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 anymoredevspace init
now always asks how you would like to initialize your project
v3.4.0
New functionality
devspace list/remove/connect cluster
: you are now able to connect your own cluster to devspace cloud (see more at connect clusters)- kustomize is now supported as deployment method (you need the newest version of kubectl installed and set kustomize to true in
devspace.yaml
) devspace sync
opens a bidirectional sync connection to a specific pod and container and prints the sync log to the console- new flag dev.sync.waitInitialSync: you can now tell devspace to wait for initial sync before starting a terminal into a pod (#343)
Changes
- devspace login now takes --key as parameter instead of --token
- config version updated to v1beta1 (will be upgraded automatically)
- portMappings -> forward
- localPort -> port (if remotePort is empty value for port is used)
Fixes
- fixed an issue with deleting spaces where the kubecontext was not correctly deleted
v3.3.1
Fixes
- Fixed an issue where the wrong question was asked on
devspace init
, when kubectl config was missing - Fixed a nil pointer panic, when docker was installed, but the docker daemon couldn't be reached
- Fixed an issue on linux with setting TILLER_NAMESPACE env variable during
devspace create space
anddevspace use space
v3.3.0
Changes
- .devspace/config.yaml was renamed to devspace.yaml (devspace will automatically rename the file)
- .devspace/vars.yaml was renamed to devspace-vars.yaml (devspace will automatically rename the file)
- .devspace/configs.yaml was renamed to devspace-configs.yaml (devspace will automatically rename the file)
- Moved
devspace add component
todevspace add deployment --component
- Moved
devspace add package
todevspace add deployment --chart
- Moved
devspace status deployments
todevspace list deployments
- New config version v1alpha4 (Will be converted automatically)
New Features
- New deployment method component (Will deploy the devspace-component-chart and the component options are essentially the values of the chart. This makes it easier for us to convert the values in the future when updating the chart)
- New options during
devspace init
: If no Dockerfile is found there are now 5 options how to initialize the project - Sync now works with relative paths & containerPath in sync config can be empty (Working directory of the container is used then)
- Added predefined config variables DEVSPACE_USERNAME (the devspace cloud username) and DEVSPACE_SPACE (the currently used space name) that can be used in the config
Fixes & Improvements
- Fixed an issue where config variables got lost after running
devspace add [option]
- Fixed an issue where config variables had to be reentered on every devspace command
- Config variables now also work within a string (e.g. 'dscr.io/{my_user}/devspace')
- Improved the kaniko builder (should be several times faster now)
v3.2.1
Fixes:
devspace init
now correctly detects Dockerfile EXPOSE statementsdevspace analyze
only considers container restarts important if they occured in the last 2 hours