이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 5. Technology Previews
This section provides an overview of Technology Preview features introduced or updated in this release of Red Hat Ceph Storage.
Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information on Red Hat Technology Preview features support scope, see https://access.redhat.com/support/offerings/techpreview/.
5.1. The Cephadm utility
New Ceph Management gateway and the OAuth2 Proxy service for unified access and high availability
With this enhancement, the Ceph Dashboard introduces the Ceph Management gateway (mgmt-gateway
) and the OAuth2 Proxy service (oauth2-proxy
). With the Ceph Management gateway (mgmt-gateway
) and the OAuth2 Proxy (oauth2-proxy
) in place, nginx
automatically directs the user through the oauth2-proxy
to the configured Identity Provider (IdP), when single sign-on (SSO) is configured.
New Cephadm certificate lifecycle management for improved Ceph cluster security
With this enhancement, Cephadm now has certificate lifecycle management in the certmgr subsystem. This feature provides a unified mechanism to provision, rotate, and apply TLS certificates for Ceph services, supporting both user-provided and automatically generated cephadm-signed certificates. As part of this feature, certmgr periodically checks the status of all certificates managed by Cephadm and issues health warnings for any that are nearing expiration, misconfigured, or invalid. This improves Ceph cluster security and simplifies certificate management through automation and proactive alerts.
5.2. Ceph Dashboard
New OAuth2 SSO
OAuth2 SSO uses the oauth2-proxy
service to work with the Ceph Management gateway (mgmt-gateway
), providing unified access and improved user experience.
5.3. Ceph Object Gateway
Bucket logging support for Ceph Object Gateway with bug fixes and enhancements
Bucket logging was introduced in Red Hat Ceph Storage 8.0. Bucket logging provides a mechanism for logging all access to a bucket. The log data can be used to monitor bucket activity, detect unauthorized access, get insights into the bucket usage and use the logs as a journal for bucket changes. The log records are stored in objects in a separate bucket and can be analyzed later. Logging configuration is done at the bucket level and can be enabled or disabled at any time. The log bucket can accumulate logs from multiple buckets. The configured prefix
may be used to distinguish between logs from different buckets.
For performance reasons, even though the log records are written to persistent storage, the log object appears in the log bucket only after a configurable amount of time or when reaching the maximum object size of 128 MB. Adding a log object to the log bucket is done in such a way that if no more records are written to the object, it might remain outside of the log bucket even after the configured time has passed.
There are two logging types: standard
and journal
. The default logging type is standard
.
When set to standard
the log records are written to the log bucket after the bucket operation is completed. As a result the logging operation can fail with no indication to the client.
When set to journal
the records are written to the log bucket before the bucket operation is complete. As a result, the operation does not run if the logging action fails and an error is returned to the client.
You can complete the following bucket logging actions: enable, disable, and get.
Red Hat Ceph Storage 8.1 enhancements introduce several improvements to bucket logging, including support for source and destination buckets across different tenants, suffix/prefix-based key filtering, and standardized AWS operation names in log records. A new REST-based flush (POST) API has been added, along with the bucket logging info admin
command for retrieving logging configurations.
Fixes address concurrency issues causing multiple temporary objects, missing object size in certain cases, and retry attributes in race conditions. Additional safeguards now ensure that source and log buckets are distinct and that log buckets do not have encryption. Cleanup mechanisms have been improved to remove pending objects when source buckets are deleted, logging is disabled or reconfigured, or when target buckets are removed. Logging records now include missing fields related to authentication and transport layer information, ensuring more comprehensive logging capabilities.
Bugzilla:2308169, Bugzilla:2341711
Restore objects transitioned to remote cloud endpoint back into Ceph Object gateway using the cloud-restore
feature
With this release, the cloud-restore
feature is implemented. This feature allows users to restore objects transitioned to remote cloud endpoint back into Ceph Object gateway, using either S3 restore-object API or by rehydrating using read-through options.