Weave GitOps provides insights into your application deployments, and makes continuous delivery with GitOps easier to adopt and scale across your teams.
check oidc-config
is introduced that validates a given OIDC configuration, either from a referenced Secret or from CLI flags. This will help users debug issues with Weave GitOps OIDC configuration as well as provide a way to validate a configuration before putting it on a cluster.Flux version | Minimum required |
---|---|
v2.0 |
>= 2.0.0 |
For Flux migrations to v2.0 see flux or weave gitops documentation.
gitops check
Flux version | Minimum required |
---|---|
v2.0 |
>= 2.0.0 |
For Flux migrations to v2.0 see flux or weave gitops documentation.
gitops
cli.Flux version | Minimum required |
---|---|
v2.0 |
>= 2.0.0 |
For Flux migrations to v2.0 see flux or weave gitops documentation.
create dashboard
command now accepts an additional --values
flag which can be used to populate values for the Weave GitOps Helm chart. This allows users to customise the resulting HelmRelease resource, according to their needs.We have also made minor changes in our CI workflows to make external contributions a little bit easier. Some workflows that required elevated permissions are now skipped for forks.
Finally, we have updated some of our UI libraries to protect against known vulnerabilities.
Flux version | Minimum required |
---|---|
v2.0 |
>= 2.0.0 |
For Flux migrations to v2.0 see flux or weave gitops documentation.
Flux version | Minimum required |
---|---|
v2.0 |
>= 2.0.0 |
For Flux migrations to v2.0 see flux or weave gitops documentation.
Flux version | Minimum required |
---|---|
v2.0 |
>= 2.0.0 |
For Flux migrations to v2.0 see flux or weave gitops documentation.
sourceRef
HelmRelease
details (as its on another cluster via spec.KubeConfig
)ImageAutomation
components to be used in EEFlux version | Minimum required |
---|---|
v2.0 |
>= 2.0.0 |
For Flux migrations to v2.0 see flux or weave gitops documentation.
This switches the storage from in-browser cookie storage, to using a session-based storage mechanism.
If you are running multiple replicas, you will run into issues with the lack of a shared session store.
This also means that when the gitops-server is restarted, the existing sessions will be lost (and will require that users can login again).
We are working to provide support for persistent session storage, and this will land in the next release.
With the switch to session-based storage, the issue where the ID Token was too big to be stored in a Cookie should be solved, this was commonly caused by Azure's use of UUIDs for groups in the OIDC groups claim.
Flux version | Minimum required |
---|---|
v2.0 |
>= 2.0.0 |
For Flux migrations to v2.0 see flux or weave gitops documentation.
We introduced a breaking change in this release by upgrading to Flux v2 APIs, notably GitRepository
v1, Kustomization
v1, and Receiver
v1. This means that this version of Weave GitOps is not compatible with previous versions of Flux v2, such as v0.41.x and earlier.
Follow Flux or Weave Gitops to upgrade to Flux v2 GA before upgrading Weave Gitops.
/releases
link with new /enterprise/getting-started/releases-enterprise/
urls/releases
link with new /enterprise/getting-started/releases-enterprise/
URLsFlux version | Minimum required |
---|---|
v2.0 |
>= 2.0.0 |
For migrations from v0.4x to v2.0 see this documentation.