inspektor-gadget
Flatcar
Our great sponsors
inspektor-gadget | Flatcar | |
---|---|---|
8 | 20 | |
1,932 | 627 | |
4.7% | 2.6% | |
9.9 | 7.5 | |
1 day ago | 11 days ago | |
C | Python | |
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.
inspektor-gadget
-
Running tcpdump on eks worker nodes
You can try using https://www.inspektor-gadget.io/ You can try either, top tcp, trace network-graph or trace tcp gadget. It's a CNCF sandbox project and it's kubernetes native so I think this should work.
-
Is there any OSS tool out there that would translate traffic flows into NetworkPolicies?
This works really well https://github.com/inspektor-gadget/inspektor-gadget/blob/main/docs/gadgets/advise/network-policy.md
-
Getting started with kubectl plugins
Link to GitHub Repository
-
Isolating Kubernetes pods for debugging
Inspector gadget is a tool designed to introspect and debug Kubernetes applications using eBPF.
-
What are some useful Kubernetes tools you can share?
I found this tool: https://github.com/kinvolk/inspektor-gadget great if you want to have a detailed debugging for running pods e.g all exec system calls or trace tcp connections etc.
- Inspektor Gadget
-
Kubernetes Security Checklist 2021
All namespaces should have NetworkPolicy. Interactions between namespaces should be limited to NetworkPolicy following least privileges principles (Inspektor Gadget)
-
How to Trace Linux System Calls in Production with Minimal Impact on Performance
The team behind traceloop has integrated it with the Inspektor Gadget project, so you can run traceloop on the K8s platform using kubectl. See the demos in Inspektor Gadget - How to use and, if you like, try it on your own.
Flatcar
- Linux fu: getting started with systemd
- Bottlerocket – Minimal, immutable Linux OS with verified boot
-
Wolfi: A community Linux OS designed for the container and cloud-native era
Sounds like you're looking for the CoreOS Linux successor FlatCar https://www.flatcar.org/
It's actually based on some ChromeOS update tools under the hood but is a regular Linux distro, just super minimal and designed to run containers.
-
Flatcar Container Linux
I guess if you found my comment to be "comically hyperbolic" then replying to mine with a "comically reductionist" is fair game
So, anyway, I actually did dig up a concrete example of my experience with it, and I cannot link to the "Additional information" section but that is both why I think the thing was a mess and also why the Miroservices YT joke resonated: https://github.com/flatcar/Flatcar/issues/220
I think the CoreOS boot strategy was decomposed into a bunch of different executables, each responsible for doing their own little slice of the world. Maybe it drew inspiration from systemd in that way. But, just like my real life experience with microservices, it requires keeping a bunch of different projects and their upgrade paths in ones head, knowing their disparate config formats, and when one of them inevitably has a bug, understanding how to troubleshoot what went wrong with the system as a whole
And, again in trying to be reasonable in this discussion[1] I do also understand why one would opt for the data URI, given how much of the rest of Ignition loads content from URLs. I don't believe cloud-init has that remote content paradigm baked into in nearly the same way, so I hear you about that.
And yes, my belief is that JSON is a data-exchange format from _computer to computer_ and making people write them is a poor DX choice, IN MY OPINION. And, to reiterate, I know that CoreOS's perspective is that it is a computer-to-computer transmission from the transpiler-project-o-the-day to the Ignition binary, but that is predicated on one having access to that transpiler binary in all cases, which is quite different from the problem that cloud-init is trying to solve
fn-1: I'm sorry you got hurt by my "tire fire" outburst, and that evidently derailed this whole interaction, but it was my experience
- An overview of single-purpose Linux distributions
- Linux Distro for Running Docker Containers in VM - Ubuntu, Alpine, or...?
What are some alternatives?
syft - CLI tool and library for generating a Software Bill of Materials from container images and filesystems
bottlerocket - An operating system designed for hosting containers
falco - Cloud Native Runtime Security
harvester - Open source hyperconverged infrastructure (HCI) software
kubesess - Kubectl plugin managing sessions
talos - Talos Linux is a modern Linux distribution built for Kubernetes.
security-profiles-operator - The Kubernetes Security Profiles Operator
typhoon - Minimal and free Kubernetes distribution with Terraform
go2seccomp - Generate seccomp profiles from go binaries
elemental-toolkit - :snowflake: The toolkit to build, ship and maintain cloud-init driven Linux derivatives based on container images
kubescape - Kubescape is an open-source Kubernetes security platform for your IDE, CI/CD pipelines, and clusters. It includes risk analysis, security, compliance, and misconfiguration scanning, saving Kubernetes users and administrators precious time, effort, and resources.
headlamp - A Kubernetes web UI that is fully-featured, user-friendly and extensible