CloudGraph cli
helmfile
CloudGraph cli | helmfile | |
---|---|---|
24 | 39 | |
870 | 4,024 | |
0.3% | - | |
1.3 | 0.0 | |
6 months ago | about 1 year ago | |
TypeScript | Go | |
Mozilla Public License 2.0 | MIT License |
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.
CloudGraph cli
- Using cloudgragh in projects
-
Resoto: An open-source alternative to AWS Systems Manager Inventory
Looks similar to https://github.com/cloudgraphdev/cli
-
What’s your experience with AWS Cloud Control API
Honestly, half baked and not very useful at all. If you want an actual single GraphQL based API for ALL of your AWS services, plus CSPM (CIS 1.2, 1.3, 1.4, PCI, and NIST) check out https://github.com/cloudgraphdev/cli. Completely free OSS
-
Interesting tools?
https://github.com/cloudgraphdev/cli the GraphQL API for K8s, AWS, GCP, and Azure
-
Ask HN: Tool to export AWS configuration entirely?
Check out https://github.com/cloudgraphdev/cli. It supports a vast majority of AWS services and creates a type-safe GraphQL definition of your entire account
-
Finding things
If you are looking for a type-safe asset inventory of your GCP footprint(s) you can check out https://github.com/cloudgraphdev/cli. Along with the asset inventory (which you can query via GraphQL) it will also check for CIS 1.2 compliance failures.
-
Need to extract full inventory from Google Cloud in a useable format
CloudGraph can give you a type-safe asset inventory (plus CIS 1.2 compliance checks) for all of your resources on GCP: https://github.com/cloudgraphdev/cli
-
General AWS Stack Security
Some great suggestions here. I would also suggest running some tool like: https://github.com/cloudgraphdev/cli with the AWS CIS policy pack so you can ensure you are following best practices.
-
List EC2 instances from all accounts in all regions
You can use a tool like [CloudGraph](https://github.com/cloudgraphdev/cli) to do this pretty easily.
- I built an open-source GraphQL API for AWS, Azure, GCP, and Kubernetes in TypeScript
helmfile
-
Deploy IRIS Application to Azure Using CircleCI
What we’re going to install into the newly created AKS cluster is located in the helm directory. The descriptive Helmfile approach enables us to define applications and their settings in the helmfile.yaml file.
-
[2022] [Updated] Alternative to Helmfile
Is there any alternative to https://github.com/roboll/helmfile you are currently using in your company.
-
Projectsveltos: Manage Kubernetes addons in multiple clusters
Interesting, I have approached this problem using Helmfile (https://github.com/roboll/helmfile) to define a “platform release package.”
-
How are you handling ILM on kubernetes?
To make managing the Helm deployments a little easier I used helmfile (https://github.com/roboll/helmfile).
-
Helm Charts Microservices
But in general it's always easier to keep things quite separated. Meaning in separate helm releases. If you want to be able to manage things "together" at will, then you can use helmfile ( https://github.com/roboll/helmfile )
-
How to Build Software Like an SRE
I agree; helm is too declarative.
Whenever I can, I use helmfile[0] for storing variables for helm since it does add a declarative layer on top of helm.
0 - https://github.com/roboll/helmfile
-
helmfile sync vs helmfile apply
I went through the Helmfile repo Readme to figure out the difference between helmfile sync and helmfile apply. It seems like unlike the apply command, the sync command doesn't do a diff and helm upgrades the hell out of all releases 😃. But from the word sync, you'd expect the command to apply those releases that have been changed. There is also mention of the potential application of helmfile apply to periodically syncing of releases. Why not use helmfile sync for this purpose? Overall, the difference didn't become crystal clear, and I though there could probably be more to it. So, I'm asking.
-
Managing multiple repos
helmfile is something i’ve used in the past for this https://github.com/roboll/helmfile
-
Helm is both "package manager" and "templating engine" - probably the best package manager but horrible template engine
I always felt like dependencies in helm are for very simple non-coupled packages. I many times use Helmfile (https://github.com/roboll/helmfile) to manage dependencies instead of banging my head with vanilla Helm.
-
So I've installed grafana, loki, and prometheus on the personal Kubernetes cluster via Terraform. Now what?
Once you do that, learn to create dynamic helm charts that use go templating and conditionals: https://github.com/roboll/helmfile
What are some alternatives?
cartography - Cartography is a Python tool that consolidates infrastructure assets and the relationships between them in an intuitive graph view powered by a Neo4j database.
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
aws-nuke - Nuke a whole AWS account and delete all its resources.
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
fixinventory - Fix Inventory consolidates user, resource, and configuration data from your cloud environments into a unified, graph-based asset inventory.
helmsman - Helm Charts as Code
pulumi-kubernetesx - Kubernetes for Everyone
kustomize - Customization of kubernetes YAML configurations
awesome-kubernetes - A curated list of awesome references collected since 2018.
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
cloud-security-list - A list of cloud security tools and vendors.
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.