Skip to content

Conversation

@kvaps
Copy link
Member

@kvaps kvaps commented Jul 16, 2025

BucketName is publicly visible, while BucketClass is an internal construct used to define parameters.
To avoid exposing sensitive details, no internal information should appear in anything that is publicly accessible.

Following the CSI naming convention where each PVC is created with a name like

pvc-e4aa897f-eed6-4931-99e1-2cc50cdae1d4

This PR will change our logic to name backets the similar way:

bucket-e4aa897f-eed6-4931-99e1-2cc50cdae1d4

Backward compatibility

  • Existing buckets keep their original names; nothing breaks.
  • The new bucket- scheme is applied only to buckets created after this change.

@netlify
Copy link

netlify bot commented Jul 16, 2025

Deploy Preview for container-object-storage-interface ready!

Name Link
🔨 Latest commit d5a8da8
🔍 Latest deploy log https://app.netlify.com/projects/container-object-storage-interface/deploys/687816074083a000081ac957
😎 Deploy Preview https://deploy-preview-90--container-object-storage-interface.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 16, 2025
@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 16, 2025
@kvaps kvaps force-pushed the exclude-bucketClassName-from-bucketName branch from 0a63f3c to d5a8da8 Compare July 16, 2025 21:13
@kvaps kvaps changed the title Exclude bucketClassName from bucketName Prefix bucket names with bucket- using UID only Jul 16, 2025
@kvaps
Copy link
Member Author

kvaps commented Jul 16, 2025

/assign @jsafrane

kvaps added a commit to cozystack/cozystack that referenced this pull request Jul 17, 2025
Signed-off-by: Andrei Kvapil <[email protected]>

<!-- Thank you for making a contribution! Here are some tips for you:
- Start the PR title with the [label] of Cozystack component:
- For system components: [platform], [system], [linstor], [cilium],
[kube-ovn], [dashboard], [cluster-api], etc.
- For managed apps: [apps], [tenant], [kubernetes], [postgres],
[virtual-machine] etc.
- For development and maintenance: [tests], [ci], [docs], [maintenance].
- If it's a work in progress, consider creating this PR as a draft.
- Don't hesistate to ask for opinion and review in the community chats,
even if it's still a draft.
- Add the label `backport` if it's a bugfix that needs to be backported
to a previous version.
-->

## What this PR does

This PR updates COSI image and also includes these fixes:
-
kubernetes-sigs/container-object-storage-interface#89
-
kubernetes-sigs/container-object-storage-interface#90

### Release note

<!--  Write a release note:
- Explain what has changed internally and for users.
- Start with the same [label] as in the PR title
- Follow the guidelines at
https://github.com/kubernetes/community/blob/master/contributors/guide/release-notes.md.
-->

```release-note
[objectstorage] Update COSI controller and sidecar
```

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* Introduced automated image building and version injection for the
object storage controller, including support for both controller and
sidecar images.
* Added comprehensive Kubernetes CustomResourceDefinitions (CRDs) for
object storage resources, including Bucket, BucketClaim, BucketClass,
BucketAccess, and BucketAccessClass.
* Added a dedicated namespace and updated resource naming conventions
for improved clarity and consistency.

* **Bug Fixes**
* Improved and unified deletion handling for object storage resources,
ensuring proper cleanup and event recording.

* **Chores**
* Updated configuration and deployment manifests to use new image
locations and naming conventions.
* Added a configuration file for specifying the controller image used in
deployments.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Copy link
Member

@shanduur shanduur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/ok-to-test

@k8s-ci-robot k8s-ci-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Jul 18, 2025
@shanduur
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 19, 2025
@BlaineEXE
Copy link
Contributor

/approve
/lgtm

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BlaineEXE, kvaps

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 11, 2025
@BlaineEXE
Copy link
Contributor

As a note, the defined behavior in the v1alpha2 KEP is to use bc-<BucketClaim.UID>. As of today, we planned to not accept any more v1alpha1 changes into main, but since this is somewhat security-based, we will merge it while we can and backport to release-0.2

@k8s-ci-robot k8s-ci-robot merged commit 71fd1b7 into kubernetes-sigs:main Sep 11, 2025
8 of 11 checks passed
@BlaineEXE
Copy link
Contributor

/cherry-pick release-0.2

@k8s-infra-cherrypick-robot

@BlaineEXE: new pull request created: #129

In response to this:

/cherry-pick release-0.2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants