flamingo
kapp-controller
| flamingo | kapp-controller | |
|---|---|---|
| 7 | 5 | |
| 582 | 254 | |
| 3.6% | 1.6% | |
| 8.5 | 8.7 | |
| about 2 months ago | 8 days ago | |
| Go | 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.
flamingo
-
Options for handling Terraform with ArgoCD
I'm aware of: - A k8s cronjob shelling out to the terraform CLI - flamingo -> Flux -> weaveworks Terraform controller - Terraform cloud operator - Crossplane's terraform provider
-
Disaster Recovery for AWS EKS Infra
Weave's TF-Controller, which also has fewer bugs, much better adoption, and it looks like it's actually being developed by someone. But requires a weird argocd <-> flux interop boilerplate. It's a "controller for flux" and not a Kubernetes controller, and I don't really get such ambiguous targeting , but meh...
- Argocd and Flux at the same time?
- What tool suggestions do you have for someone who's gonna set up an on-premise k8 cluster? Which tools do you use?
- GitHub - flux-subsystem-argo/flamingo: Flux Subsystem for Argo - Landing Repository
- ArgoCD vs. crossplane-helm provider for managing helm releases?
- chanwit/flamingo
kapp-controller
-
Helm is both "package manager" and "templating engine" - probably the best package manager but horrible template engine
We use kapp-controller when applying our charts (it uses helm template instead of helm install) so we can be very rigorous about what fields are changeable (like through pod autoscaling) and what are not (securitycontext, etc.)
-
How to handle the lifecycle of multiple COTS
Even further, you could describe your "fetch", "template", and "deploy" stages in akapp-controller AppCR and then you'd have a controller (like an operator) running the cluster continuously reconciling your private cloud to ensure that it's always reconverging to the desired state. This is basically what's underpinning a number of VMWare's commercial (and OSS) Tanzu offerings, as well as some other organization's internal platforms, or "self hosted private clouds"
-
ArgoCD vs. crossplane-helm provider for managing helm releases?
Full disclosure: I work on https://carvel.dev/kapp-controller/ which can also continuously reconcile helm charts (via our own CRD ).
-
Deployment Packaging Solutions
kapp-controller
-
Deploy Neo4J's APOC plugin with code thanks to CARVEL vendir
kapp-controller - Capture application deployment workflow in App CRD. Reliable GitOps experience powered by kapp.
What are some alternatives?
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
cnab-spec - Cloud Native Application Bundle Specification
Echo - High performance, minimalist Go web framework
kapp - kapp is a simple deployment tool focused on the concept of "Kubernetes application" — a set of resources with the same label
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
vendir - Easy way to vendor portions of git repos, github releases, helm charts, docker image contents, etc. declaratively
Buffalo - Rapid Web Development w/ Go
imgpkg - Store application configuration files in Docker/OCI registries
weave-gitops - Weave GitOps provides insights into your application deployments, and makes continuous delivery with GitOps easier to adopt and scale across your teams.
ytt - YAML templating tool that works on YAML structure instead of text
httprouter - A high performance HTTP request router that scales well
asdf - k14s asdf plugin