1. Docs
  2. Changes and releases
  3. Web UI

Web UI

  • Web UI happa 0.10.7

    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)
  • Web UI happa 0.10.6

    Changes

    • Make happa docker image available in the Aliyun registry in China. (#931)
    • Use Azure-specific wording “VM size” in cluster details view. (#904)

    Bugfixes

    • Fixed payload structure for the API request to create a v5 cluster (release 10.x.x) that would cause a manually selected master node avaiability zone choice to be ignored. (#930)
    • Fixed a problem that prevented installing an app. (#954)
    • Cosmetic fixes. (#927, #940)
  • Web UI happa 0.10.5

    Changes

    • We updated to a new version of handlebars not affected by CVE-2019-19919
    • We updated eslint-plugin-emotion
    • We improved the way our Copy to Clipboard features work internally
  • Web UI happa 0.10.4

    Bugfixes

    • We fixed an exception when clicking on availability zone labels.
    • We fixed a bug when trying to create apps on newer clusters.
  • Web UI happa 0.10.3

    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.
  • Web UI happa 0.10.2

    Bugfixes

    We’ve rolled back part of a change introduced in #882, which was intended to reduce the amount of requests to our API. It had the unintended consequence of showing incorrect information on the organization overview, and when switching between organizations. (See #890)

  • Web UI happa 0.10.1

    Changes

    • We now only fetch details for clusters that are currently in view. Improving the load on our backend. (#882)

    • The cluster detail view now redirects to the cluster list when the cluster you are viewing is no longer able to be found, for example when someone else deletes it. (#815)

    • We’ve replaced a warning mentioning that we do not support or monitor clusters below three worker nodes (which is not the case) with a recommendation to have at least three worker nodes. (#865)

    Bugfixes

    • We’re no longer show pre-installed apps in the list of apps when viewing a cluster. This list is meant to show only the apps that you have installed yourself. (#871)

    Dev Changes

    We’re adding stricter linting and continue to improve the codebase consistency on various fronts.

  • Web UI happa 0.10.0

    New Features

    • Node Pool Support On installations that have node pools enabled (this is still a preview feature) Happa will show a new cluster creation form where you can create and edit node pools. The cluster detail screen is also updated, so that you can view and scale node pools after creating a cluster.

    • Cluster Deletion Date When deleting a cluster, our systems need time to fully remove all related resources. Sometimes deletion can be blocked due to an error or resource that we are unable to clean up. To help make this visible we’ve added the deletion date to the cluster list on the organization detail page. Clusters that are being deleted will show up in the list until all their resources are successfully removed by our operators. We’ll continue to iterate on this feature in an upcoming release.

    Changes

    • New cluster creation form: The cluster creation form has changed slightly to better suit the different types of clusters that Happa can create now depending on the installation.

    • The Giant Swarm logo in the top left now redirects to the dashboard instead of our website.

    • The App Catalog has seen a number of performance improvements.

    • Version links on the cluster detail page are underlined to show that they are interactive clickable elements.

    • The worker node limit is now enforced on KVM installations. In other words, it is no longer possible to create failing clusters that will not fit on your installation.

    Bugfixes

    • Navigating between organizations and the organization list using the back button works correctly now.

    • Opening organizations in a new tab using ctrl-click works correctly now.

    • Deep linking to an App in the App Catalog has been fixed.

    • Ingress Port Mappings for KVM installations are back. They were accidentally removed from the cluster detail screen.

    • We now show a checkmark in the organization list when that organization is configured to use custom credentials.

    Dev Changes

    We would also like to note that we’ve improved test coverage significantly and the overall development experience. We have also added exception notification to Happa. When an exception occurs, we will now be notified of it so that we can investigate and fix issues that were previously unreported.

  • Web UI happa 0.9.10

    Changes

    • It is now possible to upload the ‘secret values’ for an app from the App Detail modal on the ‘Apps’ tab of a cluster.

    • The maximum number of nodes allowed when creating a cluster has been increased from 99 to 999.

    • The styling of the validation messages on the cluster create screen is now more consistent.

    • Number picker buttons become disabled when increasing or decreasing would result in an invalid number.

    Other

    • Happa has been undergoing lots of internal changes and codebase improvements that should not affect your day to day use, but prepares it for future features and development
  • Web UI happa 0.9.9

    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.

This part of our documentation refers to our vintage product. The content may be not valid anymore for our current product. Please check our new documentation hub for the latest state of our docs.