Updates for 0.31.0#3970
Closed
weave-gitops-bot wants to merge 6 commits intomainfrom
Closed
Conversation
Collaborator
Author
|
To change the release notes, edit the pull request description. As soon as you approve the PR, the release will start, and will be automatically merged when finished |
Collaborator
Author
|
Merging this will release a new helm chart. |
waleedhammam
approved these changes
Aug 30, 2023
Collaborator
Author
|
Merging this will release a new helm chart. |
waleedhammam
approved these changes
Aug 30, 2023
Contributor
|
Closing in favor of 0.31.1 as we've moved to yarn instead of npm and it needs timeout |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
💸 Features and improvements
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 compatibility
v2.0>= 2.0.0For Flux migrations to v2.0 see flux or weave gitops documentation.
🚀 Enhancements
🔥 UI
📖 Documentation
Uncategorized