Skip to content
This repository was archived by the owner on Jan 23, 2026. It is now read-only.

add missing nodeport option#156

Merged
NickCao merged 1 commit intomainfrom
add-missing-nodeport
Aug 31, 2025
Merged

add missing nodeport option#156
NickCao merged 1 commit intomainfrom
add-missing-nodeport

Conversation

@bennyz
Copy link
Copy Markdown
Member

@bennyz bennyz commented Aug 31, 2025

Summary by CodeRabbit

  • New Features
    • Added support for exposing TLS/gRPC endpoints via NodePort. Users can now choose between ingress, route, or nodeport in chart configuration.
    • Updated chart validation to accept the new option, enabling deployments in clusters without ingress or route controllers.
    • Backward compatible: existing configurations continue to work unchanged; behavior only changes when nodeport is selected.

Signed-off-by: Benny Zlotnik <bzlotnik@redhat.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Aug 31, 2025

Walkthrough

Extended the Mode enum to include "nodeport" in both the Python model and Helm values schema, expanding accepted values from ["ingress","route"] to ["ingress","route","nodeport"]. No additional logic or structural changes.

Changes

Cohort / File(s) Change Summary
Mode enum expansion
deploy/helm/jumpstarter/charts/jumpstarter-controller/model.py, deploy/helm/jumpstarter/charts/jumpstarter-controller/values.schema.json
Added "nodeport" to Mode enum in Python model and Helm values schema validation, updating allowed values from ["ingress","route"] to ["ingress","route","nodeport"].

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

I thump my paws—new ports to note,
A nodeport now joins route and moat.
Three paths to warren, neat and tight,
Charts and models both aligned right.
I nibble docs, then hop away—
Enum expanded, ship today! 🥕🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch add-missing-nodeport

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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Copy link
Copy Markdown
Contributor

@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 (3)
deploy/helm/jumpstarter/charts/jumpstarter-controller/model.py (1)

225-229: Update docstring to mention NodePort

TLS port description still says “Ingress or Route”; include NodePort for consistency.

Proposed change (outside this hunk):

port: Optional[Port] = Field(
    None,
    description="Port to use for the gRPC endpoints via Ingress, Route, or NodePort; useful for ingress routers on non-standard ports",
)
deploy/helm/jumpstarter/charts/jumpstarter-controller/values.schema.json (2)

910-921: Clarify TLS port description to include NodePort

Mirror the model/doc change so users aren’t misled.

Proposed snippet (outside this hunk):

"port": {
  "anyOf": [{ "$ref": "#/$defs/Port" }, { "type": "null" }],
  "default": null,
  "description": "Port to use for the gRPC endpoints via Ingress, Route, or NodePort; useful for ingress routers on non-standard ports"
}

724-734: Optional: tighten NodePort range if routerPort maps to Service.spec.ports[].nodePort

If “routerPort” is a NodePort value, constrain to 30000–32767; otherwise ignore.

Proposed schema addition (outside this hunk):

"$defs": {
  "NodePort": { "minimum": 30000, "maximum": 32767, "title": "NodePort", "type": "integer" }
}

Then update:

"routerPort": { "anyOf": [ { "$ref": "#/$defs/NodePort" }, { "type": "null" } ], "default": null }
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a9298a5 and 484f5e3.

📒 Files selected for processing (2)
  • deploy/helm/jumpstarter/charts/jumpstarter-controller/model.py (1 hunks)
  • deploy/helm/jumpstarter/charts/jumpstarter-controller/values.schema.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: deploy-kind
  • GitHub Check: e2e-tests-28d6b1cc3b49ab9ae176918ab9709a2e2522c97e
  • GitHub Check: e2e-tests (ubuntu-24.04)
  • GitHub Check: e2e-tests (ubuntu-24.04-arm)
  • GitHub Check: lint-go
  • GitHub Check: tests
🔇 Additional comments (2)
deploy/helm/jumpstarter/charts/jumpstarter-controller/model.py (1)

59-63: Enum: added nodeport — LGTM; service templates already gate NodePort via .Values.grpc.nodeport.enabled

deploy/helm/jumpstarter/charts/jumpstarter-controller/values.schema.json (1)

682-686: Mode enum extended with nodeport — LGTM

Schema now matches the Python model.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants