Skip to content

Releases: weaveworks/weave-gitops-enterprise

v0.0.9

23 Sep 16:01
34bff4f
Compare
Choose a tag to compare
v0.0.9 Pre-release
Pre-release

Entitlements

This is our first release that checks entitlements!

To start Weave Gitops Enterprise you'll have to load some valid entitlements into your cluster. Test/development entitlements are available for internal use.

Changes

  • Upgrades to Weave Gitops 0.2.5
  • Entitlement checking when WGE starts
  • [UI] New table view for templates
  • Improved logging

Known issues

  • The capi-server service account requires additional RBAC get/list privileges for each type of resource you have loaded into the cluster. This must be done manually for now. #108
  • Discovered post-release: [UI] Applications details page hangs / locks up in a infinite request loop. Fixed in 0.0.10

v0.0.8

22 Sep 10:10
738a2ff
Compare
Choose a tag to compare
v0.0.8 Pre-release
Pre-release

This release is missing a published helm chart, please continue to v0.0.9!

v0.0.7

06 Sep 10:25
ab9f743
Compare
Choose a tag to compare
v0.0.7 Pre-release
Pre-release

This is a polish / bug fix release. It is also the first release that integrates Weave GitOps Enterprise with Weave GitOps Core.

Docs

Check out the docs at https://docs.wkp.weave.works/docs/next/mccp/intro

New features

  • [UI] Ability to view Weave GitOps Core applications
  • [UI] Consistent look & feel
  • [UI] New design for notification
  • [UI] Server version now displayed

Fixes

  • [BE] ui-server no longer runs on port 80 for running on more locked down environments like OpenShift
  • [UI/CLI] Template parameter values are now validated
  • [CLI] Show template parameter options

Known issues

  • Deleting a PR from GitHub will not delete the row from the table on the Clusters page, this requires manual cleanup. (Cluster config -> disconnect -> remove from MCCP)
  • After deleting a CAPI cluster completely the Status will stay in Deletion PR and requires manual cleanup (config -> disconnect cluster)

Important Notes

  • To see the Cluster Status reflected in the UI the agent must be installed on the management cluster and connected back up to itself.

v0.0.6

23 Aug 07:33
82d5883
Compare
Choose a tag to compare
v0.0.6 Pre-release
Pre-release

This is a polish / bug fix release. It fixes some important bugs around cluster state transitions and adds the Deletion PR state.

Docs

Check out the docs at https://docs.wkp.weave.works/docs/next/mccp/intro

New features

  • [CLI] Support for filtering templates by their provider
  • Telemetry data now being reported to bi.weave.works
    • The data being tracked is:
      • Listing CAPI templates
      • Creating clusters via pull requests
      • Deleting clusters via pull requests
    • No user data is tracked i.e. cluster/template names, only the action itself
    • Users can opt out
  • [UI] Default values for branch/commit-message/pr-description when creating a PR to create/delete clusters
  • [UI] New Weave-Gitops logo
  • [UI] Differentiate between "Creation PR" and "Deletion PR"!

Fixes

  • [UI] Only enable Create PR to Delete Clusters button if CAPI clusters are selected
  • [CLI/UI] Improved error messages for missing / badly formatted template params
  • [CLI/UI] Fixes wrong PRs being linked to "Creation PR" / "Deletion PR" link
  • [CLI/UI] Fixes pagination returning the correct number of clusters
  • [CLI/UI] Postgres support fixed!

Known issues

  • Deleting a PR from GitHub will not delete the row from the table on the Clusters page, this requires manual cleanup. (Cluster config -> disconnect -> remove from MCCP)
  • After deleting a CAPI cluster completely the Status will stay in Deletion PR and requires manual cleanup (config -> disconnect cluster)

Important Notes

  • To see the Cluster Status reflected in the UI the agent must be installed on the management cluster and connected back up to itself.