Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add cosi bucket kit helm chart #1534

Merged
merged 3 commits into from
Jan 3, 2025

Conversation

takirala
Copy link
Contributor

@takirala takirala commented Jan 3, 2025

What type of PR is this?

Add a utility helm chart that:

  • has an implicit dependency against cosi CRDs (it is users reponsibility to ensure cosi CRDs are already deployed).
  • can be deployed multiple times (e.g.: by multiple applications)
  • can create 0 or more instances for each of cosi CRs such as
    • BucketClass
    • BucketAccessClass
    • BucketClaim
    • BucketAccess
  • can create 0 or more for compatible cosi drivers. only ceph is supported for now. we can add support for azure and nutanix drivers in future if we desire. I am open to discussing if its worth it to move this driver out of this helm chart for seperation of concerns if you feel strongly about it.

What this PR does/ why we need it:

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


Checklist

  • If a chart is changed, the chart version is correctly incremented.
  • The commit message explains the changes and why are needed.
  • The code builds and passes lint/style checks locally.
  • The relevant subset of integration tests pass locally.
  • The core changes are covered by tests.
  • The documentation is updated where needed.

Signed-off-by: Tarun Gupta Akirala <[email protected]>
@takirala takirala merged commit 6219eff into mesosphere:master Jan 3, 2025
5 checks passed
@takirala takirala deleted the tga/cosibuckets branch January 3, 2025 16:53
github-actions bot pushed a commit that referenced this pull request Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants