Upgrade notes

• Some labels have changes on the cluster-bootstrap-controller deployment (#1171). If the weave-gitops-enterprise HelmRelease stalls, delete the cluster-bootstrap-controller deployment.
• You may see some clusters stuck in waiting for access secret to be deleted during WGE upgrade. See the workaround in the issue here.

Dependency versions

• weave-gitops v0.9.1
• cluster-controller v1.2.0
• cluster-bootstrap-controller v0.1.0

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

Progressive Delivery

Flagger is a fully supported component within Weave GitOps Enterprise and allows you to reduce risk when rolling out updates to applications. A new Delivery view has been added to Weave GitOps Enterprise to help you better understand your progressive delivery rollouts.

• View a list of configured Canary objects across your fleet of clusters, including their status, configured deployment strategy, and the current live application image.
• Debug issues with the event log showing a full history of a deployment.
• Discover all flagger-generated objects to better understand its operation.
• Easily link back to the Flux objects responsible for the reconciliation of your application, to bridge the gap between Flux and Flagger.

• PR: #1094 - [UI] Replace profile section with table
• PR: #1170 - fix: remove cluster name from HelmRelease name
• PR: #1112 - Add endpoint to add workloads to a cluster
• PR: #1137 - Flag for editing values in Required Profiles
• PR: #1065 - [UI] Simplify Create a Cluster form
• PR: #1116 - Upgrade to weave-gitops v0.9.1-rc.1
• PR: #1081 - Improve Canary Yaml view
• PR: #1108 - Listing canary managed objects
• PR: #1133 - feat: add gitops cmd and poliy tenancy
• PR: #1107 - 1093 Added canary analysis tab with canary metrics section
• PR: #1139 - 1136 using consistent yaml view for canary metric templates
• PR: #1143 - Move details section to separate component
• PR: #1104 - Update /v1/clusters to accept a list of workloads
• PR: #1154 - Upgrade to weave-gitops v0.9.1-rc.2
• PR: #1155 - Fix up a snyk-detected CVE
• PR: #1042 - Return both CAPITemplate and GitOpsTemplates by default from /v1/templates
• PR: #1043 - Replace template table with filterable table
• PR: #1103 - Parse params from annotations.
• 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: #1022 - Decrease canaries poll interval
• PR: #1130 - Pd UI enhancement
• PR: #1132 - PD - Flagger generated objects
• PR: #1131 - add link to canary application details
• PR: #1161 - Flagger generated objects in Canary details should match other details views
• PR: #1038 - Show promoted image tag in ProgressiveDelivery table
• PR: #1056 - Update Policy details & violations details route
• PR: #1053 - move PD api endpoints to hooks
• PR: #1046 - UI: provide cluster namespace when fetching kubeconfig
• PR: #984 - Show events for a canary deployment
• 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: #1176 - Remove ssh known hosts file usage from dockerfile of clusters service
• PR: #1075 - fix: display correct canary progress
• PR: #1122 - Sanitize hrefs from annotations which can be changed by the user
• PR: #1123 - Fix canary details to display non-flux managed resources
• PR: #1144 - Fix bug with secret key lookup.
• PR: #1149 - Allowing services and hpa
• PR: #1160 - Fix UI break if there is no Key message in cluster condtitions
• PR: #1070 - reduce verbosity
• PR: #1088 - Improve template parsing and rendering
• PR: #1052 - Correct the namespace in the path we write files to.
• PR: #1047 - fix: set controlPlaneInitialized when available
• PR: #1054 - Update the CAPITemplate and GitOpsTemplate CRDs in the helm chart
• 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: #1117 - Test cross namespace multi violation occurance
• PR: #1183 - Add leaf cluster applications acceptance tests
• PR: #825 - Fixes demo-01 getting automatically updated
• PR: #1025 - Leaf cluster policies acceptance test
• PR: #1080 - Add violation leaf cluster acceptance test
• PR: #1049 - Fixes the acceptance tests on main
• PR: #945 - Add policies acceptance test
• PR: #993 - Violations acceptance test