[kusumachalasani]

Merge 0.0.8 release from mvp_demo to main

Summary by Sourcery

Publish the 0.0.8 operator release with updated component images, contributor documentation, and more reliable Prometheus setup checks.

Bug Fixes:

• Ensure Prometheus custom resource definitions are established before applying dependent manifests in PR checks.

Enhancements:

• Update the operator release and bundled component image versions from 0.0.7 to 0.0.8, including Autotune 0.12 and Optimizer 0.0.2.
• Add contributor guidance and community Slack resources to the project documentation.

CI:

• Improve Prometheus installation reliability in the PR validation workflow by waiting for all required CRDs to become available.

Documentation:

• Add CONTRIBUTING.md with contribution, build, testing, coding, and commit guidance.
• Document contribution resources and add a Kruize Slack QR code to the README.

Chores:

• Refresh release metadata and image references for the 0.0.8 operator bundle.

[sourcery-ai]

Reviewer's Guide

UI

Add a Slack community link and QR code to the README's contribution section.

• README.md L210-218
• docs/images/kruize_slack_QR.jpeg

Configuration

Bump the operator release version to 0.0.8 across the bundle, manager image configuration, and Makefile default.

• Makefile L6
• bundle/manifests/kruize-operator.clusterserviceversion.yaml L98-630 (4 small edits)
• config/manager/kustomization.yaml L8
• config/manifests/bases/kruize-operator.clusterserviceversion.yaml L8

Update the default Autotune and optimizer image versions in the sample and operator constants, alongside the bundle's corresponding image settings.

• bundle/manifests/kruize-operator.clusterserviceversion.yaml L18, L60
• config/samples/v1alpha1_kruize.yaml L11-13
• internal/constants/kruize_images.go L36, L42

Wait for the specific Prometheus CRDs to become established before applying Prometheus manifests.

• .github/workflows/pr-check.yaml L105-117

Documentation

Document the contribution workflow, build and test steps, commit conventions, and project resources.

• CONTRIBUTING.md L1-160

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 3 issues

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="bundle/manifests/kruize-operator.clusterserviceversion.yaml" line_range="105" />
<code_context>
     repository: https://github.com/kruize/kruize-operator
     support: Kruize Community
-  name: kruize-operator.v0.0.7
+  name: kruize-operator.v0.0.8
   namespace: placeholder
 spec:
</code_context>
<issue_to_address>
**Existing installations cannot upgrade**

When an OLM catalog contains both the previously released 0.0.7 bundle and this 0.0.8 bundle, the 0.0.8 CSV has no upgrade edge from 0.0.7, so OLM cannot resolve the upgrade and existing installations remain on the old release.

Set the 0.0.8 CSV to replace the 0.0.7 bundle.
</issue_to_address>

### Comment 2
<location path=".github/workflows/pr-check.yaml" line_range="112" />
<code_context>
+              customresourcedefinitions.apiextensions.k8s.io/podmonitors.monitoring.coreos.com \
+              customresourcedefinitions.apiextensions.k8s.io/probes.monitoring.coreos.com \
+              customresourcedefinitions.apiextensions.k8s.io/prometheuses.monitoring.coreos.com \
+              customresourcedefinitions.apiextensions.k8s.io/prometheusagents.monitoring.coreos.com \
+              customresourcedefinitions.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com \
+              customresourcedefinitions.apiextensions.k8s.io/scrapeconfigs.monitoring.coreos.com \
</code_context>
<issue_to_address>
**PR check stops before applying manifests**

When the PR check runs on a fresh cluster with the pinned kube-prometheus v0.13.0 setup, `kubectl wait` targets the `prometheusagents.monitoring.coreos.com` CRD, which the setup does not install, so the command exits nonzero and the workflow stops before applying the Prometheus manifests.

Remove the `prometheusagents.monitoring.coreos.com` CRD from the wait targets or ensure the setup installs it.
</issue_to_address>

### Comment 3
<location path="CONTRIBUTING.md" line_range="134" />
<code_context>
+## Code Style and Guidelines
+
+- Follow standard [Go conventions](https://google.github.io/styleguide/go/)
+- Run `gofmt` before committing: `gofmt -w ./...`
+- Keep changes focused — one logical change per commit and per PR
+- Add or update documentation in `docs/` for non-trivial changes
</code_context>
<issue_to_address>
**Documented formatting command fails**

When a contributor runs the documented command from the repository root, `gofmt -w ./...` treats `./...` as a literal path, not a Go package pattern, and exits because that path does not exist, so contributors cannot complete the documented formatting step.

Replace the command with one that passes Go source file paths to `gofmt`.
</issue_to_address>

Sourcery assessment

Approval pending. 2 findings to address first.

Blocking findings: bundle/manifests/kruize-operator.clusterserviceversion.yaml:105, .github/workflows/pr-check.yaml:112

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[khansaad]

LGTM