Providing an operational Helm chart for Kubernetes #43

New issue

Open

opened 2025-01-19 03:30:14 +00:00 by Catgirl · 0 comments

Catgirl commented

2025-01-19 03:30:14 +00:00

Summary

I would like to see a Helm chart operational. I run a Kubernetes cluster personally, and having to figure out and modify the configuration manually can take time and research. This is a task that can be automated.
This helm chart would ideally set up Forkey and its dependencies with reasonable defaults, but with room to customize if needed.
If needed, I can test this with my cluster.

Speculated tasks (will expand as needed)

Offer Helm chart data within the repository (seems to? Need to look into it.)
Offer a Helm Chart Registry from which to source the project for deployment with Helm
- Provide a Workflow to automatically push it as it updates

Purpose

Kubernetes allows administrators to efficiently manage their infrastructure across multiple servers. Enabling administrators a path of doing this easily would be quite the help to administrators seeking to deploy Forkey on their Kubernetes clusters.

A helm chart would allow an administrator to rapidly deploy, update, and manage Forkey on a Kubernetes cluster in an automated manner, simply by running a few simple commands. Forgejo allows hosting Forkey in this manner via the Helm Chart Registry.

To illustrate this, an example of how it can be used with Helm:

# Add the woem.men user as a source of Helm packages
helm repo add git.woem.men https://git.woem.men/api/packages/woem.men/helm
helm repo update

# Install Forkey
helm install forkey git.woem.men/forkey

One should after this have a functional Kubernetes setup of Forkey - There are options you can customize, of course, that Helm enables.

Do you want to implement this feature yourself?

Yes, I will implement this by myself and send a pull request

### Summary I would like to see a Helm chart operational. I run a Kubernetes cluster personally, and having to figure out and modify the configuration manually can take time and research. This is a task that can be automated. This helm chart would ideally set up Forkey and its dependencies with reasonable defaults, but with room to customize if needed. If needed, I can test this with my cluster. Speculated tasks (will expand as needed) - [ ] Offer Helm chart data within the repository (seems to? Need to look into it.) - [ ] Offer a Helm Chart Registry from which to source the project for deployment with Helm - [ ] Provide a Workflow to automatically push it as it updates ### Purpose Kubernetes allows administrators to efficiently manage their infrastructure across multiple servers. Enabling administrators a path of doing this easily would be quite the help to administrators seeking to deploy Forkey on their Kubernetes clusters. A helm chart would allow an administrator to rapidly deploy, update, and manage Forkey on a Kubernetes cluster in an automated manner, simply by running a few simple commands. Forgejo allows hosting Forkey in this manner via the [Helm Chart Registry.](https://forgejo.org/docs/latest/user/packages/helm/) To illustrate this, an example of how it can be used with Helm: ```bash # Add the woem.men user as a source of Helm packages helm repo add git.woem.men https://git.woem.men/api/packages/woem.men/helm helm repo update # Install Forkey helm install forkey git.woem.men/forkey ``` One should after this have a functional Kubernetes setup of Forkey - There are options you can customize, of course, that Helm enables. ### Do you want to implement this feature yourself? - [x] Yes, I will implement this by myself and send a pull request