Add watch verb for storageclasses

[kvaps]

this PR fixes the errors:

E0924 11:31:59.069472       1 reflector.go:150] pkg/mod/k8s.io/client-go@v0.30.2/tools/cache/reflector.go:232: Failed to watch *v1.StorageClass: unknown (get storageclasses.storage.k8s.io)
E0924 11:32:57.379956       1 reflector.go:150] pkg/mod/k8s.io/client-go@v0.30.2/tools/cache/reflector.go:232: Failed to watch *v1.StorageClass: unknown (get storageclasses.storage.k8s.io)
E0924 11:33:50.776342       1 reflector.go:150] pkg/mod/k8s.io/client-go@v0.30.2/tools/cache/reflector.go:232: Failed to watch *v1.StorageClass: unknown (get storageclasses.storage.k8s.io)
E0924 11:34:21.872401       1 reflector.go:150] pkg/mod/k8s.io/client-go@v0.30.2/tools/cache/reflector.go:232: Failed to watch *v1.StorageClass: unknown (get storageclasses.storage.k8s.io)

Summary by CodeRabbit

• New Features
  • Enhanced role permissions to include the ability to monitor changes to resources in real-time by adding the watch verb.
• Bug Fixes
  • Improved resource management capabilities for the EtcdClusterReconciler by updating permissions to allow watching of storage classes.

[coderabbitai]

Walkthrough

The changes involve updates to RBAC (Role-Based Access Control) permissions across multiple files. Specifically, the watch verb has been added to the rules for various roles, allowing them to monitor changes to resources in addition to the existing get and list permissions. This adjustment enhances the capabilities of the roles and the EtcdClusterReconciler struct, enabling real-time observation of resource states.

Changes

File Path	Change Summary
charts/etcd-operator/templates/rbac/...	Added watch verb to the rules section of clusterrole-manager-role.yml.
config/rbac/role.yaml	Added watch verb to the rules section of role.yaml.
internal/controller/etcdcluster_controller.go	Updated RBAC permissions for storageclasses in EtcdClusterReconciler to include watch.

Poem

In the garden where the bunnies play,
New powers bloom, bright as the day.
With a watchful eye, we see it all,
From tiny seeds to the tallest wall.
Hopping with joy, we cheer and prance,
For every change, a merry dance! 🐇✨

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e00e6cb and fc757da.

Files selected for processing (3)

• charts/etcd-operator/templates/rbac/clusterrole-manager-role.yml (1 hunks)
• config/rbac/role.yaml (1 hunks)
• internal/controller/etcdcluster_controller.go (1 hunks)

Additional comments not posted (4)

config/rbac/role.yaml (1)

113-113: LGTM: Addition of 'watch' verb for storageclasses is appropriate.

The addition of the 'watch' verb for storageclasses is consistent with the PR objective to "Add watch verb for storageclasses". This change allows the role to monitor changes to storageclasses in real-time, which can be beneficial for maintaining up-to-date information about storage resources in the cluster.

To ensure consistency across the file, let's check if other similar resources also have the 'watch' verb:

This script will help us verify if the addition of 'watch' to storageclasses is consistent with other resources in the file.

charts/etcd-operator/templates/rbac/clusterrole-manager-role.yml (1)

76-76: LGTM! Addition of 'watch' verb enhances monitoring capabilities.

The addition of the 'watch' verb for storageclasses is appropriate and consistent with other resources in this ClusterRole. This change allows the etcd-operator to monitor storageclasses in real-time, which can be beneficial for dynamic provisioning and management of storage resources.

internal/controller/etcdcluster_controller.go (2)

73-73: LGTM! Addition of 'watch' verb enhances real-time monitoring capabilities.

The addition of the watch verb to the RBAC permissions for storageclasses is a positive change. This enhancement allows the EtcdClusterReconciler to monitor storage classes in real-time, enabling more responsive and efficient handling of storage-related changes in the etcd cluster. The change is consistent with other RBAC annotations in the file and aligns well with the controller's responsibilities.

---

73-73: Verify plans for utilizing the new 'watch' capability

While the addition of the watch verb is beneficial, I noticed that the current implementation doesn't directly use this new capability. It would be helpful to confirm if there are plans to utilize this in upcoming features or if additional changes are needed to take advantage of this new permission.

To ensure this change will be utilized, you can run the following script to check for any TODO comments or upcoming feature plans related to watching storage classes:

Verification successful

'Watch' capability is being implemented through PR #266

The addition of the watch verb corresponds with the open pull request #266 titled "Add watch verb for storageclasses". This indicates that the new capability will be utilized in upcoming changes.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for TODO comments or feature plans related to watching storage classes

# Search for TODO comments or feature plans in Go files
rg --type go "TODO.*watch.*storageclass" -g '!vendor'

# Search for related issues or pull requests
gh issue list --search "watch storageclass"
gh pr list --search "watch storageclass"

Length of output: 221

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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>, please review it.
  -- Generate unit testing code 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.