CloudGraph cli
rook
CloudGraph cli | rook | |
---|---|---|
24 | 51 | |
870 | 11,931 | |
0.3% | 0.6% | |
1.3 | 9.9 | |
6 months ago | 8 days ago | |
TypeScript | Go | |
Mozilla Public 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.
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
rook
-
Ceph: A Journey to 1 TiB/s
I have some experience with Ceph, both for work, and with homelab-y stuff.
First, bear in mind that Ceph is a distributed storage system - so the idea is that you will have multiple nodes.
For learning, you can definitely virtualise it all on a single box - but you'll have a better time with discrete physical machines.
Also, Ceph does prefer physical access to disks (similar to ZFS).
And you do need decent networking connectivity - I think that's the main thing people think of, when they think of high hardware requirements for Ceph. Ideally 10Gbe at the minimum - although more if you want higher performance - there can be a lot of network traffic, particularly with things like backfill. (25Gbps if you can find that gear cheap for homelab - 50Gbps is a technological dead-end. 100Gbps works well).
But honestly, for a homelab, a cheap mini PC or NUC with 10Gbe will work fine, and you should get acceptable performance, and it'll be good for learning.
You can install Ceph directly on bare-metal, or if you want to do the homelab k8s route, you can use Rook (https://rook.io/).
Hope this helps, and good luck! Let me know if you have any other questions.
-
Running stateful workloads on Kubernetes with Rook Ceph
Another option is to leverage a Kubernetes-native distributed storage solution such as Rook Ceph as the storage backend for stateful components running on Kubernetes. This has the benefit of simplifying application configuration while addressing business requirements for data backup and recovery such as the ability to take volume snapshots at a regular interval and perform application-level data recovery in case of a disaster.
-
People who run Nextcloud in Docker: Where do you store your data/files? In a Docker volume, or on a remote server/NAS?
This is beyond your question but might help someone else: I switch from docker-compose to kubernetes for my home lab a while ago. The storage solution I've settled on is Rook. It was a bit of up-front work learning how to get it up but now that it's done my storage is automatically managed by Ceph. I can swap out drives and Ceph basically takes care of everything itself.
-
Rook/Ceph with VM nodes on research cluster?
The stumbling point I am at is I want to use rook.io(Ceph) as my storage solution for the cluster. The Ceph prerequisites are one of the following:
-
Asking for recommendation on remote Kubernetes storage for a small cluster and databases
Have you looked at Rook?
-
Want advice on planned evolution: k3os/Longhorn --> Talos/Ceph, plus Consul and Vault
I've briefly run ceph in an external mode, you can actually use a rook deployment to manage it (sort of). Here is the documentation for doing that. For me it didn't pass my testing phase because I need better networking equipment before I can try that.
-
ATARI is still alive: Atari Partition of Fear
This article explains the data corruption issue happened in Rook in 2021. The root cause lies in an unexpected place and can also occurs in all Ceph environment. It's interesting that Rook had started to encounter this problem recently even though this problem has existed for a long time. It's due to a series of coincidences. I wrote this article because the word "Atari" used in a non-historical context in 2021.
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 2/2
Rook (this is a nice article for Rook NFS)
-
Running on-premise k8s with a small team: possible or potential nightmare?
Storage: Favor any distributed storage you know to start with for Persistent Volumes: Ceph maybe via rook.io, Longhorn if you go rancher etc
-
My completely automated Homelab featuring Kubernetes
I've dealt with a lot of issues that are very close to just unplugging a node. Unfortunately on node lost, my stateful workloads using rook-ceph block storage won't migrate over to another node automatically due to an issue with rook. Stateless apps (ingress nginx, etc..) not using rook-ceph block failover to another node just fine. I've kind of accepted this for now and I know Longhorn has a feature that makes this work but I find rook-ceph to be more stable for my workloads.
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.
longhorn - Cloud-Native distributed storage built on and for Kubernetes
aws-nuke - Nuke a whole AWS account and delete all its resources.
ceph-csi - CSI driver for Ceph
fixinventory - Fix Inventory consolidates user, resource, and configuration data from your cloud environments into a unified, graph-based asset inventory.
velero - Backup and migrate Kubernetes applications and their persistent volumes
pulumi-kubernetesx - Kubernetes for Everyone
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
awesome-kubernetes - A curated list of awesome references collected since 2018.
Ceph - Ceph is a distributed object, block, and file storage platform
cloud-security-list - A list of cloud security tools and vendors.
hub-feedback - Feedback and bug reports for the Docker Hub