Developer Portal
New Features
- When viewing a cluster that does not come with a preinstalled ingress we now show a message explaining why and include a link to get more information. (#1079)
Changes
- We’ve made a change to avoid showing the upgrade available message for incompatible version jumps on AWS. (#1083)
- The names of node pools are now truncated only if there is not enough space to display them (#1084)
- The kubeconfigs generated when creating a keypair are now aligned with what gsctl produces. They now have cluster specific values for the name, username, and context fields (#1073)
Bug Fixes
- Improve how we deal with clusters that have been deleted. (#1086)
- Fixed certain issues on the cluster detail page (#1082, #1062, #1059)
- Fixed invite modal logic (#1072) (This is relevant only to Giant Swarm staff, customers are not able to invite users)
- Reduce the number of api calls made when switching organizations (#1060)
Dev changes / Refactorings
Note: We’ve started adding
vto our tags, because that is the recommended practice and how other repos throughout Giant Swarm do it too!Changes
- Instead of waiting for all requests to finish, we render the cluster overview immediately with some placeholders for things like CPU, RAM, Nodecount. (#1048, #1036)
Bugfixes
- Fixed a crash when trying to render clusters with an unknown instance type (#1058)
- Corrected the endpoint used when upgrading our latest (v5) clusters (#1057)
- Fixed various display issues in the cluster detail view (#1056, #1053, #1054, #1037)
- Fixed an error after creating clusters with an older version (#1051)
- Fixed a bug when deleting clusters that could cause it to reappear in a deleted state. (#1035)
Dev Changes
Changes
- Show helpful errors and validation when creation organizations (#1006)
- Remove BETA tag from Home (#1020)
Bugfixes
- Fixed a problem with the upgrade modal not closing after an upgrade (#1026)
- Fixed cluster list when accessed from organization details of a not initially selected org (#1004)
- Fixed loading all clusters when in detail view (#1022)
- Fixed the copy to clipboard functionality in the code blocks (#1011)
Dev Changes
- Load node pools for selected organization only (#1010)
- Fix pre-commit formatting not running on staged files (#1007)
- Minor refactor cluster status call (#1009)
- Refactor ensureWorkersHaveKey (#1012)
- Update dependencies (#1017, #1029, #1018, #1030)
- Added and improved testing (#964, #998, #994, #1032)
- Refactor computeCapabilities and add hasOptionalIngress (#1021)
- Remove deprecated version checks (#1028)
- We’ve changed how cluster resources are calculated behind the scenes (#1033)
Changes
- Happa now ensures that certain apps (like the ingress app) can only be installed in the right namespace.
Bugfixes
- We fixed a bug in the getting started guide.
Greetings fellow Happa users and Happa followers. It is now possible to set an App’s secret while installing it! Before this, it was possible to upload a secret for an app, but only after creating it. That meant you’d potentially have a misconfigured app for a moment, which isn’t ideal. Now the install app modal contains a field for uploading your Secrets file too!
Other than that, Happa 0.10.7 brings quite a lot of behind the scenes development work to the table.
We’ve discussed internally the future of Happa’s codebase extensively, and these decisions are starting to be implemented and are now finding their way into the codebase.
Changes:
- It is now also possible to supply a secret when creating an app (#877)
Bugfixes:
- Fixed an issue when editing node pool names regarding truncation (#969)
- Fixed the CPU and RAM label showing “0” when loading a ‘v4’ cluster. (#970)
- Fixed a bug when loading keypairs (#985)
- Fixed an infinite loop that could occur in the availability zone component (#992)
Dev Changes
- Internal data handling now uses await instead of promises and has been refactored (#928, #991, #982, #997)
- Added some more tests around the organization management feature. (#958, #963)
- Updated various dependencies (#961, #966, #916, #972, #981, #996)
- Various code style improvements and changes (#957, #944)
- Use latest node version in our CI (#967)
- Include the sha of the deployed Happa instance in our exception notification (#984, #995)
- We decided to pin all dependencies in the package.json file (#983)
Changes
- We updated to a new version of
handlebarsnot affected by CVE-2019-19919 - We updated
eslint-plugin-emotion - We improved the way our Copy to Clipboard features work internally
- We updated to a new version of
Bugfixes
- We fixed an exception when clicking on availability zone labels.
- We fixed a bug when trying to create apps on newer clusters.
Changes
We removed the BETA tag next to the notice that lists refresh. This was intended to indicate that the refreshing of lists was still an experiment. Happa itself is not in BETA.
Some of our labels flash to indicate that new data has arrived, this used to be triggered on first view of those labels. We’ve changed that so now they only flash when new data comes in, instead of at initial viewing.
Bugfixes
- We fixed an issue with loading of the app catalog.