-
Notifications
You must be signed in to change notification settings - Fork 24
chore: add Helm Chart #58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thank you! ❤️ What a nice idea. I can look into it this Sunday. |
Thank you so much! 😊 I'm thrilled that you liked the idea. Looking forward to your feedback after the weekend. Have a fantastic Sunday, and thanks again for taking the time to check it out! 🌟 |
FYI, I attempted to use this helm template and I found several issues:
|
@matteovivona |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kahirokunn, I'm very sorry for the delay 😔
The last couple of months were very full and I didn't find the time to look into Helm Charts, as I'm quite new to this subject.
In the future, it might be good to include instructions in our docs for installing the Helm Chart via a URL to the GitHub Repo.
Thank you very much for your contribution to making it easier to install github-actions-cache-server
on k8s.
Also thanks to @helletheone (who definitely has more experience than me) for reviewing this PR.
feat: Add Helm Chart for GitHub Actions Cache Server
This PR introduces a Helm chart for deploying a GitHub Actions cache server on Kubernetes. With this addition, setting up a local or production-ready cache server for GitHub Actions becomes straightforward and easily manageable via Kubernetes.
Key Features
github-actions
) to ensure clean and organized deployments.kind
for development and testing.Quick Start
To quickly get started with a local Kubernetes setup using
kind
:kind
:Run the following commands to forward the cache server port to your local machine:
Releasing a New Helm Chart
To release a new version of the Helm chart, follow these steps:
Chart.yaml
Version:Before packaging the Helm chart, ensure that the
version
field in theChart.yaml
file is updated to the new release version. For example:Make sure to replace
0.1.0
with the new version number for the release.Once the
Chart.yaml
is updated, package the Helm chart by navigating to the directory containing your Helm chart and running the following command:This will create a
.tgz
package file for your Helm chart.After packaging, use the
helm push
command to upload the packaged Helm chart to the OCI registry. Make sure to use the correct version number that matches the one inChart.yaml
:Replace
0.1.0
with the actual version number you're releasing.Ensure you have the appropriate permissions to push to the specified OCI registry.
Notes
Looking forward to your reviews and suggestions!