Grove Helm charts
Path & Utilities Helm charts

Table of Contents

• Introduction
  • Getting started
  • Makefile targets
  • Required packages
• Releasing a New Version
  • Versioning
  • Updates to the main Branch
  • Important Considerations on Multiple Updates
• ClaudeSync Setup

Introduction

Welcome to Grove's helm repo. Here you'll find the charts to get Path up and running.

Getting started

To add Grove's helm repository to your local machine, run the following command:

helm repo add grove https://buildwithgrove.github.io/helm-charts

Once you have the repository added, refresh the repositories added running:

helm repo update

Makefile targets

This repository has a number of makefile targets which allow the team with functionality such as validations and workflow execution.

If you're unsure where to start, run make help for a better understanding of the target capabilities.

Required packages

This repo requires you to have installed the following packages:

• helm
• gh

To install them using Homebrew simply run the following command:

brew install helm gh

If you're using a distribution other than MacOS or not using Homebrew, head over to the release page of each package to find out the best way to install them:

• https://helm.sh/docs/intro/install/
• https://github.com/cli/cli?tab=readme-ov-file#installation

Releasing a New Version

Versioning

When the Helm chart is prepared for release, update its version in the Chart.yaml file.

Adhere to SemVer guidelines for versioning.

Updates to the main Branch

Upon updating the version in the main branch, the CI will automatically create a new release for the Helm chart.

Important Considerations on Multiple Updates

Updating several Helm chart versions simultaneously may cause CI failures, likely due to an issue with the helm/chart-releaser-action GitHub action.

If this occurs, please report the issue for prompt troubleshooting and resolution.

Our suggestion, alternatively, is to only update one at a time.

For example, if you are updating the guard chart, you should follow this sequence:

1. Increment the guard chart version in the charts/guard/Chart.yaml file according the SemVer guidelines
2. Open a PR with the changes and merge to main
3. Once the PR is merged, the CI will automatically create a new release for the Helm chart
4. Once the release is created, you can update the path chart to use the new guard chart version
5. Increment the path chart version in the charts/path/Chart.yaml file according the SemVer guidelines
6. Open a PR with the changes and merge to main

ClaudeSync Setup

This repo is setup to use ClaudeSync to help answer questions about the repo.

You can view .claudeignore to see what files are being ignored to ensure Claude's context is limit to the right details.

1. Install ClaudeSync - Ensure you have python set up on your machine

   pip install claudesync

2. Authenticate - Follow the instructions in your terminal

   claudesync auth login

3. Create a Project - Follow the instructions in your terminal

   make claudesync_init

4. Start Syncing - Run this every time you want to sync your local changes with Claude

   make claudesync_push

5. Set the following system prompt

   You are a friendly, helpful AI assistant specialized in analyzing Helm charts and Kubernetes configurations.
   
   Your task is to review Helm charts, explain issues in simple terms, and provide straightforward recommendations.
   
   When reviewing Helm charts:
   
   1. Focus on critical issues first - what's preventing deployment or causing errors
   2. Explain problems and solutions in plain language a backend developer would understand
   3. Provide specific, actionable fixes with code examples when helpful
   4. Keep explanations brief and bias to using bullet points for clarity
   
   Present your findings in a conversational way:
   - Start with a brief overall assessment (1-2 sentences)
   - List 3-5 key issues/recommendations as bullet points
   - Offer code snippets only for the most important fixes
   - End with a simple "next steps" suggestion
   - Bias towards industry best practices
   
   Avoid:
   - Lengthy analysis processes
   - DevOps jargon without explanation
   - Complex Kubernetes concepts without context
   - Overwhelming the user with too many recommendations
   - Giving multiple solutions unless you're asked for them
   
   Remember that while the user is an experienced engineer, and they are not professional DevOps.
   It is likely they may not be familiar with Kubernetes or Helm chart best practices, so focus on practical solutions rather than theoretical correctness.