v0.21.5

This is an incremental release where the following has been done:

• Updated Mission Control theme to match the new SpaceCloud website theme.
• Updated outdated libraries to the latest version
• Fixed a bug in the DB read rest endpoint which didn't allow use of joins.
• Improved test coverage for the database module.

Upgrade guide

Follow the steps to migrate from v0.20.0 and above:

• Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
• Backup setup configuration (space-cli inspect sc-setup-config.yaml)
• Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.
• Make sure you run Reload Schema in Database > Settings for each SQL database you've added in SpaceCloud.

Ping us on #general of our Discord server, if you face any issues while migrating.

v0.21.4

This is a huge release where we are making everything in SpaceCloud fully open source. The following features are now available for everyone to use.

• Add multiple projects in a single k8s cluster
• Add multiple Databases in each project
• Enable caching on all database and REST queries

Upgrade guide

Follow the steps to migrate from v0.20.0 and above:

• Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
• Backup setup configuration (space-cli inspect sc-setup-config.yaml)
• Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.
• Make sure you run Reload Schema in Database > Settings for each SQL database you've added in SpaceCloud.

Ping us on #general of our Discord server, if you face any issues while migrating.

v0.21.3

This is a minor release containing a new enhancement.

Changes

• Added support for traffic splitting based on header & urls (#1485)

Upgrade guide

Follow the steps to migrate from v0.20.0 and above:

• Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
• Backup setup configuration (space-cli inspect sc-setup-config.yaml)
• Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.
• Make sure you run Reload Schema in Database > Settings for each SQL database you've added in SpaceCloud.

Ping us on #general of our Discord server, if you face any issues while migrating.

v0.21.2

This is a minor release containing a few fixes.

Changes

• Updated letsencrypt client

Upgrade guide

Follow the steps to migrate from v0.20.0 and above:

• Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
• Backup setup configuration (space-cli inspect sc-setup-config.yaml)
• Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.
• Make sure you run Reload Schema in Database > Settings for each SQL database you've added in SpaceCloud.

Ping us on #general of our Discord server, if you face any issues while migrating.

v0.19.8

This release contains a minor bugfix:

• Updated letsencrypt client

Upgrade guide

Upgrade is possible from v0.17.0 and above.

Before upgrading your cluster, make sure you backup cluster config using space-cli --project <project_id> get all /path/to/backup/dir. If things go right, you'll be able to reapply all saved project config using space-cli apply /path/to/backup/dir.

For Docker-based deployments:

Simply run space-cli upgrade.

For Kubernetes based deployment:

We recommend setting up a fresh Kubernetes cluster and installing Istio and SC on top of it. Don't forget to backup all project config first!

v0.21.1

This is a minor release containing a few fixes.

Changes

• Improved support for operation type one #1536
• Fixed issue with jwk urls #1530

To see the complete list of enhancements/fixes, check out the v0.21.1 milestone.

Upgrade guide

Follow the steps to migrate from v0.20.0 and above:

• Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
• Backup setup configuration (space-cli inspect sc-setup-config.yaml)
• Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.
• Make sure you run Reload Schema in Database > Settings for each SQL database you've added in SpaceCloud.

Ping us on #general of our Discord server, if you face any issues while migrating.

v0.21.0

This is a minor release containing few enhancements and fixes.

Changes

• Added support changing the request payload format in graphQL API #1526
• Dataloader improvements #1487 #1501
• Improved data type compatibility with all SQL databases #1496 #1424 #1465 #1467 #1469
• Add support to display the raw SQL query being fired along with the time it took to get the result. #1120
• Added a DockerCompose file for deploying SC with docker #1253

To see the complete list of enhancements/fixes, check out the v0.21.0 milestone.

Contributors

A special thanks to @narayandreamer for redesigning out website (link: https://spaceuptech.com)

Upgrade guide

Follow the steps to migrate from v0.20.0 and above:

• Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
• Backup setup configuration (space-cli inspect sc-setup-config.yaml)
• Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.
• Make sure you run Reload Schema in Database > Settings for each SQL database you've added in SpaceCloud.

Ping us on #general of our Discord server, if you face any issues while migrating.

v0.20.1

This is a minor release of Space Cloud that has a few improvements and bug fixes.

• Added bit(1) support in MySQL and fixed runner related errors when using gateway standalone #1453
• Optimized links to use native joins wherever possible #1422
• Added support to aggregate fields of joint tables #1421

To see the complete list of enhancements/fixes, check out the v0.20.1 milestone.

Upgrade guide

Follow the steps to migrate from v0.20.0:

• Backup your current config using space-cli (space-cli --project <project_id> get all /path/to/backup/dir)
• Backup setup configuration (space-cli inspect sc-setup-config.yaml)
• Download the latest version of space-cli (Linux | Windows | Mac) and run space-cli update -f sc-setup-config.yaml.

Ping us on #general of our Discord server, if you face any issues while migrating.

v0.20.0

This is a major release of Space Cloud that has tons of improvements and a few breaking changes.

Revamped eventing architecture

Space Cloud now uses a CDC (Change Data Capture) based eventing mechanism to capture database events reliably. Space Cloud uses Debezium and Redis under the hood to implement a reliable and performant eventing system.

Perks

• Eventing works even for mutations made directly to the database from outside of Space Cloud.
• All the previous limitations are gone. Events would be captured even if mutations are made without the primary key in the where clause or even if the primary key is not of type ID.
• Stronger guarantees and reliability.

New data types

Thanks to the new eventing architecture, eventing is not tied to specific data types anymore. Hence, we have added a few data types that were asked for a lot of time:

• Date
• Time
• Autoincrementing/Serial primary keys

More data types will be coming in the next releases.

Event-driven auto-scaling

We have added support for KEDA (Kubernetes Event-Driven Autoscaling) to Space Cloud. This means you can now autoscale your services based on:

• Requests per second
• Active requests
• CPU consumption
• Memory consumption
• CRON schedule
• Tons of other events (e.g. number of pending items in Kafka, SQL query output from Postgres, etc.), all thanks to KEDA!

Dropped Docker Support

As discussed and concluded in various community calls before, we have dropped the support for Docker as a target of the deployments module in Space Cloud. Space Cloud can now deploy services to Kubernetes only.

Dropping docker support would go a long way for us in developing and maintaining the deployments module. It would also help us to focus more on k8s and its ecosystem.

Caching module ⚡️

We have introduced a Redis based caching module in v0.20.0 that can cache responses from databases, ingress routes and remote services. It supports TTL based caching as well as instant invalidation.

Note: Caching is a part of our enterprise version.

Other notable enhancements

• Conditional event triggers #1392
• Support for configuring underlying database driver #1023
• Default limit clause in every ready query #1338
• Support for specifying kid in JWT secrets #1405
• Support for overriding token claims in event triggers #1389
• Added support for search in all resources in Mission Control

To see the complete list of enhancements/fixes, check out the v0.20.0 milestone.

Upgrade guide

Follow the steps to migrate from the previous versions to v0.20.0:

• Backup your current config using space-cli version 0.19.X. (space-cli --project <project_id> get all /path/to/backup/dir)
• Delete the existing SC setup using kubectl delete -f https://raw.githubusercontent.com/spaceuptech/space-cloud/v0.19.7/install-manifests/kubernetes/local/space-cloud.yaml
• Download the latest space-cli. (Linux | Windows | Darwin). This latest space-cli should be used from now for the further operations.
• Make sure kubectl is pointing to the right k8s cluster and run space-cli setup.
• Apply the backup config using space-cli apply /path/to/backup/dir

Ping us on #general of our Discord server, if you face any issues while migrating.

v0.19.7

This release contains a minor bugfix in ingress routes:

• Gateway ended up following redirects from ingress routes #1394

Upgrade guide

Upgrade is possible from v0.17.0 and above.

Before upgrading your cluster, make sure you backup cluster config using space-cli --project <project_id> get all /path/to/backup/dir. If things go right, you'll be able to reapply all saved project config using space-cli apply /path/to/backup/dir.

For Docker-based deployments:

Simply run space-cli upgrade.

For Kubernetes based deployment:

We recommend setting up a fresh Kubernetes cluster and installing Istio and SC on top of it. Don't forget to backup all project config first!