kustomize
containers-roadmap
Our great sponsors
| kustomize | containers-roadmap | |
|---|---|---|
| 28 | 80 | |
| 10,532 | 5,137 | |
| 1.2% | 0.6% | |
| 9.2 | 2.0 | |
| 7 days ago | 9 months ago | |
| Go | Shell | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
kustomize
-
Building a Kubernetes Operator with the Operator Framework
kustomize: brew install kustomize
- Kustomize deployment order
- Deploying helm charts with other resources
-
How and when to use Helm and Kustomize together
It's a built in feature of kustomize https://github.com/kubernetes-sigs/kustomize/blob/master/api/types/helmchartargs.go
-
Alternatives to Helm?
I think the combination of Kustomize and helm works in my experience. For advanced use cases, you can also see KRM functions in Kustomize.
-
How to pass dynamic values to Kustomize?
See for instance a related issue: https://github.com/kubernetes-sigs/kustomize/issues/3866
-
Help with Kustomize: cleanest way to replace an environment variable in a pod or deployment?
Using a strategic merge is the safest way so you avoid the index fragility.
-
Helm makes it overly complex, or is it just me?
Rendering out the manifests is something I have been pushing for. Not having to understand how every templating tool works and what actually is being changed is key. Though, it gets complicated when you use helm (or any templating/patching tool) that produces many variants. You also lose any release/deployment time hooks that are provided (helm hooks or recently "patched" kustomize env variables).
-
Deployment with ArgoCD & secrets in helm chart
https://github.com/kubernetes-sigs/kustomize/blob/master/examples/chart.md (edit: oh I see the other commenter also included this link, oops)
-
Monokle, Kustomize & Quality Kubernetes Deployments
Kustomize is an open-source project that “lets you customize raw, template-free YAML files for multiple purposes, leaving the original YAML untouched and usable as is.” It’s now the most popular tool for customizing Kubernetes manifests reasonably, and it’s even built directly into the Kubernetes CLI since K8s v1.14.
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
- 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?
What are some alternatives?
helmfile - Deploy Kubernetes Helm Charts
eks-nvme-ssd-provisioner - EKS NVMe SSD provisioner for Amazon EC2 Instance Stores
kpt - Automate Kubernetes Configuration Editing
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
ytt - YAML templating tool that works on YAML structure instead of text
netshoot - a Docker + Kubernetes network trouble-shooting swiss-army container
kubevela - The Modern Application Platform.
kraken - P2P Docker registry capable of distributing TBs of data in seconds
tanka - Flexible, reusable and concise configuration for Kubernetes
juicefs - JuiceFS is a distributed POSIX file system built on top of Redis and S3.
helm-charts - Prometheus community Helm charts
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.