version-checker
pluto
version-checker | pluto | |
---|---|---|
3 | 18 | |
646 | 1,994 | |
2.3% | 2.3% | |
8.2 | 5.8 | |
8 days ago | 9 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
version-checker
- How do you guys monitor K8s core services new versions
- opensource tool for version checker
-
What tool to check images for new versions ?
jetstack’s verison-checker exposes Prometheus metrics about containers images from which you can create dashboards.
pluto
-
Upgrading Hundreds of Kubernetes Clusters
We also leverage tools like Kubent, popeye, kdave, and Pluto to help us manage API deprecations (when Kubernetes deprecates features in updates) and ensure the overall health of our infrastructure.
- Updating from 1.25.15 to 1.26.10
-
How do you handle continuous k8s cluster version upgrades in your organization?
You have to constantly run tools like https://github.com/doitintl/kube-no-trouble / https://github.com/FairwindsOps/pluto.
- How do you guys monitor K8s core services new versions
-
eks cluster upgrade Anyone has done eks cluster upgrade to upgrade the cluster from 1.21 to 1.22 there are some api resources kind need to changed, which need changes in manifest file changes. how do we identify the helm charts that are using these resources ? https://docs.aws.amazon.com/eks/lat
You might like https://github.com/FairwindsOps/pluto
- Kubernetes upgrade
-
Upgrading EKS from k8s version 1.21 to 1.24
Run Pluto against the old cluster to check for outdated APIs in your namespaces: https://github.com/FairwindsOps/pluto
-
kubernetes provider resources v1 vs non-v1 is it just me or is this dumb?
I knew it was unsupported so about 6 months ago I had started an effort to switch to Kyverno, which is far better and actually supported. The version of Kyverno I was using had a v1beta1 AdmissionController. Fortunately that was in a helm chart so easily caught by pluto before my upgrade.
-
Helm chart - fluent-bit
If you're looking for API deprecations specifically you can look into pluto from fairwinds.
-
Updating EKS to 1.22: dealing with deprecated APIs on ALB Ingresses
you can use https://github.com/FairwindsOps/pluto to check for api deprecations before updating the cluster.
What are some alternatives?
bump2version - Version-bump your software with a single command
kube-no-trouble - Easily check your clusters for use of deprecated APIs
helm-charts
silver-surfer - Kubernetes objects api-version compatibility checker and provides migration path for K8s objects and prepare it for cluster upgrades
script_exporter - Prometheus exporter to execute scripts and collect metrics from the output or the exit status.
helm - The Kubernetes Package Manager
renovate - Universal dependency automation tool.
rbac-manager - A Kubernetes operator that simplifies the management of Role Bindings and Service Accounts.
git-describe - Embeds git-describe output in your Golang binary. Alternative to 'go build -ldflags -X version=' command.
helmfile - Deploy Kubernetes Helm Charts
scraper - A simple library to scrape and monitor multiple urls in Go (with support for prometheus metrics)
polaris - Validation of best practices in your Kubernetes clusters