Skip to content

v0.9.0-rc.2

Pre-release
Pre-release
Compare
Choose a tag to compare
@github-actions github-actions released this 05 Jul 13:46
· 2588 commits to main since this release
ef77752

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

🔥 UI

  • PR: #1046 - UI: provide cluster namespace when fetching kubeconfig
  • PR: #984 - Show events for a canary deployment

🐛 Bugs

  • PR: #1047 - fix: set controlPlaneInitialized when available
  • PR: #1054 - Update the CAPITemplate and GitOpsTemplate CRDs in the helm chart
Uncategorized
  • PR: #1049 - Fixes the acceptance tests on main