chartmuseum
debug-toolkit
Our great sponsors
chartmuseum | debug-toolkit | |
---|---|---|
8 | 24 | |
3,477 | 56 | |
1.3% | - | |
6.8 | 2.8 | |
5 days ago | about 2 months 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.
debug-toolkit
-
Ask HN: Companies of one, what is your tech stack?
We're very much not a company of one anymore, but I used Unicorn Platform for our startups website (http://robusta.dev)
It's optimized for building a decent looking startup website in half an hour.
We now have an in house designer and frontend team so the whole thing will be replaced soon... But it got us fairly far.
- Ask HN: What podcasts are you listening to?
-
GitHub: Private Profiles
I use it all the time when hiring!
We're open source (https://robusta.dev) and very involved in the kubernetes ecosystem so GitHub history is extremely relevant when we look at candidates.
We'll hire people with no GitHub activity too, but when it's available it's great
- Come home to it like this?? Hard reset doesnt do anything.
- KOPF for operators in python?
-
"kubectl get sleep" t-shirts (free k8s give-away)
Github: https://github.com/robusta-dev/robusta Marketing site: http://robusta.dev/ Docs: https://docs.robusta.dev/master/
- GitHub - robusta-dev/debug-toolkit: A modern code-injection framework for Python. Like Pyrasite but Kubernetes-aware.
-
Hikaru 0.9.0b released
We're using Hikaru extensively in Robusta. The best part (well, other then the ease of use) is that Tom is super responsive to issues on GitHub and always happy to help.
-
My self-hosting infrastructure, fully automated
To everyone saying that Kubernetes is unnecessary, try implementing autoscaling, service discovery, secrets management, and autohealing in a vendor independent way without it.
Of course none of that is necessary for a self hosted home lab, but neither is gitops.
This is a very nice example of how to set stuff up properly.
OP, I would love to see Robusta (https://robusta.dev) as part of this too. It's definitely in line with your vision of automating everything, as it let's you automate the response to alerts and other events in your cluster. (Disclaimer: I'm one of the maintainers)
- Run script in the pod like a cron job.
What are some alternatives?
Harbor - An open source trusted cloud native registry project that stores, signs, and scans content.
robusta - Kubernetes observability and automation, with an awesome Prometheus integration
helm-diff - A helm plugin that shows a diff explaining what a helm upgrade would change
batgrl - badass terminal graphics library
helm-push - Helm plugin to push chart package to ChartMuseum
opentelemetry-python-contrib - OpenTelemetry instrumentation for Python modules
helm - The Kubernetes Package Manager
hyperpaper-planner - Dayplanner pdf for large e-readers (eg Remarkable 2, Supernote, Boox)
tailscale - The easiest, most secure way to use WireGuard and 2FA.
PyFlow - Visual scripting framework for python - https://wonderworks-software.github.io/PyFlow
hub-feedback - Feedback and bug reports for the Docker Hub
profile