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
Published by FabianKramm over 3 years ago
profiles.description
to describe what a profile is doing (can be viewed via devspace list profiles) (#1312)--component
flag for devspace add deployment
(#1315)devspace deploy
with kubectl wouldn't deploy correctly (#1314)--skip-push-local-kube
to devspace dev
, devspace deploy
, devspace build
and devspace render
to skip or allow image push skipping in local kubernetes environmentsPublished by FabianKramm over 3 years ago
devspace dev --ui-port
flag to specify the port of the ui it should start underdevspace open
would not recognize LoadBalancer servicesPublished by FabianKramm over 3 years ago
devspace dev --ui-port
flag to specify the port of the ui it should start underdevspace open
would not recognize LoadBalancer servicesPublished by FabianKramm over 3 years ago
Published by FabianKramm over 3 years ago
We renamed the devspace repository from devspace-cloud/devspace
to loft-sh/devspace
. We felt this change was necessary, since there was some confusion regarding the relationship between devspace, devspace-cloud and loft:
Published by FabianKramm over 3 years ago
Published by FabianKramm over 3 years ago
devspace sync --config ...
asks for a sync path by displaying the image or label selector (#1300)dev.sync.imageName
and dev.sync.labelSelector
simultaneouslyPublished by FabianKramm over 3 years ago
images.build.kaniko.command
, images.build.kaniko.env
, images.build.kaniko.initEnv
and images.build.kaniko.skipPullSecretMount
for kaniko builderdev.sync
, dev.ports
and profiles
config sectionsPublished by FabianKramm almost 4 years ago
Published by FabianKramm almost 4 years ago
--parent-profile
to apply multiple profiles with flags:# Applies the profiles profile1, profile2, profile3 and profile4 in this order
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3 --profile=profile4
# You can also leave out the --profile flag and only the profiles
# profile1, profile2 and profile3 are appied
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3
upload
and download
for hooks to upload or download files from a container:hooks:
# Upload the complete local bin folder to the container path ./bin
- upload:
localPath: bin
containerPath: bin
where:
container:
imageName: default
when:
after:
deployments: deployment-1
# Download a single file from the container to the local path
- download:
localPath: build/artifact.jar
containerPath: build/artifact-test.jar
where:
container:
imageName: java
when:
after:
deployments: deployment-2
${DEVSPACE_VERSION}
hooks.when.before.purgeDeployments
, hooks.when.after.purgeDeployments
andhooks.when.onError.purgeDeployments
to execute hooks on devspace purge
dev.interactive.terminal.workDir
to specify a working directory to open the terminal in--workdir
for devspace enter
and devspace dev
to specify a working directory to open the terminal in or execute a command incommands section
. It is now possible to have commands that are only available or change with specific profiles. A profile can be used with devspace run
by supplying the flag before the run
: devspace --profile my-special-command-profile run profile-command
devspace init
that would lead to an incomplete devspace.yaml
--save-vars
and --restore-vars
are now globalprofiles.replace
would lead to a yaml errorPublished by LukasGentele almost 4 years ago
--parent-profile
to apply multiple profiles with flags:# Applies the profiles profile1, profile2, profile3 and profile4 in this order
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3 --profile=profile4
# You can also leave out the --profile flag and only the profiles
# profile1, profile2 and profile3 are appied
devspace dev --parent-profile=profile1 --parent-profile=profile2 --parent-profile=profile3
upload
and download
for hooks to upload or download files from a container:hooks:
# Upload the complete local bin folder to the container path ./bin
- upload:
localPath: bin
containerPath: bin
where:
container:
imageName: default
when:
after:
deployments: deployment-1
# Download a single file from the container to the local path
- download:
localPath: build/artifact.jar
containerPath: build/artifact-test.jar
where:
container:
imageName: java
when:
after:
deployments: deployment-2
${DEVSPACE_VERSION}
hooks.when.before.purgeDeployments
, hooks.when.after.purgeDeployments
andhooks.when.onError.purgeDeployments
to execute hooks on devspace purge
dev.interactive.terminal.workDir
to specify a working directory to open the terminal in--workdir
for devspace enter
and devspace dev
to specify a working directory to open the terminal in or execute a command incommands section
. It is now possible to have commands that are only available or change with specific profiles. A profile can be used with devspace run
by supplying the flag before the run
: devspace --profile my-special-command-profile run profile-command
devspace init
that would lead to an incomplete devspace.yaml
--save-vars
and --restore-vars
are now globalprofiles.replace
would lead to a yaml errorPublished by FabianKramm almost 4 years ago
Published by FabianKramm almost 4 years ago
Published by FabianKramm almost 4 years ago
imageName
was specifiedPublished by FabianKramm almost 4 years ago
devspace deploy
would raise a panic if it cannot find the release right after deploymentPublished by LukasGentele almost 4 years ago
devspace build
would not consider the --namespace
flagPublished by FabianKramm almost 4 years ago
images:
app:
tags:
# Each single hashtag will be replaced with a random character
- my-###-latest
- ${DEVSPACE_GIT_BRANCH}-#####
- ${USER}-#####
- '############'
tag(registry/repo/image)
and image(registry/repo/image)
in helm values to only insert a tag or the image name without any modification. This is useful for helm charts that split image and tag (#1188):images:
default:
image: registry/repo/image
tags:
- random-#####
deployments:
- name: my-deployment
helm:
chart: ...
values:
# Will be replaced by devspace to -> imageWithTag: registry/repo/image:random-xAhgW
imageWithTag: registry/repo/image
# Will be replaced by devspace to -> image: registry/repo/image
image: image(registry/repo/image)
# Will be replaced by devspace to -> tag: random-xAhgW
tag: tag(registry/repo/image)
dev.logs.selectors
option that allows you to specify additional label selectors to select pods you want to stream logs from:images:
default:
image: registry/repo/image
dev:
logs:
images:
# Selects all pods that use the image default (registry/repo/image)
- default
selectors:
# Selects all pods with the given label selector and streams the logs to the console
- labelSelector:
abc: def
containerName: optional
namespace: optional
hooks.*.where.container
:...
hooks:
- command: "echo"
args: ["Hello from within the container!"]
where:
container:
imageName: default
# Or select via labelSelector etc.
# labelSelector: ...
when:
after:
deployments: my-deployment
...
images:
image-1:
image: registry/repo/image
image-2:
image: registry/repo/image
hooks:
- command: "echo"
args: ["before", "all"]
when:
before:
images: all
- command: "echo"
args: ["before", "image-1"]
when:
before:
images: image-1
- command: "echo"
args: ["before", "image-2"]
when:
before:
images: image-2
--container
, --pod
, --label-selector
and --pick
for command devspace restart
hooks.*.background
and hooks.*.silent
to execute hooks without output or in the backgroundimages.*.build.kaniko.annotations
& images.*.build.kaniko.labels
to specify extra labels and annotations for the kaniko build pod (#1265)images.*.restartHelperPath
to override the bundled restart helper with a custom scriptimages.*.build.docker.useCli
to configure DevSpace to use the docker cli directlydev.logs.sync: false
in the devspace.yaml
dev.autoReload.deployments
would not correctly watch for changes to manifest folders and values files (#1255)devspace init
would create a failing devspace.yaml
if the Dockerfile was missing ENTRYPOINT and CMD (#1252).dockerignore
statements were not correctly working with kaniko builderPublished by FabianKramm almost 4 years ago
hooks.*.when.onError
to execute hooks if an error has occured (#1239):# This will print the error to the console that has occured during a deployment
hooks:
- command: "sh"
os: linux,darwin
args:
- -c
- 'echo "The following error has occured: $DEVSPACE_HOOK_ERROR"'
when:
onError:
deployments: all
dependencies.*.vars
to override variables in dependency configs:# This will deploy the same dependency 2 times with different variable values
dependencies:
- source:
path: my-dependency
vars:
- name: TEST
value: value-1
- source:
path: my-dependency
vars:
- name: TEST
value: value-2
images.*.build.kaniko.nodeSelector
, images.*.build.kaniko.initImage
and images.*.build.kaniko.serviceAccount
that make the kaniko pod creation more customizable (#1240)Published by FabianKramm almost 4 years ago