Skip to content

Conversation

@kvaps
Copy link
Member

@kvaps kvaps commented Jun 16, 2025

Signed-off-by: Andrei Kvapil [email protected]

Summary by CodeRabbit

  • New Features
    • The application now automatically detects and uses the Kubernetes server version when rendering manifests and performing diff operations, improving compatibility with your cluster environment.

@coderabbitai
Copy link

coderabbitai bot commented Jun 16, 2025

Walkthrough

A new helper function, discoverKubeVersion, was added to query the Kubernetes API server for its version and return it as a hchart.KubeVersion struct. This function is now called in three locations to set the KubeVersion field on Helm install actions, ensuring they are aware of the server version during rendering and diffing.

Changes

File(s) Change Summary
main.go Added discoverKubeVersion function; integrated it into three locations to set Helm action version.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Main
    participant K8sAPI as Kubernetes API Server
    participant HelmInstall

    User->>Main: Trigger manifest render or diff
    Main->>K8sAPI: Query for server version (discoverKubeVersion)
    K8sAPI-->>Main: Return version info
    Main->>HelmInstall: Set KubeVersion field
    Main->>HelmInstall: Proceed with render/diff action
Loading

Poem

A hop to the cluster, a leap to the sky,
Now Helm knows the version, oh my oh my!
With queries so clever, and structs set just right,
Our manifests render, diffing takes flight.
🐰✨


📜 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 9ead6e4 and 62d8d62.

📒 Files selected for processing (1)
  • main.go (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • main.go
✨ Finishing Touches
  • 📝 Generate Docstrings

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.

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: 2

🧹 Nitpick comments (1)
main.go (1)

327-336: Re-use the existing REST config instead of creating one more round-trip
realHelmDiff() creates a fresh REST config even though its caller already has one (and the function immediately uses it only for version discovery). This:

  1. Duplicates kube-config parsing work for every diff invocation.
  2. Makes the code path harder to unit-test because the function owns the config construction.

Consider passing the *rest.Config down from the caller (same as renderManifests already does) and deleting the extra restConfig() call to reduce overhead and keep the API uniform.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 91c6764 and 9ead6e4.

📒 Files selected for processing (1)
  • main.go (3 hunks)

Comment on lines 240 to 246
if plain {
kubeVer, err := discoverKubeVersion(rc)
if err != nil {
return "", err
}
inst.KubeVersion = &kubeVer
vers, err := discoverAPIVersions(rc)
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

*Guard against nil rest.Config before querying the cluster
renderManifests() assumes that rc is non-nil. When cmdShow is invoked with --plain and there is no valid KUBECONFIG, restConfig() returns (nil, err) but the error is ignored (rc, _ := restConfig()).
Calling discoverKubeVersion(rc) (or discoverAPIVersions(rc)) with a nil pointer will panic inside the REST client constructor.

-if plain {
-    kubeVer, err := discoverKubeVersion(rc)
+if plain {
+    if rc == nil {
+        return "", fmt.Errorf("renderManifests: kubeconfig not found – cannot discover cluster version")
+    }
+    kubeVer, err := discoverKubeVersion(rc)

Fail fast with a clear error instead of a runtime panic.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
if plain {
kubeVer, err := discoverKubeVersion(rc)
if err != nil {
return "", err
}
inst.KubeVersion = &kubeVer
vers, err := discoverAPIVersions(rc)
if plain {
if rc == nil {
return "", fmt.Errorf("renderManifests: kubeconfig not found – cannot discover cluster version")
}
kubeVer, err := discoverKubeVersion(rc)
if err != nil {
return "", err
}
inst.KubeVersion = &kubeVer
vers, err := discoverAPIVersions(rc)
🤖 Prompt for AI Agents
In main.go around lines 240 to 246, the code calls discoverKubeVersion(rc) and
discoverAPIVersions(rc) without checking if rc (a *rest.Config) is nil, which
can cause a panic if restConfig() returned nil due to missing or invalid
KUBECONFIG. Modify the code to check if rc is nil immediately after calling
restConfig(), and if so, return a clear error indicating the missing or invalid
kubeconfig before proceeding to call any functions that use rc.

@kvaps kvaps merged commit ce42fe9 into main Jun 16, 2025
2 of 3 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.

3 participants