chartmuseum
robusta
chartmuseum | robusta | |
---|---|---|
8 | 36 | |
3,613 | 2,626 | |
0.6% | 1.3% | |
6.0 | 9.5 | |
3 months ago | 1 day ago | |
Go | Python | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
chartmuseum
- GitHub - helm/chartmuseum: Host your own Helm Chart Repository
-
Do you mirror external helm chart repositories for local use?
We may switch over to Chartmusuem, and something like Charts-Syncer to try to help with this, or maybe abandon the whole idea of mirroring external repositories and just keep our repository hosting internal projects. What are your thoughts on this?
-
Ask r/kubernetes: What are you working on this week?
Also trying to find a small self-hosted container registry (not some beast like goharbor.io) and possibly a Helm chart repository (looking into chartmuseum.com). Anyone got some recommendations?
-
Where do you store your helm charts?
You can use either something like https://chartmuseum.com/ or any docker registry if it has OCI support.
-
Share how you do your CI/CD to Kubernetes
ChartMuseum is indeed open source and is on GitHub.
-
Self Hosted Module Registry
This is also basically an s3 proxy, but it specifically implements the Terraform Registry API so that things like version constraints are handled correctly. If you use Helm at all, an analogous project for charts would be https://github.com/helm/chartmuseum
-
Metadata for chartmuseum
I raised a PR (WIP) https://github.com/helm/chartmuseum/pull/464 but wondering if others would think this is useful or if I just have a niche usecase.
-
Ditching Docker Compose for Kubernetes
Another benefit of Helm is in it's package management. If your application requires another team's application up and running, they can publish their Helm chart to a remote repository like a ChartMuseum. You can then install their application into your Kubernetes by naming that remote chart combined with a local values file. E.g., helm install other-teams-app https://charts.mycompany.com/other-teams-app-1.2.3.tgz -f values-other-teams-app.yaml. This is convenient because it means you don't have to checkout their project and dig through it for their helm charts to get up and running - all you need to supply is your own values file.
robusta
-
Show HN: Kr8s a batteries-included Python client library for Kubernetes
To put one more option out there, we use Hikaru (https://pypi.org/project/hikaru/) in Robusta.dev (https://github.com/robusta-dev/robusta) and have been pretty happy with it. Example code below:
with Pod().read(name='thename', namespace='the-namespace') as p:
- Robusta 0.10.17 released - track Ingress changes, Helm failures, and more
-
datadog-agent VS robusta - a user suggested alternative
2 projects | 31 May 2023
Open Source alternative based on Prometheus
-
kubevoy VS robusta - a user suggested alternative
2 projects | 31 May 2023
-
Kubernetes Tooling ranking on GitHub
I'm from the Robusta team (https://github.com/robusta-dev/robusta) which bursts upwards towards the end. Happy to answer any questions!
-
Broke the Kubernetes cluster, and asked ChatGPT to write me a poem about it in Shakespear style
The guys at Robusta, added it into thier slack so when alerts pop of issues in k8s, chatgpt can be used to investigate and offer options to check and potentially solutions. Next phase is probably to let it also apply it :)
-
Troubleshooting k8s - your recommendations for strategies and tools.
It's no replacement for learning how things work, but we're trying to automate common troubleshooting cases with Robusta. https://github.com/robusta-dev/robusta
-
How to automate repetitive tasks in Kubernetes with runbooks
https://docs.robusta.dev/master/ https://github.com/robusta-dev/robusta
-
Most efficient way to check all containers cluster wide for missing probes?
This is the sort of thing we built Robusta for: https://github.com/robusta-dev/robusta
- Writing Operators
What are some alternatives?
Harbor - An open source trusted cloud native registry project that stores, signs, and scans content.
karma - Alert dashboard for Prometheus Alertmanager
helm-diff - A helm plugin that shows a diff explaining what a helm upgrade would change
debug-toolkit - A modern code-injection framework for Python. Like Pyrasite but Kubernetes-aware.
helm-push - Helm plugin to push chart package to ChartMuseum
pydantic-aioredis - A Declarative ORM for Redis using Pydantic Models and aioredis
hub-feedback - Feedback and bug reports for the Docker Hub
kubectl - Issue tracker and mirror of kubectl code
helm - The Kubernetes Package Manager
star-history - The missing star history graph of GitHub repos - https://star-history.com
chart-releaser - Hosting Helm Charts via GitHub Pages and Releases
docker-swarm-tools - This repository contains useful docker-swarm-tools.