Enable kubebuilder autoupdate plugin via github workflow

[asergeant01]

Proposed Changes

Enables kubebuilder autoupdate plugin and github workflow

Fixes #647

Summary by CodeRabbit

Release Notes

• Chores
  • Added automated weekly update workflow to check for and apply available updates
  • Configured automatic issue creation when updates are detected, streamlining the update process

[coderabbitai]

Walkthrough

A new GitHub Actions workflow is added to automatically update the Kubebuilder project scaffold, triggered manually or weekly on Tuesdays. The autoupdate plugin is enabled in the PROJECT configuration file.

Changes

Cohort / File(s)	Summary
Kubebuilder Auto Update Workflow .github/workflows/auto_update.yml	New workflow that runs kubebuilder alpha update with force, push, and restore-path flags, with configuration for git user, Go setup, and Kubebuilder installation. Supports opening GitHub issues for review.
Project Configuration PROJECT	Enables the autoupdate.kubebuilder.io/v1-alpha plugin in the PROJECT configuration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description follows the template with a 'Proposed Changes' section and issue reference, though the bullet points are replaced with inline text rather than a list format.
Linked Issues check	✅ Passed	The PR implements the requirement from issue #647 by adding the autoupdate-v1-alpha plugin to the PROJECT file and creating the corresponding GitHub Actions workflow.
Out of Scope Changes check	✅ Passed	All changes are directly related to enabling the kubebuilder autoupdate plugin and workflow as specified in issue #647; no extraneous modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately describes the main changes: enabling the kubebuilder autoupdate plugin and adding a GitHub workflow to support it.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch kubebuilder-autoupdate-plugin-workflow

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/auto_update.yml:
- Around line 44-49: Replace the unpinned "Install Kubebuilder" step to download
a specific Kubebuilder release matching the PROJECT cliVersion (e.g., 4.11.1)
and verify its checksum before installing: add a shell variable for the pinned
version (from PROJECT), download the corresponding kubebuilder tarball and its
SHA256SUM (or .sha256) from the official release URL, verify the checksum with
sha256sum (or similar) and exit on mismatch, then extract/move the binary and
run kubebuilder version; update the step that currently uses "latest" and the
kubebuilder installation flow so it fails fast on checksum verification and uses
the pinned version variable.

🧹 Nitpick comments (1)

.github/workflows/auto_update.yml (1)

38-41: Consider pinning Go to the repo’s supported version for reproducibility.
Using stable can change behavior when new Go versions are released. Aligning with go.mod improves determinism.

♻️ Example pin

     - name: Set up Go
       uses: actions/setup-go@v5
       with:
-        go-version: stable
+        go-version-file: go.mod