-
Notifications
You must be signed in to change notification settings - Fork 29
BucketClass API should use Protocol Object as first class object #15
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. In response to this:
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/test-infra repository. |
…code_ba Adding BucketAccess Add Functionality, Fix cmd controller and pass co…
…code_ba Adding BucketAccess Add Functionality, Fix cmd controller and pass co…
…readme updated README.md
…readme updated README.md
…readme-spec updated README.md and added spec.md
Bucket Class currently use Protocol as a string, we should change this to Protocol Structure for admins to specify specific information.
The text was updated successfully, but these errors were encountered: