php-k8s
Unofficial PHP client for Kubernetes. It supports any form of authentication, the exec API, and it has an easy implementation for CRDs. (by renoki-co)
kube-no-trouble
Easily check your clusters for use of deprecated APIs (by doitintl)
| php-k8s | kube-no-trouble | |
|---|---|---|
| 3 | 21 | |
| 307 | 3,036 | |
| 0.0% | 3.2% | |
| 5.0 | 6.4 | |
| 3 months ago | 9 days ago | |
| PHP | Go | |
| Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
php-k8s
Posts with mentions or reviews of php-k8s.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-10.
-
https://np.reddit.com/r/PHP/comments/nqzux3/another_kubernetes_client_for_php_k8sclient/h0f1oaj/
I have leveraged some of the best practices in renoki-co/php-k8s, taking initially Laravel Eloquent as an example to build resources that have many attributes. You might want to take examples from there as it's coherent, and you're on a good path. :D
-
Manage K8s resources in PHP
I was inspired by Laravel Eloquent ORM model. PHP K8S is some kind of ORM, but for Kubernetes Resources. Since the Kubernetes API is consistent, the implementation was DRY af, and I could write end-to-end testing with real-world examples like running MySQL as StatefulSet. Retrieve a model or build a model, you got anything you need in one class.
kube-no-trouble
Posts with mentions or reviews of kube-no-trouble.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-06-26.
-
Mitigating disruption during Amazon EKS cluster upgrade with blue/green deployment
There are several tools that help us find out the API deprecations in our clusters. One of them is “kube-no-trouble” aka kubent. At the time I write this document, the latest ruleset is for 1.29 in kubent. I run kubent with target version of 1.29 and got the below result. As you can see, kubent shows the deprecated APIs.
-
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.
- Best Practices for Upgrading Kubernetes?
-
Updating from 1.25.15 to 1.26.10
kubent has been my goto for this - you point it at your cluster, tell it the target version you want to use, and it'll let you know if you have any depreciated resources and what you'll need to change. It's simple to use, quick, and just does the job.
-
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.
-
Upgrading our EKS from 1.21 to 1.22
A great tool for checking depreciations is kubent/kube-no-trouble: https://github.com/doitintl/kube-no-trouble
-
strategy to upgrade eks cluster
https://github.com/doitintl/kube-no-trouble can be used to check for deprecated/removed APIs - you'll need to fix these in your codebase. You should fix these before upgrading your cluster
- choose from Two strategies we can implement to upgrade eks cluster
- Amazon EKS now support Kubernetes version 1.25
-
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
Just upgraded a few clusters from 1.21 to 1.24 the past few weeks. Used kubent (Kube No Trouble https://github.com/doitintl/kube-no-trouble) before upgrading and reviewed the output. Pretty painless process all in all.
What are some alternatives?
When comparing php-k8s and kube-no-trouble you can also consider the following projects:
Easy!Appointments - :date: Easy!Appointments - Self Hosted Appointment Scheduler
kubepug - Kubernetes PreUpGrade (Checker)
Fusion Directory - FusionDirectory is a modern, efficient and secure Identity Management (IAM) solution.
silver-surfer - Kubernetes objects api-version compatibility checker and provides migration path for K8s objects and prepare it for cluster upgrades
Pawl - Asynchronous WebSocket client
pluto - A cli tool to help discover deprecated apiVersions in Kubernetes
server-builder - Deploying K3s to hetzner in the most ridiculous way possible: KISS
gardener - Homogeneous Kubernetes clusters at scale on any infrastructure using hosted control planes.
container-terminal
polaris - Validation of best practices in your Kubernetes clusters
laravel-query-builder - Easily build Eloquent queries from API requests
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.
php-k8s vs Easy!Appointments
kube-no-trouble vs kubepug
php-k8s vs Fusion Directory
kube-no-trouble vs silver-surfer
php-k8s vs Pawl
kube-no-trouble vs pluto
php-k8s vs server-builder
kube-no-trouble vs gardener
php-k8s vs container-terminal
kube-no-trouble vs polaris
php-k8s vs laravel-query-builder
kube-no-trouble vs Gravitational Teleport