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 LukasGentele over 5 years ago
tar
command to be present in the container. (#542, #441)Published by FabianKramm over 5 years ago
Published by FabianKramm over 5 years ago
dev.selectors
could lead to a nil pointer panicPublished by FabianKramm over 5 years ago
build-sequential
(#533)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)
--deployments
for devspace deploy
and devspace dev
to only deploy a specific deploymentdevspace update config
devspace dev
, devspace deploy
and devspace purge
have an --namespace
flag that let's you redirect devspace to another kubectl namespacedevspace init
doesn't write kube context anymoredevspace init
now always asks how you would like to initialize your projectPublished by FabianKramm over 5 years ago
devspace list/remove/connect cluster
: you are now able to connect your own cluster to devspace cloud (see more at connect clusters)devspace.yaml
)devspace sync
opens a bidirectional sync connection to a specific pod and container and prints the sync log to the consolePublished by FabianKramm over 5 years ago
devspace init
, when kubectl config was missingdevspace create space
and devspace use space
Published by FabianKramm over 5 years ago
devspace add component
to devspace add deployment --component
devspace add package
to devspace add deployment --chart
devspace status deployments
to devspace list deployments
devspace init
: If no Dockerfile is found there are now 5 options how to initialize the projectdevspace add [option]
Published by FabianKramm over 5 years ago
Fixes:
devspace init
now correctly detects Dockerfile EXPOSE statementsdevspace analyze
only considers container restarts important if they occured in the last 2 hoursPublished by FabianKramm over 5 years ago
New features:
devspace containerize
will detect your programming language and create a Dockerfile for your application (was previously part of `devspace init, but can now be used separately)devspace init
now detects the application port based on the dockerfileFixes:
devspace remove space --all
now also removes the kube contexts correctlyPublished by LukasGentele over 5 years ago
Fixes:
Improvements:
Published by FabianKramm over 5 years ago
Fixes:
devspace use space
and devspace create space
where setting environment variables took too longPublished by FabianKramm over 5 years ago
Changes:
devspace update config
to upgrade the config to the latest version.devspace analyze
only checks the events if a pod has an issue or a replicaset or statefulset cannot start a poddevspace dev
devspace enter
and devspace logs
can now be used outside of a devspace projectdevspace add component
- Creates a new component in the chart/values.yaml based on some predefined components. To list all available components you can run devspace list available-components
devspace update chart
- Updates the devspace helm chart to the newest versiondevspace open
- Opens the space domain in the browserdevspace ui
- Opens the management ui in the browserPublished by FabianKramm over 5 years ago
Fixes:
Enhancements:
devspace analyze
and returns an error if it finds any issues -> this makes it much easier to find an issue with container starting or faulty dockerfiles)Published by LukasGentele over 5 years ago
Changes introduced in this pull request:
myimage: mydockeruser/mydockerimage:latest
will be rewritten in memory during devspace dev/deploy
to myimage: mydockeruser/mydockerimage:JUSTBUILTTAG
by devspace, so you can easily integrate existing charts with devspace. This makes it possible to create helm charts that have a custom values structure instead of using the previous .Values.containers approach. For compatibility reasons devspace will still fill the .Values.containers.configImageKey.image fields during runtime.config1:
config:
path: mypath1.yaml
overrides:
- path: myoverride1.yaml
- data:
images:
default:
image: ${ImageName}
vars:
- name: ImageName
question: Please specify the image url
config2:
config:
data:
...
overrides:
- path: myoverride1.yaml
You can list all configs with the devspace list configs
command. You can change the active config via devspace use config config2
.
deployments:
- name: ${DeploymentName}
helm:
overrideValues:
myValue: ${MyVariable}
Variables have the form ${Name} and devspace will try to get the value from an environment variable in the form of DEVSPACE_VAR_NAME. If there is no such environment variable found, devspace will ask the user to input them after it loaded the active config. The variable values are stored in the genrated.yaml and are user specific and should not be checked in. You can also define a custom question, default value and regex validation pattern either in the configs.yaml under the configName.vars key or in the vars.yaml if there is only a single config.
Published by LukasGentele over 5 years ago
Published by FabianKramm over 5 years ago
Published by FabianKramm almost 6 years ago
Changes:
devspace add service/image
functionality (see #432)--service
flag for devspace add port/sync
commandsFixes:
Published by FabianKramm almost 6 years ago
New Features:
Changes:
devspace up
, the image contextPath is now hashed and checked for changes instead of only the dockerfile timestamp (excluding the patterns in .dockerignore) (see #414)Fixes:
devspace add/remove deployment
where the command wouldn't save the config correctly (thanks @ALCarden)Published by FabianKramm almost 6 years ago
Published by FabianKramm almost 6 years ago
Changes:
devspace down --deployment
option to delete a single or multiple deploymentsFixes:
devspace up
would deploy tiller to the wrong namespace if no config.yaml exists (#417)