k8s-ecr-login-renew
pluto
k8s-ecr-login-renew | pluto | |
---|---|---|
4 | 18 | |
195 | 1,965 | |
- | 0.9% | |
3.8 | 5.8 | |
16 days ago | about 1 month ago | |
Go | Go | |
MIT License | 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.
k8s-ecr-login-renew
-
EKS needing an updated refresh token with ECR
I've done some googling and found some solutions like this https://github.com/nabsul/k8s-ecr-login-renew which seems to indicate that others have had the same issue.
- Interesting tools?
-
Replacing YAML with TypeScript
As for challenges I foresee: In this example, the applications are defined generically such that you could use them even if you wanted to skip Kubernetes altogether. However, I have two Kubernetes-specific applications that I run in the cluster: KCert and ecr-login-renewal. These applications require special Kubernetes configurations around service accounts and permissions. I'm not yet sure how to cleanly encode those.
- Image pull secret controller for AWS ECR
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?
k8s-yaml-alternative - An alternative to yaml files for Kubernetes
kube-no-trouble - Easily check your clusters for use of deprecated APIs
aws-ecr-image-pull-secret-controller - Custom controller for Kubernetes which automatically renews image pull secrets for AWS ECR
silver-surfer - Kubernetes objects api-version compatibility checker and provides migration path for K8s objects and prepare it for cluster upgrades
Flux - Successor: https://github.com/fluxcd/flux2
helm - The Kubernetes Package Manager
awesome-k8s-resources - A curated list of awesome Kubernetes tools and resources.
rbac-manager - A Kubernetes operator that simplifies the management of Role Bindings and Service Accounts.
rook - Storage Orchestration for Kubernetes
helmfile - Deploy Kubernetes Helm Charts
kcert - KCert: A Simple Let's Encrypt Manager for Kubernetes
polaris - Validation of best practices in your Kubernetes clusters