Changed
- Migrated to be deployed via an app CR not a chartconfig CR
Changes and Releases
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Changes
On KVM installations, the minimum and default values for CPU Core and Memory size have been adjusted:
- The minimum has been raised from 1 CPU Core and 1 GB RAM to 2 CPU Cores and 3 GB RAM.
- The default is now 4 CPU cores and 4 GB RAM.
Bug Fixes
Fixes problems with logging in using a normal password.
Bug Fixes
- Improve issues with authentication and being logged out randomly in some cases. This mostly only affected Giant Swarm staff users.
Updated
- Use retagged images.
- Use ClusterIP for all services except proxy which uses LoadBalancer.
- Add support for an external PostgreSQL database.
Bug fixes
- Fix an issue with cluster scaling, where Happa would go completely blank after confirming the scaling dialog.
Bug Fixes
- Fixes a bug where the number of nodes and status such as CPU/RAM/Storage would not show up correctly, or flap periodically
Changes
- Various behind the scenes changes to prepare Happa for upcoming features.
Added
- Add first version of the kong-app chart based on the community Kong chart.
Updated
- Enable Kong Ingress Controller mode.
- Use service of type Load Balancer for the Kong proxy service.
- Disable using Postgres and use Kubernetes resources for storing state.
Changes
- On KVM installations, happa now shows additional explanation regarding the node’s storage size and it’s use.
- App catalogs now show additional labels, like
incubator,test,community.
Fixes
This release fixes a crash of the application that would occur after cluster creation.