forked from rook/rook
Blaine Gardner
88bf8dd475
Add a note about the upcoming potentially-breaking change to OBCs to the v1.17 release notes. This covers usage of `ROOK_OBC_ALLOW_ADDITIONAL_CONFIG_FIELDS` for OBC fields that some admins might not want exposed to users. Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com>
16 lines
738 B
Markdown
16 lines
738 B
Markdown
# v1.17 Pending Release Notes
|
|
|
|
## Breaking Changes
|
|
|
|
Object:
|
|
|
|
- Some ObjectBucketClaim options were added in Rook v1.16 that allowed more control over buckets.
|
|
These controls allow users to self-serve their own S3 policies, which many administrators might
|
|
consider a risk, depending on their environment. Rook has taken steps to ensure potentially risky
|
|
configurations are disabled by default to ensure the safest off-the-shelf configurations.
|
|
Administrators who wish to allow users to use the full range of OBC configurations must use the
|
|
new `ROOK_OBC_ALLOW_ADDITIONAL_CONFIG_FIELDS` to enable users to set potentially risky options.
|
|
See https://github.com/rook/rook/pull/15376 for more information.
|
|
|
|
## Features
|