Skip to content

Releases: devspace-sh/devspace

v6.2.0

28 Nov 18:12
e1d27b9

Choose a tag to compare

Local Registry

DevSpace now makes it even easier to start developing on Kubernetes. In many cases, it can be difficult to get started when you don't have an established way of pushing images between your local environment and a remote cluster. Setting up a registry when you're only evaluating Kubernetes and DevSpace is sometimes too much to ask.

DevSpace will detect whether you are using a local or remote cluster. When using a remote cluster DevSpace will check if you have push permissions to the image's registry. When you do not have push permissions, DevSpace will deploy an image registry to your cluster with a NodePort service, start port forwarding between your localhost and the registry pod, and update your image URLs to use the new localhost registry URL. The remote cluster will now resolve images from the deployed registry.

For cases when you are using a local Kubernetes cluster, or have push permissions to a remote registry, DevSpace will behave exactly as before. No additional configuration is needed in devspace.yaml, but if you wish to enabled persistence for the local registry, or use a custom registry image, configuration options are available.

What's Changed

Other Changes

New Contributors

Full Changelog: v6.1.1...v6.2.0

v6.2.0-beta.0

23 Nov 19:14

Choose a tag to compare

v6.2.0-beta.0 Pre-release
Pre-release

Local Registry

DevSpace now makes it even easier to start developing on Kubernetes. In many cases, it can be difficult to get started when you don't have an established way of pushing images between your local environment and a remote cluster. Setting up a registry when you're only evaluating Kubernetes and DevSpace is sometimes too much to ask.

DevSpace will detect whether you are using a local or remote cluster. When using a remote cluster DevSpace will check if you have push permissions to the image's registry. When you do not have push permissions, DevSpace will deploy an image registry to your cluster with a NodePort service, start port forwarding between your localhost and the registry pod, and update your image URLs to use the new localhost registry URL. The remote cluster will now resolve images from the deployed registry.

For cases when you are using a local Kubernetes cluster, or have push permissions to a remote registry, DevSpace will behave exactly as before. No additional configuration is needed in devspace.yaml, but if you wish to enabled persistence for the local registry, or use a custom registry image, configuration options are available.

What's Changed

  • Add DEVSPACE_PROFILES variable and is_in command by @alexissellier in #2297
  • Specify a kubeClient when loading the devspace configuration by @alexissellier in #2306
  • Add dark-green color for completed state pods in UI by @mahendrabagul in #2335
  • Improve arch detection of pod when installing devspacehelper by @pratikjagrut in #2336 and @FabianKramm in #2381
  • Fallback to ssh if https doesn't work when cloning dependencies by @pratikjagrut in #2330 & #2355
  • Allow importing require statements and show all failures by @dtomasi in #2354
  • Add disabled flag for dependencies to avoid resolving all dependencies by @lizardruss in #2361
  • Add proper schema validation for vars by @mahendrabagul in #2343
  • Fix an issue when authenticating with Azure Container Registry (ACR) by @lizardruss in #2376
  • Local registry by @lizardruss in #2326
  • Support "~" (home) at the start of sync path by @matskiv in #2384
  • Add SIGINT syscall signal before SIGKILL by @mahendrabagul in #2388
  • Fixed improper parsing of volume name by @ryancharris in #2405
  • Use 'wss' protocol when DevSpace ui is loaded via 'https' by @lizardruss in #2410
  • Fixed building in Kaniko from Windows by @lizardruss in #2423
  • Improve output for pull secret creation by @FabianKramm in #2428
  • Pass DevSpace vars to plugin environment by @mahendrabagul in #2400
  • Add global flag for running dependencies sequentially by @pratikjagrut in #2424
  • Fix commands with predefined variables by @FabianKramm in #2429
  • Fix local registry failing with multiple dependencies by @lizardruss in #2425
  • Scale down replica sets to allow transfer of persistPaths persistent volume claims between pods by @lizardruss in #2431
  • Fix imported variables are not used in other variables by @pratikjagrut in #2432

Other Changes

New Contributors

Full Changelog: v6.1.1...v6.2.0-beta.0

v6.2.0-alpha.0

25 Oct 21:09
bf42b41

Choose a tag to compare

v6.2.0-alpha.0 Pre-release
Pre-release

Local Registry

DevSpace now makes it even easier to start developing on Kubernetes. In many cases, it can be difficult to get started when you don't have an established way of pushing images between your local environment and a remote cluster. Setting up a registry when you're only evaluating Kubernetes and DevSpace is sometimes too much to ask.

DevSpace will detect whether you are using a local or remote cluster. When using a remote cluster DevSpace will check if you have push permissions to the image's registry. When you do not have push permissions, DevSpace will deploy an image registry to your cluster with a NodePort service, start port forwarding between your localhost and the registry pod, and update your image URLs to use the new localhost registry URL. The remote cluster will now resolve images from the deployed registry.

For cases when you are using a local Kubernetes cluster, or have push permissions to a remote registry, DevSpace will behave exactly as before. No additional configuration is needed in devspace.yaml, but if you wish to enabled persistence for the local registry, or use a custom registry image, configuration options are available.

What's Changed

  • Add dark-green color for completed state pods in UI by @mahendrabagul in #2335
  • Improve arch detection of pod when installing devspacehelper by @pratikjagrut in #2336 and @FabianKramm in #2381
  • Fallback to ssh if https doesn't work when cloning dependencies by @pratikjagrut in #2330 & #2355
  • Allow importing require statements and show all failures by @dtomasi in #2354
  • Add disabled flag for dependencies to avoid resolving all dependencies by @lizardruss in #2361
  • Add proper schema validation for vars by @mahendrabagul in #2343
  • Fix an issue when authenticating with Azure Container Registry (ACR) by @lizardruss in #2376
  • Add Hooks page in docs by @mahendrabagul in #2364
  • Local registry by @lizardruss in #2326
  • Support "~" (home) at the start of sync path by @matskiv in #2384

Other Changes

New Contributors

Full Changelog: v6.1.2-alpha.0...v6.2.0-alpha.0

v6.1.2-alpha.0

23 Sep 08:49
add4feb

Choose a tag to compare

v6.1.2-alpha.0 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v6.1.1...v6.1.2-alpha.0

v6.1.1

12 Sep 20:01
9cd3723

Choose a tag to compare

What's Changed

Full Changelog: v6.1.0...v6.1.1

v6.1.1-beta.0

12 Sep 18:06
9cd3723

Choose a tag to compare

v6.1.1-beta.0 Pre-release
Pre-release

What's Changed

Full Changelog: v6.1.0...v6.1.1-beta.0

v5.18.6-beta.0

12 Sep 20:05
04e45e7

Choose a tag to compare

v5.18.6-beta.0 Pre-release
Pre-release

What's Changed

Full Changelog: v5.18.5...v5.18.6-beta.0

v6.1.0

09 Sep 15:39
8c393e2

Choose a tag to compare

Changes

  • New option dev.sync.onUpload.exec.once to only execute a command a single time in a container's lifecycle
  • Fixed an issue where xargs was sometimes not working correctly for non pipeline functions
  • Fixed an issue where port-forwarding in devspace could be blocking
  • Fixed an issue where DevSpace skipped creating a pull secret when logged in with Azure container registry. (thanks @lizardruss)
  • Silent params value being true used to discard the logs, setting it to false will now show the logs on the terminal when --debug is enabled. (thanks @mahendrabagul)
  • DevSpace is now aware of sleeping Kubernetes environments and improves the messaging and handling for it
  • Bumped component chart to 0.8.5
  • Allow $$() to escape $() for config expressions
  • Fixed an issue where DevSpace would incorrectly omit \r in pipeline commands
  • New --tty flag for devspace enter to disable tty
  • New dev.terminal.disableTTY option to disable tty
  • New wait_pod function for pipelines that waits for pods / containers to become ready
  • Variables can now be used in the whole imports section
  • DevSpace will not ask a question anymore if stdin is not recognized as a terminal

Other Changes

New Contributors

Full Changelog: v6.0.1...v6.1.0-beta.0

v6.1.0-beta.0

09 Sep 09:29
6636c72

Choose a tag to compare

v6.1.0-beta.0 Pre-release
Pre-release

Changes

  • New option dev.sync.onUpload.exec.once to only execute a command a single time in a container's lifecycle
  • Fixed an issue where xargs was sometimes not working correctly for non pipeline functions
  • Fixed an issue where port-forwarding in devspace could be blocking
  • Fixed an issue where DevSpace skipped creating a pull secret when logged in with Azure container registry. (thanks @lizardruss)
  • Silent params value being true used to discard the logs, setting it to false will now show the logs on the terminal when --debug is enabled. (thanks @mahendrabagul)
  • DevSpace is now aware of sleeping Kubernetes environments and improves the messaging and handling for it
  • Bumped component chart to 0.8.5
  • Allow $$() to escape $() for config expressions
  • Fixed an issue where DevSpace would incorrectly omit \r in pipeline commands
  • New --tty flag for devspace enter to disable tty
  • New dev.terminal.disableTTY option to disable tty
  • New wait_pod function for pipelines that waits for pods / containers to become ready
  • Variables can now be used in the whole imports section
  • DevSpace will not ask a question anymore if stdin is not recognized as a terminal

Other Changes

New Contributors

Full Changelog: v6.0.1...v6.1.0-beta.0

v6.0.1

26 Aug 17:19
ffa1317

Choose a tag to compare

What's Changed

  • Fixed an issue where DevSpace had problems syncing single files by @FabianKramm in #2257
  • Fixed an issue where DevSpace would always re-deploy charts imported using git by @lizardruss in #2244
  • Fixed an issue where DevSpace wouldn't resolve environment variable vars correctly by @FabianKramm in #2249
  • Fixed an issue where DevSpace incorrectly compared semantic versions. by @CiiDyR in #2250
  • Fixed an issue where DevSpace commands were not usable in the DevSpace UI by @FabianKramm in #2251
  • Fixed an issue where DevSpace would panic if there would be an empty pipeline, var, command, pullSecret or dev config by @FabianKramm in #2252
  • Improved the output if a yaml parsing error occurs @FabianKramm in #2253
  • Print error if reserved function name is used in config @FabianKramm in #2253
  • Mention that path field can be a URL as well by @alexissellier in #2235
  • Fixed an issue where DevSpace was not correctly authenticating to an OCI registry if chart.username and chart.password were provided by @FabianKramm in #2240
  • Fixed an issue where DevSpace would spawn many subprocesses if devspace was used as part of a DevSpace variable by @FabianKramm in #2240

New Contributors

Full Changelog: v6.0.0...v6.0.1