Skip to content

Releases: MetaCell/cloud-harness

Cloud-Harness v2.4.0

08 Oct 08:52
Compare
Choose a tag to compare

With this release we introduce a few new features, updates, enhancements and bug fixes:

  • Support for docker-compose
  • Support update to Python 3.12 and Node 20
  • Neo4j browser
  • Application generation upgrades
    • Webpack to Vite
    • Fastapi/Django template improved in structure and clarity
  • Other enhancements and bugfixes (see changelog)

Full changelog

New Contributors

Full Changelog: v2.3.0...v2.4.0

Cloud-Harness v2.3.1

04 Jul 10:12
ac1f272
Compare
Choose a tag to compare

Hotfix release -- fixes typer dependency issue that prevents harness-deployment to run

What's Changed

New Contributors

Full Changelog: v2.3.0...v2.3.1

Cloud-Harness v2.3.0

26 Mar 11:37
df30a63
Compare
Choose a tag to compare

This new release introduces a few small features and bug fixes

  • Ingress setting to forward headers (now true by default)
  • Open Sentry init parameters in Python
  • Update PR template to match the new workflow based on Jira
  • Fix stage pipeline

See also https://metacell.atlassian.net/projects/CH/versions/10156/tab/release-report-all-issues

What's Changed

Full Changelog: v2.2.0...v2.3.0

Cloud-Harness v2.2.0

15 Jan 17:01
c460baa
Compare
Choose a tag to compare

This new release on CloudHarness introduces a few small features, fixes some bugs and improved documentation.

New features

  • Configure proxy timeouts and payload size #701

What's Changed

New Contributors

Full Changelog: v2.1.0...v2.2.0

Cloud-Harness v2.1.0

31 Jul 07:16
392fc28
Compare
Choose a tag to compare

Summary

This new release on CloudHarness introduces a few new features and fixes some bugs.

Main new features

See also https://github.com/MetaCell/cloud-harness/milestone/7?closed=1 to see the scope of the release

What's Changed

Full Changelog: v2.0.0...v2.1.0

Cloud-Harness v1.0.3

21 Dec 10:00
Compare
Choose a tag to compare

Summary

Add support to jupyterhub profiles

Upgrade instructions

Nothing to report.

Addressed issues:

What's Changed

Full Changelog: v1.0.0...v1.0.3

Cloud-Harness v2.0.0

08 Nov 15:05
3692dd7
Compare
Choose a tag to compare

What's Changed

  • Added testing framework
  • Added Django + FastAPI application templates
  • Accounts event listener
  • Test coverage improved
  • Update to Python 3.9
  • New Typing/model layer
  • Bug fixes

Detailed log:

New Contributors

Full Changelog: v1.0.1...v2.0.0

CloudHarness v1.0.1

12 Jul 16:16
3a84d5e
Compare
Choose a tag to compare

What's Changed

  • Fix to properly support jupyterhub communication to the accounts microservice

Full Changelog: v1.0.0...v1.0.1

CloudHarness v1.0.0

31 Mar 08:16
Compare
Choose a tag to compare

Version 1.0.0 includes general stability improvements and upgrades over the previous version.

Main changes

  • Upgrade Kubernetes specifications to v1 #342
  • Argo, JupyterHub (#342), Keycloak (#362), upgrade
  • Gatekeeper upgraded #130
  • Fix Keycloak user for backend api calls #361 #395
  • Build dependencies resolution improved (images that are not declared as build dependencies are not included) #346
  • Node affinity selectors per for JupyterHub applications #327
  • Efficiency improvements #422
  • Bug fixes #265 #216 #423 #222 #347 #380 #394

See also https://github.com/MetaCell/cloud-harness/milestone/5

Upgrading from previous version

No major api update is implemented from 0.4.0.

The upgrade can break the deployments for the following reasons:

  • Kubernetes definitions upgrade to v1. Kubernetes versions < 1.19 are not supported anymore.
  • Keycloak version upgraded to 15.1.1. Deployments with old Keycloak versions may break in a hot upgrade. See also https://www.keycloak.org/docs/latest/upgrading/
  • Applications using the user accounts client api is now required to add accounts as a hard dependency
  • JupyterHub helm chart upgraded. Some overridden configurations may need changes
  • Argo helm chart changed. Some overridden configurations may need changes
  • Default databases version changes from latest to a specific version. May need to set the desired version globally or specifically per application
  • Directory utilities renamed to tools. Codefresh pipelines may need to change the install command. Change the deployment-configuration/codefresh-ENV.yaml to replace utilities with tools and regenerate the deployment with harness-deployment ... -e ENV

What's Changed

New Contributors

Full Changelog: v0.4.0...v1.0.0-RC

CloudHarness v1.0.0 Release Candidate

14 Feb 09:56
8dc5ddb
Compare
Choose a tag to compare
Pre-release

Version 1.0.0 includes general stability improvements and upgrades over the previous version.

Main changes

  • Upgrade Kubernetes specifications to v1 #342
  • Argo, JupyterHub (#342), Keycloak (#362), upgrade
  • Gatekeeper upgraded #130
  • Fix Keycloak user for backend api calls #361 #395
  • Build dependencies resolution improved (images that are not declared as build dependencies are not included) #346
  • Node affinity selectors per for JupyterHub applications #327
  • Efficiency improvements #422
  • Bug fixes #265 #216 #423 #222 #347 #380 #394

See also https://github.com/MetaCell/cloud-harness/milestone/5

Upgrading from previous version

No major api update is implemented from 0.4.0.

The upgrade can break the deployments for the following reasons:

  • Kubernetes definitions upgrade to v1. Kubernetes versions < 1.19 are not supported anymore.
  • Keycloak version upgraded to 15.1.1. Deployments with old Keycloak versions may break in a hot upgrade. See also https://www.keycloak.org/docs/latest/upgrading/
  • Applications using the user accounts client api is now required to add accounts as a hard dependency
  • JupyterHub helm chart upgraded. Some overridden configurations may need changes
  • Argo helm chart changed. Some overridden configurations may need changes
  • Default databases version changes from latest to a specific version. May need to set the desired version globally or specifically per application
  • Directory utilities renamed to tools. Codefresh pipelines may need to change the install command. Change the deployment-configuration/codefresh-ENV.yaml to replace utilities with tools and regenerate the deployment with harness-deployment ... -e ENV

What's Changed

New Contributors

Full Changelog: v0.4.0...v1.0.0-RC