Skip to content

feat: add Clearnode Helmfile#630

Merged
philanton merged 1 commit intomainfrom
feat/clearnode-helmfile
Mar 25, 2026
Merged

feat: add Clearnode Helmfile#630
philanton merged 1 commit intomainfrom
feat/clearnode-helmfile

Conversation

@philanton
Copy link
Contributor

@philanton philanton commented Mar 25, 2026

Summary by CodeRabbit

  • Chores
    • Added deployment configuration for multiple environments (sandbox-v1 and v1-rc), enabling environment-specific releases and dynamic image tagging. Configuration sourcing updated to support environment-specific parameters.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 25, 2026

📝 Walkthrough

Walkthrough

A new Helmfile template is added that defines two Kubernetes environments (sandbox-v1 and v1-rc) with a single clearnode release deployed from a local chart directory. The template configures environment-specific namespaces, values files, and requires an IMAGE_TAG environment variable for the container image.

Changes

Cohort / File(s) Summary
New Helmfile Template
clearnode/helmfile.yaml.gotmpl
Helmfile configuration defining sandbox-v1 and v1-rc environments with a clearnode release sourcing values from environment-specific YAML files in chart/config/{{ .Environment.Name }}/ and requiring IMAGE_TAG environment variable for container image tag.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Whiskers twitch with glee, a template takes flight,
Two environments configured, oh what a delight!
Sandbox and RC, bundled with care,
Helmfiles and values floating through the air,
IMAGE_TAG echoes—deployment's near! 🚀

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title accurately describes the main change: adding a new Helmfile configuration template for Clearnode deployment.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/clearnode-helmfile

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

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

Copy link
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.

🧹 Nitpick comments (1)
clearnode/helmfile.yaml.gotmpl (1)

9-11: Consider enabling namespace auto-creation for first-time deploys.

If clearnode-<env> doesn't already exist, install can fail. Adding createNamespace: true improves rollout reliability for new clusters/environments.

Suggested change
   - name: clearnode
     namespace: clearnode-{{ .Environment.Name }}
     chart: ./chart
     installed: true
+    createNamespace: true
     values:
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@clearnode/helmfile.yaml.gotmpl` around lines 9 - 11, Add namespace
auto-creation to the Helm release definition so first-time deploys don't fail
when the namespace (namespace: clearnode-{{ .Environment.Name }}) doesn't exist;
modify the release block that contains namespace/chart/installed to include
createNamespace: true (or the equivalent Helm option) so Helm will create
clearnode-{{ .Environment.Name }} automatically during install.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@clearnode/helmfile.yaml.gotmpl`:
- Around line 9-11: Add namespace auto-creation to the Helm release definition
so first-time deploys don't fail when the namespace (namespace: clearnode-{{
.Environment.Name }}) doesn't exist; modify the release block that contains
namespace/chart/installed to include createNamespace: true (or the equivalent
Helm option) so Helm will create clearnode-{{ .Environment.Name }} automatically
during install.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3e03194d-4e03-45b6-ace7-e32a53e80cd8

📥 Commits

Reviewing files that changed from the base of the PR and between 9422d91 and 6429010.

📒 Files selected for processing (1)
  • clearnode/helmfile.yaml.gotmpl

@philanton philanton merged commit d241b1d into main Mar 25, 2026
8 checks passed
@philanton philanton deleted the feat/clearnode-helmfile branch March 25, 2026 15:38
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.

1 participant