Releases: giantswarm/object-storage-operator
Releases · giantswarm/object-storage-operator
v0.10.2
v0.10.1
Fixed
- Fix bucket creation in us-east-1.
v0.10.0
Changed
- Secure Azure Storage Account by making them private and accessible through an Azure Private Endpoint. This also requires the creation of a private DNS zone and A record.
- Update Kyverno PolicyException to v2beta1.
Removed
- Remove PSP.
v0.9.0
Added
- Add doc and unit tests using github copilot.
Fixed
- Disable logger development mode to avoid panicking, use zap as logger
- Fix
irsa domain
in China after we migrated the irsa domain tooidc-pod-identity-v3
.
v0.8.0
Added
- ReclaimPolicy added in the Bucket CR to manage the data clean up (retain or delete).
- Add a finalizer on the Azure secret to prevent its deletion.
- Empty all the objects in the S3 bucket in case of bucket deletion.
v0.7.0
Changed
- Change azure storage account secret name by using the bucket name instead of the storage account name to not be bothered by azure storage account name limitations (up to 24 characters) which truncates secret name for long bucket names like
giantswarm-glippy-mimir-ruler
which becomesgiantswarmglippymimirrul
. As this rule is unpredictable (depends on the installation name), it is better to fix the name of the secret.
v0.6.1
Fixed
- Fix object-storage-operator templating.
v0.6.0
Changed
- Add support for the region of China.
v0.5.5
Fixed
- Add basic tag key sanitization for azure bucket tags as they need to match c# identifiers.
v0.5.4
Fixed
- Fix KyvernoPolicyException to apply when podSecurityStandard is enabled.