Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reaper front end auth release notes #1270

Merged
merged 1 commit into from
Apr 5, 2024
Merged

Reaper front end auth release notes #1270

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG/RELEASE-NOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# k8ssandra-operator - Release Notes

## v1.12.0

It is now possible to disable Reaper front end authentication by adding either `spec.reaper.uiUserSecretRef: {}` or `spec.reaper.uiUserSecretRef: ""`.

This brings this API into line with our standard convention; which is that an absent/nil field will use the default behaviour of the operator (which is secure by default; i.e. with auth turned on) but that explicitly setting a zero value allows you to turn features off.

However, users with existing deployments which use auth should note that this new capability will result in their authentication being turned off, if - for some reason - they have set `spec.reaper.uiUserSecretRef` to the empty value. If you are in this situatin and want to keep auth turned on, you can simply remove the field `spec.reaper.uiUserSecretRef` entirely which will leave you with the default behaviour (auth enabled).

## v1.6.0

### Removal of the CassandraBackup and CassandraRestore APIs
Expand Down