Skip to content

fix: generate manifest in conformance with the deployment spec #530

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 24, 2025

Conversation

dud225
Copy link
Contributor

@dud225 dud225 commented May 21, 2025

Summary by CodeRabbit

  • Chores

    • Updated chart version metadata and documentation references from 0.6.0 to 0.6.1.
  • Refactor

    • Adjusted deployment configuration to include the service name only for StatefulSet resources.

Copy link

coderabbitai bot commented May 21, 2025

Walkthrough

The changes update the graph-node Helm chart by incrementing the chart version from 0.6.0 to 0.6.1 and updating the version badge in the README accordingly. The Helm template logic is modified so that the serviceName field is included only when the resource kind is StatefulSet.

Changes

File(s) Change Summary
charts/graph-node/Chart.yaml, charts/graph-node/README.md Bumped chart version from 0.6.0 to 0.6.1 and updated version badge in README accordingly.
charts/graph-node/templates/graph-node/all.yaml Moved serviceName and podManagementPolicy fields inside conditional block for StatefulSet kind in Helm template.

Sequence Diagram(s)

sequenceDiagram
    participant Helm Chart
    participant Kubernetes API

    Helm Chart->>Kubernetes API: Deploy resource
    alt If kind == StatefulSet
        Helm Chart->>Kubernetes API: Include serviceName and podManagementPolicy in spec
    else Other kinds
        Helm Chart->>Kubernetes API: Exclude serviceName and podManagementPolicy from spec
    end
Loading

Estimated code review effort

2 (~15 minutes)

Suggested reviewers

  • cjorge-graphops
  • calinah

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7c30c01 and eaefb0a.

📒 Files selected for processing (3)
  • charts/graph-node/Chart.yaml (1 hunks)
  • charts/graph-node/README.md (1 hunks)
  • charts/graph-node/templates/graph-node/all.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • charts/graph-node/Chart.yaml
  • charts/graph-node/README.md
  • charts/graph-node/templates/graph-node/all.yaml

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

@dud225 dud225 force-pushed the graph_node_schema branch 2 times, most recently from f5759e9 to 7c30c01 Compare May 21, 2025 12:56
@dud225 dud225 changed the title Fix schema non-conformance fix: generate manifest in conformance with the deployment spec May 21, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
charts/graph-node/Chart.yaml (1)

25-25: Chart appVersion updated correctly; consider bumping chart version
The appVersion has been bumped from v0.38.0 to v0.39.0, which aligns with the new Graph Node release. Per Helm SemVer best practices, please also increment the chart’s version (currently 0.5.9) to 0.5.10 to reflect this change in the chart artifacts.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between da54e00 and 7c30c01.

📒 Files selected for processing (3)
  • charts/graph-node/Chart.yaml (1 hunks)
  • charts/graph-node/README.md (1 hunks)
  • charts/graph-node/templates/graph-node/all.yaml (1 hunks)
🔇 Additional comments (2)
charts/graph-node/README.md (1)

5-5: Update version badge for AppVersion
The README badge for AppVersion has been updated to v0.39.0, keeping it in sync with Chart.yaml.

charts/graph-node/templates/graph-node/all.yaml (1)

65-74: Conditionally include serviceName only for StatefulSet
The serviceName (and accompanying StatefulSet properties) has been moved inside the if (eq $values.kind "StatefulSet") block to prevent schema non-conformance for other kinds (e.g., Deployment). Verify that indentation under spec: remains correct and that rendering with helm template or helm lint succeeds for both resource kinds.

@cjorge-graphops
Copy link
Contributor

Hi @dud225 , sorry for the long time to reply. First of all, thank you for your contribution! 🥳
Graph-Node 0.39+ was pending for a while for two reasons: having the recommended version here updated (https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md), and then for breaking changes in the schema which required a dashboard update.

Would you be willing to rebase this to main and reduce it to the bugfix (which I very much would like to get in)? While bumping chart version a patch version up? 🙏

@dud225 dud225 force-pushed the graph_node_schema branch from 7c30c01 to eaefb0a Compare July 22, 2025 19:47
@dud225
Copy link
Contributor Author

dud225 commented Jul 22, 2025

@cjorge-graphops done

@cjorge-graphops
Copy link
Contributor

Thank you @dud225! for both your contribution and quick response ⭐ , much appreciated. Releasing this soon.

@cjorge-graphops cjorge-graphops merged commit f652063 into graphops:main Jul 24, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants