phoenix_container_example
kube-fledged
phoenix_container_example | kube-fledged | |
---|---|---|
9 | 10 | |
19 | 1,204 | |
- | - | |
9.1 | 4.7 | |
5 days ago | 3 months ago | |
HCL | 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.
phoenix_container_example
-
Testcontainers
It's particularly useful for testing a set of microservices.
See https://github.com/cogini/phoenix_container_example for a full example.
-
Musl 1.2.4 adds TCP DNS fallback
I use distroless images based on Debian or Ubuntu, e.g., https://github.com/cogini/phoenix_container_example
The result is images the same size as Alpine, or smaller, without the incompatibilities. I think Alpine is a dead end.
-
Where do you build your image in your pipeline?
Here is a full-featured example of building images in GitHub Actions that includes optimized caching: https://github.com/cogini/phoenix_container_example/blob/master/.github/workflows/ci-ghcr.yml
-
AWS Devops tools vs Bitbucket
Here are some examples of using GitHub actions to build, or call hosted runners in AWS to build Arm images, and using OIDC to manage AWS credentials: https://github.com/cogini/phoenix_container_example/blob/master/.github/workflows/
-
Running python when building a Docker image on AWS
Parameter Store is a good place to store things. ECS can read from it and set variables. This is a complete example of using Terraform to manage infrastructure with EC2 or ECS: https://github.com/cogini/multi-env-deploy Here is an app that runs in ECS: https://github.com/cogini/phoenix_container_example This task file sets env vars based on parameter store: https://github.com/cogini/phoenix_container_example/blob/master/ecs/taskdef.json
- Advice on CI/CD at scale from GitHub Enterprise to CodePipeline (TF & CFN) ?
-
When would you introduce Docker to your project?
Here is a complete example project which shows how to use Earthly and Visual Studio Code .devcontainer: https://github.com/cogini/phoenix_container_example
- I wrote A blog post about my experience trying to use buildkit caching to speed up CI
-
We are the AWS Containers Team - Ask the Experts - Feb 10th @ 11AM PT / 2PM ET / 7PM GMT!
I am heavily using multi-stage builds, e.g.: https://github.com/cogini/phoenix_container_example/blob/master/deploy/Dockerfile.alpine
kube-fledged
-
Musl 1.2.4 adds TCP DNS fallback
Exactly. Part of the appeal to consolidate all of our container images to use Debian-slim is the ability to optimise the caching of layers, both in our container registry but also on our kubernetes cluster’s nodes (which can be done in a consistent manner with kube-fledged[1]).
[1] https://github.com/senthilrch/kube-fledged
-
Ask HN: Have You Left Kubernetes?
If you're pulling big images you could try kube-fledged (it's the simplest option, a CRD that works like a pre-puller for your images), or if you have a big cluster you can try a p2p distributor, like kraken or dragonfly2.
Also there's that project called Nydus that allows starting up big containers way faster. IIRC, starts the container before pulling the whole image, and begins to pull data as needed from the registry.
https://github.com/senthilrch/kube-fledged
https://github.com/dragonflyoss/Dragonfly2
https://github.com/uber/kraken
https://nydus.dev/
-
Interesting tools?
kube fledged - pre pull containes in nodes: https://github.com/senthilrch/kube-fledged
-
Kube-fledged: Cache Container Images in Kubernetes
kube-fledged is a kubernetes add-on or operator for creating and managing a cache of container images directly on the worker nodes of a kubernetes cluster. It allows a user to define a list of images and onto which worker nodes those images should be cached (i.e. pulled). As a result, application pods start almost instantly, since the images need not be pulled from the registry. kube-fledged provides CRUD APIs to manage the lifecycle of the image cache, and supports several configurable parameters in order to customize the functioning as per one’s needs. (URL: https://github.com/senthilrch/kube-fledged)
- Introducing GKE image streaming for fast application startup and autoscaling
-
Can Kubernetes pre-pull and cache images?
I found recently this tool kube-fledged that should do what you want..
- senthilrch/kube-fledged: A kubernetes add-on for creating and managing a cache of container images directly on the cluster worker nodes, so application pods start almost instantly
-
Best way to mirror images to improve their availability for a cluster?
I recommend you also look at kube-fledged this is more appealing IMHO.
What are some alternatives?
elixir-boilerplate - ⚗ The stable base upon which we build our Elixir projects at Mirego.
kraken - P2P Docker registry capable of distributing TBs of data in seconds
amazon-ecs-agent - Amazon Elastic Container Service Agent
ImageWolf - Fast Distribution of Docker Images on Clusters
ecs-deploy - Simple shell script for initiating blue-green deployments on Amazon EC2 Container Service (ECS)
image-cache-daemon
multi-env-deploy - Complete example of deploying complex web apps to AWS using Terraform, Ansible, and Packer
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
Veil - Simple passwordless authentication for your Phoenix apps
Dragonfly - This repository has be archived and moved to the new repository https://github.com/dragonflyoss/Dragonfly2.
NuGet - NuGet Gallery is a package repository that powers https://www.nuget.org. Use this repo for reporting NuGet.org issues.
kubefwd - Bulk port forwarding Kubernetes services for local development.