containers-roadmap
amazon-ecr-credential-helper
Our great sponsors
| containers-roadmap | amazon-ecr-credential-helper | |
|---|---|---|
| 80 | 14 | |
| 5,137 | 2,396 | |
| 0.6% | 1.2% | |
| 2.0 | 8.4 | |
| 9 months ago | 4 days ago | |
| Shell | Go | |
| GNU General Public License v3.0 or later | 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.
containers-roadmap
-
General Availability of the AWS SDK for Rust
Thanks for showing up and answering questions. Congratulations on the release.
What kind of plans for support of Rust's evolving async ecosystem?
Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps? See example for Containers: https://github.com/aws/containers-roadmap/projects/1
Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically
-
Architecting for Resilience: Crafting Opinionated EKS Clusters with Karpenter & Cilium Cluster Mesh — Part 1
Second, We will only rely on one managed node group, but we will leverage Karpenter; however, karpenter needs to be deployed on a node. (This may change soon once the Karpenter is available on the EKS Control Plane.) [EKS] Karpenter inside control plane · Issue #1792 · aws/containers-roadmap
-
Running a Web Application with 100% AWS Fargate Spot Containers 🤘
As written in the AWS documentation, during periods of extremely high demand, Fargate Spot capacity might be unavailable. In concrete terms, if your ECS service is set up to execute tasks in 100% Spot, there is a risk of running out of capacity. A workaround has been created in the hope that one day this issue will be implemented by the AWS team. This workaround allows you to set up two ECS services :
-
Kubernetes SidecarContainers feature is merged
Deploying Fargate with CDK has to have been the most pleasant developer experience I have ever had with any product so far.
If image caching becomes a reality with Fargate I can't imagine a need to ever use anything else
https://github.com/aws/containers-roadmap/issues/696
- AWS Config supports recording exclusions by resource type
- Announcing pull through cache for registry.k8s.io in Amazon Elastic Container Registry
-
EKS/Spot vs EKS Fargate/Spot?
Eks Fargate doesn't support spot yet https://github.com/aws/containers-roadmap/issues/622
- audit logging of the master plane in EKS
-
How to use Podman inside of a container
Until podman could be used with AWS ECR/ECS it's pretty much moot in my case: https://github.com/aws/containers-roadmap/issues/626
- How to keep 100% availability with a single ec2 spot instance?
amazon-ecr-credential-helper
-
Authenticating your GitLab CI runner to an AWS ECR registry using Amazon ECR Docker Credential Helper 🔑
Install the AWS ECR Docker Credential Helper in your runner
-
Terraform module to create a DNS alias for an ECR registry (123456789012.dkr.ecr.us-east-1.amazonaws.com => ecr.example.com)
Instead of doing that you can download the official ecr-login credential helper tool (a binary built with Go) and configure Docker to use this helper tool every time you interact with the registry. So to you, the user, the authentication is happening in the background and you can push and pull without doing anything.
-
ECR and EC2
IAM instance profile that allows ECR actions. Then set up ecr credential helper so docker pull will just work.
-
EKS needing an updated refresh token with ECR
You can use the ECR credential helper which rotates the credentials for you: https://github.com/awslabs/amazon-ecr-credential-helper
- awslabs/amazon-ecr-credential-helper: Automatically gets credentials for Amazon ECR on docker push/docker pull
- error: failed to solve: authorization status: 401: authorization failed
-
Yes, you can use Docker without Docker Desktop on your Mac!
AWS ECR credential helper though..
-
Docker no basic auth credentials after successful login on linux
Based on what I am seeing here, I would check for a ~/.docker/config.json file or an /etc/docker/config.json to see if anything could be misconfigured.
- Does anyone have a clean way to update AWS ecr credentials for pulling images
-
ECR in larger organisations - looking for opinions
Use https://github.com/awslabs/amazon-ecr-credential-helper posted in another reply https://www.reddit.com/r/aws/comments/p5e9td/ecr_in_larger_organisations_looking_for_opinions/h95bv9b/
What are some alternatives?
eks-nvme-ssd-provisioner - EKS NVMe SSD provisioner for Amazon EC2 Instance Stores
lima - Linux virtual machines, with a focus on running containers
kube-fledged - A kubernetes operator for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
colima - Container runtimes on macOS (and Linux) with minimal setup
netshoot - a Docker + Kubernetes network trouble-shooting swiss-army container
k8s-ecr-login-renew - Renews Docker login credentials for an AWS ECR container registry.
kraken - P2P Docker registry capable of distributing TBs of data in seconds
juicefs - JuiceFS is a distributed POSIX file system built on top of Redis and S3.
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
aws-eks-share-gpu - How to share the same GPU between pods on AWS EKS
k8s-device-plugin - NVIDIA device plugin for Kubernetes