Releases: Midburn/midburn-k8s
Releases · Midburn/midburn-k8s
v0.2.1
v0.2.0
v0.1.0
- add minikube environment #37
- added option to skip spark drupal login, enabled on production 1798bd6
- configure spark staging to work with test profiles server (test-profile2) (not exposed publically)
- Add gate force entry secret (#40)
- add tickets-sync pod - updates entered ticket states from spark to profiles (#41)
v0.0.9
v0.0.8
- Added camps index chart, continuously deployed to production and staging
- Deploy dreams to production
v0.0.7
v0.0.6
- finalize dreams deployment to staging environment (#21)
- added chatops server (#8)
- add spark recreate db script - to allow restarting staging from backup
- added pod autoscaler for spark deployment (deployed on staging and production)
- increased resources for spark and sparkdb
- set aws credentials for spark (#23)
- upgrade to large nodes (#25)
- enable persistent storage for metabase and set proper cpu limit
- added healthchecks on upgrade + upgrade_all and remove_all scripts to support creating test environments
v0.0.5
- added dreams external chart (#12)
- enabled on staging + continuous deployment from Midburn/Dreams
- finalized and deployed the business intelligence chart to production
- supports querying volunteers and spark production DBs
- misc. fixes and improvements
v0.0.4
v0.0.3
- added
profiles
external chart containing the drupal app and DB:- chart is enabled and deployed on staging see staging README for the profiles and db entrypoints
- chart is disabled on production
- images are based on production drupal, exported on
Jan 16, 2018
- drupal app is continuously deployed from https://github.com/orihoch/midburn-profiles-drupal
- DB is meant to be read only at the moment and is run from prepopulated image with full production data, it can be updated by supplying a full sql dump from production
- added business intelligence external chart - using metabase
- mostly ready but requires some more work and testing
- currently disabled on all environments
- upgrade traefik configuration to use route53 dns API for more robust certificate issuing and renewals
- due to changes in Let's encrypt, it's required now to use DNS for certificate challenge
- also upgraded the configuration to be more robust and stable in general