DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
APACHE-2.0 License
Bot releases are hidden (Show)
Published by FabianKramm over 3 years ago
dev.replacePods
would fail config validationPublished by FabianKramm over 3 years ago
Published by FabianKramm over 3 years ago
deployments[*].helm.values.service.ports[*].name
to schema (#1472)devspace dev
completely, if devspace was not able to reconnect correctlyPublished by FabianKramm over 3 years ago
deployments[*].helm.values.service.ports[*].name
to schema (#1472)devspace dev
completely, if devspace was not able to reconnect correctlyPublished by FabianKramm over 3 years ago
devspace dev
completely, if devspace could not reconnectPublished by FabianKramm over 3 years ago
--wait
in devspace dev/deploy
would sometimes return too soondependencies[*].overwriteVars
option to disable variable overwriting in dependencies (#1466)devspace dev
if a replaced pod cannot be found, but the parent was scaled down alreadyPublished by FabianKramm over 3 years ago
--wait
in devspace dev/deploy
would sometimes return too soondependencies[*].overwriteVars
option to disable variable overwriting in dependencies (#1466)devspace dev
if a replaced pod cannot be found, but the parent was scaled down alreadyPublished by FabianKramm over 3 years ago
--wait
in devspace dev/deploy
would sometimes return too soonPublished by FabianKramm over 3 years ago
Published by FabianKramm over 3 years ago
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'
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
--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
insteaddevspace reset pods
will now reset scaled down deployments, statefulsets & replicasets even though no resettable pod could be founddevspace init
now uses imageSelector
instead of imageName
to generate a getting started configurationdev.replacePods
during devspace purge
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 profilesdevspace update plugin
will now allow you to install older plugin versions as well when --version
is specifiedPublished by FabianKramm over 3 years ago
Published by LukasGentele over 3 years ago
Published by FabianKramm over 3 years ago
Published by FabianKramm over 3 years ago
Published by FabianKramm over 3 years ago
v1beta10
. Polling can still be used by setting dev.sync[*].polling
to true or using an older config version. Inotify file watching greatly decreases CPU usage in containers if many files are watched and decreases change detection time (#1429)DEVSPACE_LOG_TIMESTAMPS
is set to true
devspace init
for build stage and disable building by default for newly created devspace.yaml
sPublished by FabianKramm over 3 years ago
v1beta10
. Polling can still be used by setting dev.sync[*].polling
to true or using an older config version. Inotify file watching greatly decreases CPU usage in containers if many files are watched and decreases change detection time (#1429)DEVSPACE_LOG_TIMESTAMPS
is set to true
devspace init
for build stage and disable building by default for newly created devspace.yaml
sPublished by FabianKramm over 3 years ago
v1beta10
. Polling can still be used by setting dev.sync[*].polling
to true or using an older config version. Inotify file watching greatly decreases CPU usage in containers if many files are watched and decreases change detection time (#1429)DEVSPACE_LOG_TIMESTAMPS
is set to true
devspace init
for build stage and disable building by default for newly created devspace.yaml
sPublished by FabianKramm over 3 years ago
devspace open
would not work correctly with port-forwarding (#1432)deployments[*].helm.displayOutput
to show the helm upgrade
command output (#1423)Published by LukasGentele over 3 years ago
devspace init
: add additional comments to the generated devspace.yamldevspace init
Published by FabianKramm over 3 years ago