v0.9.0-rc.1

Known issues

• Setting namespace of cluster in create-cluster form writes out to wrong path in git #1051
• Policy details page on leaf clusters shows a 404 #1055

Breaking changes from 0.8.1

Directory structure includes GitopsCluster namespace

The new paths:

• ./clusters/management/clusters/namespace/cluster-name.yaml
• ./clusters/namespace/cluster-name/{profiles.yaml,flux-system/*.yaml}

During upgrade additional migration will be required:

• Update ClusterBootstrapConfig to include namespace in the path to the flux bootstrap command. Before doing this bootstrapping new clusters will not work.
• Move cluster.yaml files into new git layout and update leaf cluster gotk-sync.yaml files. Before doing this deleting existing clusters via the UI will not work. e.g.
  1. git mv clusters/management/clusters/my-cluster.yaml clusters/management/clusters/my-clusters-namespace/my-cluster.yaml
  2. vim clusters/my-cluster/flux-system/gotk-sync.yaml, and change Kustomization.spec.path to include the path:
     • old: ./clusters/my-cluster.yaml
     • new: ./clusters/my-clusters-namespace/my-cluster.yaml
  3. git commit and git push. The leaf clusters will now be an erroring state as the path is wrong
  4. Now move the leaf cluster flux-system into the correct path git mv clusters/my-cluster clusters/my-clusters-namespace/my-cluster
  5. git commit and git push. The leaf clusters errors should resolve as they can now find the files in the correct path.

createNamespace: true is set on created profiles

If a profile / helm-chart defines the release namespace explicitly in its templates, this should be removed.

Cluster readiness

A GitopsCluster now becomes ready when the Secret or Cluster object exists in the cluster.

go-template support in templates

The CAPITemplate CRD has been updated, make sure you have install.crds and upgrade.crds set in the weave-gitops-enterprise helm-release file so that the CRD is reloaded correctly.

spec:
  install:
    crds: CreateReplace
  upgrade:
    crds: CreateReplace

🚀 Enhancements

• PR: #917 - [UI] Individual cluster page
• PR: #934 - Progressive Delivery Flow - UI
• PR: #963 - feat: add policy violations multi cluster
• PR: #988 - add ingress template to helm chart
• PR: #994 - add config for service annotations on helm chart
• PR: #956 - Violation logs shows violations on leaf clusters
• PR: #989 - Compress http response
• PR: #952 - Go templating for CAPI templates
• PR: #992 - Add ListEvents endpoint
• PR: #954 - Clusters across namespaces
• PR: #1014 - Upgrade to core v0.9.0
• PR: #1016 - Upgrade to cluster-controller w/ finalizer

🔥 UI

• PR: #960 - [UI] Use useQuery for api calls
• PR: #1012 - WG902 Profiles are very slow to load on the create-a-cluster page

🐛 Bugs

• PR: #948 - chore: Bump progressive-delivery version
• PR: #922 - Reconcile the Default and management naming in the UI
• PR: #957 - Handle invalid annotations.
• PR: #977 - Ensure profile namespaces exist.
• PR: #959 - Updating a profile upgrades the CRD
• PR: #1009 - fix error message when missing entitlement

🧪 Tests

• PR: #945 - Add policies acceptance test
• PR: #993 - Violations acceptance test

Uncategorized

• PR: #967 - chore: Bump progressive-delivery version
• PR: #968 - fix: Add missing logger
• PR: #981 - fix: Remove feature flag from progressive delivery API
• PR: #962 - Add example front-end tests
• PR: #1011 - add section about managing multiple clusters
• PR: #965 - add validation for namespace in template PR creation
• PR: #1036 - [UI] Small fixes prior to release
• PR: #1035 - Fixes to clusters-in-any-namespace
• PR: #1039 - Add prerequisites to CONTRIBUTING
• PR: #1034 - Disable the "Delivery" item in the navbar so we can release