Skip to main content
Version: 0.13.0

Releases enterprise


This page details the changes for Weave GitOps Enterprise and its associated components. For Weave GitOps OSS - please see the release notes on GitHub.




GitOps Templates Path feature

  • GitOps templates now provide the capability to write resources to multiple paths in the Git repository. This feature allows complex scenarios, like for example creating a self-service for an application that requires an RDS database. We’ve provided documentation which has a example.
- path: ./clusters/${CLUSTER_NAME}/definition/cluster.yaml
- apiVersion:
kind: Cluster
- apiVersion:
kind: AWSCluster
- path: ./clusters/${CLUSTER_NAME}/workloads/helmreleases.yaml
- apiVersion:
kind: HelmRelease
name: ${CLUSTER_NAME}-nginx
- apiVersion:
kind: HelmRelease
name: ${CLUSTER_NAME}-cert-manager

Workspace UI

  • Weave GitOps now provides a GUI for Workspaces.

Enhanced Terraform Table in UI

  • Weave GitOps now provides more details on the Terraform inventory GUI page. Adding the type and identifier fields to the inventory table, plus filtering and a 'no data' message.

Keyboard shortcuts for "port forwards" on GitOps Run

  • Weave GitOps now building and printing a list of set up port forwards.
  • Weave GitOps now opening the selected port forward URL on key press. Listening for keypress is performed with the package (other options required pressing Enter after a keypress, this catches just a single numeric keypress) and opening URLs with the package.

Minor fixes

[UI] Notifications Fixed provider page showing a 404.

Dependency versions

  • weave-gitops v0.13.0
  • cluster-controller v1.4.1
  • cluster-bootstrap-controller v0.3.0
  • (optional) pipeline-controller v0.8.0
  • (optional) policy-agent v2.2.0

Breaking changes

No breaking changes




We highly recommend users of v0.11.0 upgrade to this version as it includes fixes for a number of UI issues.

GitOps Templates

  • Support to specify Helm charts inside the CRD, instead of annotations. We’ve provided documentation which has a example.
- chart: cert-manager
version: v1.5.3
editable: false
required: true
targetNamespace: cert-manager
layer: layer-1
labels: cert-manager
  • Ability to edit all fields now, including name/namespace

Authentication with OIDC support

Supporting custom OIDC groups claims for azure/okta integration Support for OIDC custom username and group claims:

claimUsername: ""
claimGroups: ""

Policy commit-time agent

  • Support Azure DevOps and auto-remediation in commit-time enforcement.

Admin User- simpler RBAC

  • Weave GitOps default admin user can now “read” all objects. Why is this important? As users are trying out Weave GitOps they will most likely try it out with some of their favorite Cloud Native tools such as Crossplane, Tekton, Istio, etc. This enables them to see all of those resources and explore the full power of Weave GitOps. We still do not recommend this user for “production-use” cases, and customers should always be pushed towards implementing OIDC with scoped roles.

Pipelines - adding Pipelines through Templates

  • From the Pipelines view you can add new Pipelines in a way which leverages GitOpsTemplates, additionally - to help users configure these, we’ve provided documentation which has some samples.

Support for multiple Flux instances on a single cluster

  • Support for running multiple flux instances in different namespaces on a single cluster for resource isolation.

Minor fixes

Terraform CRD Error Users of the Terraform Controller will be pleased to know we’ve addressed the issue where an error would be displayed if it had not been installed on all connected clusters.

Management cluster renaming If the name of the cluster where Weave GitOps Enterprise is installed, was changed from the default of management through the parameter, certain workflows could fail such as fetching profiles, this has now been resolved.

Dependency versions​

weave-gitops v0.12.0 cluster-controller v1.4.1 cluster-bootstrap-controller v0.3.0 (optional) pipeline-controller v0.0.11 (optional) policy-agent 2.1.1

Known issues

  • [UI] Notifications provider page shows a 404.





  • We are working towards unifying CAPI and GitOps Templates under a single umbrella. For those already using CAPITemplates, we will ensure a smooth transition is possible by making use of a conversion hooks. There are some breaking changes for GitOpsTemplates as part of this transitionary period, so be sure to check the guidance under Breaking Changes.
  • We now retain the ordering of parameters in the template instead of sorting them alphabetically. Providing to the author control in what sequence the parameters are rendered in the form and thus present a more logically grouped set of parameters to the end consumer.
  • You can control what delimiters you want to use in a template. This provides flexibility for if you want to use the syntax for dynamic functions like the helper functions we support.


  • This feature is now enabled by default when you install the Weave GitOps Enterprise Helm Chart. You can toggle this with the enablePipelines flag.
  • GitOpsTemplates are a highly flexible way to create new resources - including Pipelines. We now provide a shortcut on the Pipelines table view to navigate you to Templates with the label.


This release incorporates anonymous aggregate user behavior analytics to help us continuously improve the product. As an Enterprise customer, this is enabled by default. You can learn more about this here.

Dependency versions

  • weave-gitops v0.11.0
  • cluster-controller v1.4.1
  • cluster-bootstrap-controller v0.3.0
  • (optional) pipeline-controller v0.0.11
  • (optional) policy-agent 2.1.1

Breaking changes

GitOpsTemplates and CAPITemplates

We are making these changes to provide a unified and intuitive self-service experience within Weave GitOps Enterprise, removing misleading and potentially confusing terminology born from when only Clusters were backed by Templates.

New API Group for the GitOpsTemplate CRD

  • old:
  • new:

After upgrading Weave GitOps Enterprise which includes the updated CRD:

  1. Update all your GitOpsTemplates in Git changing all occurrences of apiVersion: to apiVersion:
  2. Commit, push and reconcile. They should now be viewable in the Templates view again.
  3. Clean up the old CRD. As it stands:
    • kubectl get gitopstemplate -A will be empty as it is pointing to the old CRD.
    • kubectl get -A will work To fix the former of the commands, remove the old CRD (helm does not do this automatically for safety reasons):
    • kubectl delete crd
    • You may have to wait up to 5 minutes for your local kubectl CRD cache to invalidate, then kubectl get gitopstemplate -A should be working as usual

Template Profiles / Applications / Credentials sections are hidden by default

For both CAPITemplates and GitopsTemplates the default visibility for all sections in a template has been set to "false". To re-enable profiles or applications on a template you can tweak the annotations

annotations: "true" # enable profiles "true" # enable applications "true" # enable CAPI credentials

The default values for a profile are not fetched and included in a pull-request

Prior to this release WGE would fetch the default values.yaml for every profile installed and include them in the HelmReleases in the Pull Request when rendering out the profiles of a template.

This was an expensive operation and occasionally led to timeouts.

The new behaviour is to omit the values and fall back to the defaults included in the helm-chart. This sacrifices some UX (being able to see all the defaults in the PR and tweak them) to improve performance. There should not be any final behaviour changes to the installed charts.

You can still view and tweak the values.yaml when selecting profiles to include on the "Create resource (cluster)" page. If changes are made here the updated values.yaml will be included.




  • Retain template parameter ordering.
  • Allow configuration of the delimiters in templates.
  • Add create a pipeline button.
  • add missing support for policy version v2beta2 to tenancy cmd.

Dependency versions

  • weave-gitops v0.10.2
  • cluster-controller v1.4.1
  • cluster-bootstrap-controller v0.3.0
  • (optional) policy-agent 2.1.1




  • Create non-cluster resources / Add Edit option to resources with create-request annotation

  • bump pipeline-controller

  • Parse annotations from template

  • Add cost estimate message if available

  • Adds support for showing policy modes and policy configs in the UI

  • Show suspended status on pipelines detail

  • YAML view for Pipelines

  • Align and link logo

  • Actually remove the watcher from the helm-watcher-cache

  • UI 1817 disable create target name space if name space is flux system

  • Adding edit capi cluster resource acceptance test

  • Add preview acceptance test

Dependency versions

  • weave-gitops v0.10.1
  • cluster-controller v1.4.1
  • cluster-bootstrap-controller v0.3.0
  • (optional) policy-agent 2.0.0




  • When adding applications, you can now preview the changes(PR) before creating a pull request
  • You can now see included Cluster Profiles when previewing your Create Cluster PR
  • Notifications are now available in the Notifications Page
  • You can now automatically create namespace when adding applications

Dependency versions

  • weave-gitops v0.9.6
  • cluster-controller v1.3.2
  • cluster-bootstrap-controller v0.3.0
  • (optional) policy-agent 1.2.1




  • Tenancy
    • gitops create tenant now supports --prune to remove old resources from the cluster if you're not using --export with gitops.
    • deploymentRBAC section in tenancy.yaml allows you to specify the permissions given to the flux Kustomizations that will apply the resources from git to your tenants' namespaces in the cluster.
    • Support for OCIRepository sources when restricting/allowing the sources that can be applied into tenants' namespaces.
  • Templates
    • Templates now support helm functions for simple transformations of values: {{ .params.CLUSTER_NAME | upper }}
    • Templates has moved to its own page in the UI, this is the first step in moving towards embracing them as a more generic feature, not just for cluster creation.
    • If a version is not specified in a template profile annotation it can be selected by the user.
    • A namespace can be specified in the template profile annotation that will be provided as the HelmRelease's targetNamespace by default.
  • Bootstrapping
    • A ClusterBootstrapConfig can now optionally be triggered when phase="Provisioned", rather than ControlPlaneReady=True status.

Dependency versions

  • weave-gitops v0.9.5
  • cluster-controller v1.3.2
  • cluster-bootstrap-controller v0.3.0
  • (optional) policy-agent 1.1.0

Known issues

  • [UI] Notifications page shows a 404 instead of the notification-controller's configuration.

⚠️ Breaking changes from v0.9.4

If using the policy-agent included in the weave-gitops-enterprise helm chart, the configuration should now be placed under the config key.


enabled: true
accountId: "my-account"
clusterId: "my-cluster"


enabled: true
accountId: "my-account"
clusterId: "my-cluster"