fx VS kubectl-jq

Compare fx vs kubectl-jq and see what are their differences.

fx

Terminal JSON viewer & processor (by antonmedv)

kubectl-jq

Kubectl plugin that works like "kubectl get" but runs everything through a JQ program you provide (by jrockway)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
fx kubectl-jq
50 1
18,283 12
- -
9.2 2.6
5 days ago 6 months ago
Go Go
MIT License Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

fx

Posts with mentions or reviews of fx. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-29.

kubectl-jq

Posts with mentions or reviews of kubectl-jq. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-24.
  • An Introduction to JQ
    10 projects | news.ycombinator.com | 24 Aug 2021
    Big fan of JQ. I like it more than the traditional UNIX suite of text manipulation commands, because I get closer to "querying" rather than just filtering. It has really made me rethink where I want "interacting with a computer" to go in the future -- less typing commands, more querying stuff.

    I have a few utilities involving JQ that I wrote.

    For structured logs, I have jlog. Pipe JSON structured logs into it, and it pretty-prints the logs. For example, time zones are converted to your local time, if you choose; or you can make the timestamps relative to each other, or now. It includes jq so that you can select relevant log lines, delete spammy fields, join fields together, etc. Basically, every time you run it, you get the logs YOU want to look at. https://github.com/jrockway/json-logs. Not to oversell it, but this is one of the few pieces of software I've written that passes the toothbrush test -- I use it twice a day, every day. All the documentation is in --help; I should really paste that into the Github readme.

    I am also a big fan of using JQ on Kubernetes objects. I know what I'm looking for, and it's often not in the default table view that kubectl prints. I integrated JQ into a kubectl extension, to save you "-o json | jq" and having to pick apart the v1.List that kubectl marshals objects into. https://github.com/jrockway/kubectl-jq. That one actually has documentation, but there is a fatal flaw -- it doesn't integrate with kubectl tab completion (limitation of k8s.io/cli-runtime), so it's not too good unless you already have a target in mind, or you're targeting everything of a particular resource type. This afternoon I wanted to see the image tag of every pod that wasn't terminated (some old Job runs exist in the namespace), and that's easy to do with JQ: `kubectl jq pods 'select(.status.containerStatuses[].state.terminated == null) | .spec.containers[].image'`. I have no idea how you'd do such a thing without JQ, probably just `kubectl describe pods | grep something` and do the filtering in your head. (The recipes in the kubectl-jq documentation are pretty useful. One time I had a Kubernetes secret that had a key set to a (base64-encoded) JSON file containing a base64-encoded piece of data I wanted. Easy to fix with jq; `.data.THING | @base64d | fromjson | .actualValue | @base64d`.

    JQ is something I definitely can't live without. But I will admit to sometimes preprocessing the input with grep, `select(.key|test("regex"))` is awfully verbose compared to "grep regex" ;)

What are some alternatives?

When comparing fx and kubectl-jq you can also consider the following projects:

jless - jless is a command-line JSON viewer designed for reading, exploring, and searching through JSON data.

dasel - Select, put and delete data from JSON, TOML, YAML, XML and CSV files with a single tool. Supports conversion between formats and can be used as a Go package.

jiq - jid on jq - interactive JSON query tool using jq expressions

jid - json incremental digger

rq - Record Query - A tool for doing record analysis and transformation

ngs - Next Generation Shell (NGS)

murex - A smarter shell and scripting environment with advanced features designed for usability, safety and productivity (eg smarter DevOps tooling)

nnn - nĀ³ The unorthodox terminal file manager

gron - Make JSON greppable!

jj - JSON Stream Editor (command line utility)

shell-scripts - Collection of various shell scripts and utilitites