feat: enforce singleton Gpu CR

[vrdc-sap]

Description

Changes proposed in this pull request:

• enforce singleton Gpu CR

Related issue(s)
Make gpu cr singleton

[hyperspace-insights]

Summary

The following content is AI-generated and provides a summary of the pull request:

---

Enforce Singleton GPU CR

New Feature

✨ Enforces that only a single Gpu custom resource named "gpu" can exist per cluster. This is achieved via a CEL validation rule on the CRD as the primary gate, with an additional controller-side defense-in-depth check for scenarios where CEL admission is not in effect.

Changes

• api/v1beta1/gpu_types.go: Added a +kubebuilder:validation:XValidation marker to enforce that the Gpu CR name must be "gpu". Updated the type comment to reflect the singleton naming requirement.
• config/crd/bases/gpu.kyma-project.io_gpus.yaml: Regenerated CRD manifest to include the x-kubernetes-validations rule rejecting any Gpu resource not named "gpu". Updated the description accordingly.
• internal/controller/gpu_controller.go: Added the expectedCRName = "gpu" constant and a reconciler-side singleton check that marks misnamed CRs with a ForbiddenCRName condition and skips further reconciliation.
• internal/controller/conditions.go: Added the reasonForbiddenName = "ForbiddenCRName" condition reason constant alongside alignment formatting of existing constants.
• internal/controller/gpu_controller_test.go: Updated test GPU name from "test-gpu" to "gpu" to match the singleton requirement. Added a new singleton enforcement test verifying that creating a Gpu CR with any other name is rejected with the expected CEL error message.

Jira Issues

GitHub Issues:

• #55: Make gpu cr singleton

---

• 🔄 Regenerate and Update Summary
• ✏️ Insert as PR Description (deletes this comment)
• 🗑️ Delete comment

PR Bot Information

Version: 1.20.51

• Correlation ID: 00681b13-103c-4d43-9e40-d84d88791988
• Summary Prompt: Default Prompt
• Output Template: Default Template
• LLM: anthropic--claude-4.6-sonnet
• Event Trigger: pull_request.opened
• File Content Strategy: Full file content
• GithubContextProvider: Make gpu cr singleton #55

[hyperspace-insights]

The PR is well-structured and achieves its goal cleanly. The one substantive issue posted is that a rogue CR with a finalizer (added manually or through a future code change) could trigger reconcileDelete and invoke Installer.Uninstall, potentially uninstalling the legitimate GPU Operator — the singleton guard needs to be moved above (or merged with) the deletion-timestamp check to fully protect the deletion path.

PR Bot Information

Version: 1.20.51

• Correlation ID: 00681b13-103c-4d43-9e40-d84d88791988
• Agent Instructions:
  • CLAUDE.md
• LLM: anthropic--claude-4.6-sonnet
• Event Trigger: pull_request.opened
• File Content Strategy: Full file content