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

Update README.md #40

Merged
merged 1 commit into from
Mar 21, 2024
Merged

Update README.md #40

merged 1 commit into from
Mar 21, 2024

Conversation

hoptical
Copy link
Collaborator

@hoptical hoptical commented Mar 21, 2024

Summary by CodeRabbit

  • Documentation
    • Updated deployment instructions for the Ceph S3 Operator, shifting focus from Makefile to Operator Lifecycle Manager (OLM) usage.
    • Added guidance on finding and installing the operator via OLM and Helm, including specific version changes for Helm upgrades.

@hoptical hoptical added the documentation Improvements or additions to documentation label Mar 21, 2024
@hoptical hoptical self-assigned this Mar 21, 2024
Copy link
Contributor

coderabbitai bot commented Mar 21, 2024

Walkthrough

The update transitions the deployment process of the Ceph S3 Operator from a Makefile-based approach to one that primarily utilizes the Operator Lifecycle Manager (OLM). This change streamlines the installation process and integrates Helm for specific operations, including version updates. The documentation has been reorganized to prioritize the OLM method, reflecting a shift towards more modern, Kubernetes-native deployment practices.

Changes

Files Change Summary
README.md Updated deployment instructions from Makefile to OLM and Helm; rearranged instructions for clarity

🐰✨
In the land of code and kube,
A rabbit hopped, with a geeky vibe.
"Farewell, Makefile," it cheerfully said,
"Hello, OLM, our new thread."
With Helm in hand and a skip in step,
It leaped ahead, with no regret.
🚀🌟

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@hoptical hoptical merged commit c68dd1a into main Mar 21, 2024
3 checks passed
@hoptical hoptical deleted the update/readme branch March 21, 2024 22:05
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 8f36325 and 40add15.
Files selected for processing (1)
  • README.md (1 hunks)
Additional comments: 4
README.md (4)
  • 32-34: The instructions for using OLM to install the Ceph S3 Operator are clear and concise. However, it would be beneficial to include a brief explanation of what OLM is and why it's recommended for managing Kubernetes operators, especially for readers who might be unfamiliar with it.
  • 41-41: The Helm upgrade command specifies version v0.3.7. Ensure this version aligns with the latest stable release of the Ceph S3 Operator and reflects any necessary updates or enhancements mentioned in the PR objectives.
Verification successful

The Helm upgrade command in the README.md correctly specifies version v0.3.7 for the Ceph S3 Operator, which aligns with the latest stable release according to the GitHub repository. The verification confirms that the documentation is up-to-date with the actual release version.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Verify the latest stable release version of the Ceph S3 Operator Helm chart
curl -s https://api.github.com/repos/snapp-incubator/ceph-s3-operator/releases/latest | jq -r '.tag_name'

Length of output: 112

* 44-50: The Makefile approach for deployment is still included in the README. Given the PR's objective to prioritize OLM and Helm for installation, consider removing this section or explicitly stating that it's a less recommended method compared to OLM and Helm. * 29-53: > 📝 **NOTE** > This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [128-128]

The phrase "feel free to" is commonly used but can be replaced with a more formal alternative to enhance the professionalism of the document.

Consider using "We welcome contributions. Please submit issues or pull requests." as an alternative.

Comment on lines 29 to 53
> Note: prior Ceph versions [don't support the subuser bucket policy](https://github.com/ceph/ceph/pull/33714). Nevertheless, other features are expected to work properly within those earlier releases.
- ClusterResourceQuota CRD: `kubectl apply -f config/external-crd`

### Using Makefile

Deploy using a simple command:
### Using OLM

```bash
make deploy
```
You can find the operator on [OperatorHub](https://operatorhub.io/operator/ceph-s3-operator) and install it using OLM.

### Using Helm

Deploy using Helm (version 3.8.0 or later), which supports OCI charts. To use the helm chart, edit the `values.yaml` file and set `controllerManagerConfig.configYaml` to your Ceph cluster configuration like [secret.yaml](config/manager/secret.yaml).

```bash
helm upgrade --install ceph-s3-operator oci://ghcr.io/snapp-incubator/ceph-s3-operator/helm-charts/ceph-s3-operator --version v0.3.6
helm upgrade --install ceph-s3-operator oci://ghcr.io/snapp-incubator/ceph-s3-operator/helm-charts/ceph-s3-operator --version v0.3.7
```

### Using OLM
### Using Makefile

You can find the operator on [OperatorHub](https://operatorhub.io/operator/ceph-s3-operator) and install it using OLM.
Deploy using a simple command:

```bash
make deploy
```

## Usage and Documentation

Copy link
Contributor

Choose a reason for hiding this comment

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

📝 NOTE
This review was outside the diff hunks, and no overlapping diff hunk was found. Original lines [91-93]

Consider changing "setup" to "set up" when used as a verb, to improve grammatical correctness.

- First setup the local Ceph cluster:
+ First set up the local Ceph cluster:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant