Update CLAUDE.md with tooling and RBAC guidance

[abyrne55]

Summary

Updates CLAUDE.md with essential development guidance based on recent work on the project.

Changes

Added new sections covering:

Code Generation and Tooling

• Controller-Gen Version Management: Guidance on ensuring local controller-gen version matches the version used to generate existing CRDs
• Boilerplate and Container Tools: Overview of boilerplate update process and container-based build commands
• Testing Workflow: Standard pre-commit testing commands

RBAC Model

• ClusterRole: Documents cluster-scoped resources and permissions
• Namespace-scoped Roles: Explains namespace-specific permissions for sensitive resources
• Key Principle: Clarifies the design choice to use namespace-scoped access for sensitive resources like Secrets

Motivation

These additions provide context that's helpful for any development work on the operator, whether fixing bugs or adding features. The documentation captures important patterns and constraints that weren't previously documented.

Testing

• ✅ CLAUDE.md syntax verified
• ✅ Information accuracy confirmed against actual codebase structure

---

🤖 Generated with Claude Code

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abyrne55

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [abyrne55]

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

[openshift-ci]

@abyrne55: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale