Changes and Releases
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Fixed
- Fixed an infinite loading spinner issue when opening Happa. (We had to add support for ‘giantswarm’ authorization schemes in a new client we introduced while refactoring) (#1195)
Changed
- Remove an exclamation mark from the app detail pane in the cluster detail page. (#1194)
Added
- Add Pod Disruption Budget.
Changes
- Removed the “Browse Catalog” button and made the whole catalog repo clickable (#1177)
- We now autofocus on the cluster name input in the cluster creation screen (#1172)
Fixes
- Fixed redirection behaviour when visiting a cluster that no longer exists (#1165)
- We ‘accidentally a word’ on the cluster detail page in the custom credentials area (#1167)
- Show app name instead of object Object in flash and error to reducer (#1171)
- We now show an error when cluster creation fails (#1169)
- Fixed an exception when clicking on the availability zone icons in the cluster details screen (#1151)
Dev Changes / Refactorings
- Create model layer for the control plane API (#1145)
- In preparation of an upcoming feature we’ve added a version picker component, which is not yet implemented in its intended form. (#1164)
- Added various integration tests
- Clusters listing (#1176)
- User management page and modals (User management is a Giant Swarm staff only feature) (#1168)
- Reseting password (#1154)
- Ellipsis in members list and as a composable (#1170)
Added
- Allow custom forward configuration destination and options.
Changed
- Configured app icon. (#15)
Changed
- Upgrade to nginx-ingress-controller 0.30.0. (#31)
- Configured app icon. (#32)
- Enabled HorizontalPodAutoscaler by default. (#27)
- Based on HPA trials done so far, following settings have been adjusted to better fit actual observed usage profiles:
- CPU resource requests have been adjusted from 500m to 2 CPU
- 0.5 CPU was not enough for all the processes NGINX Ingress Controller starts
- Memory requests changed from 600Mi to 2.5GB
- Scaling out does not shard Ingress definitions and other configurations stored in memory of every nginx-ingress-controller replica
- Memory usage spikes during configuration reloads
- It improves the HPA stability
- Default number of nginx worker processes was changed from 4 to 1
- This reduced memory usage of each replica
- It didn’t affect request handling capacity
- Better defaults considering CPU requests and number of processes running on every nginx-ingress-controller replica.
- To avoid cluster-operator and HPA collision and nginx service disruption, this release also breaks with cluster-operator controllable nginx ingress controller Deployment replicas count
ingressController.replicas which was previously dynamically set by cluster-operator is now removed- New
controller.replicaCount config property is introduced, default replica count is set to 1, and then by default enabled HPA takes it over from there, by default scaling the Deployment in range of 1 to 20 replicas - If HPA gets disabled on-demand, replica count will stay static if not manually or automatically changed by some third party.
Added
- Add
autopath variable in the values file to make possible to configure or disable the plugin.