Skip to main content

Kubejyg

Kubernetes Resource Extraction with Namespace Grouping.

How it works

kubejyg extracts Kubernetes resources across multiple namespaces, grouping them by namespace. The output is generated in either JSON or YAML, ready to be piped into well known processors like jq, yq, and grep.

Examples

Fetch all deployment manifests from all namespaces in YAML.

kubejyg | yq ".Namespaces.[].[].[].Deployments" -C

Fetch all deployment manifests across all namespaces in YAML and filter nulls.

kubejyg | yq ".Namespaces[].[].[].Deployments | select ( . != null ) | .[]" -C

Fetch all the annotations from all the Services across all Namespaces in JSON.

kubejyg -o json | jq ".Namespaces[].[].[].Services | select ( . != null) | .[].metadata.annotations" -C

Output structure

{
    "Namespaces": [
        {
            "ns-1": [
                {
                    "Deployments": [
                        {
                            deployment-manifest-1
                        }
                        ...
                    ]
                    "Services": [
                        {
                            service-manifest-1
                        }
                        ...
                    ]
                    "Ingress": [
                        {
                            ingress-manifest-1
                        }
                        ...
                    ]
                }
            ]
        ...
        }
    ]
}

Installation

pip install kubejyg

Features

Kubernetes resources:

  • Deployments
  • Services
  • Ingresses

Output:

  • YAML
  • JSON

Naming

kubejyg is named after the following utilities:

  1. kubectl
  2. jq
  3. yq
  4. grep

Gotchas

jq: error (at <stdin>:1): Cannot iterate over null (null).

Some namespaces might not contain resources of all kinds. If we apply filters over empty arrays, jq and yq will replaces those arrays with null values. Applying filters over them will error out. Use select ( . != null) to filter null expressions, see examples for details.

Contributing

  1. Create an issue
  2. Fork
  3. Change
  4. Open PR
  5. Profit!

Metadata

Release files for kubejyg 0.3.17

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for kubejyg 0.3.17
File Size Uploaded
kubejyg-0.3.17.tar.gz 16.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for kubejyg 0.3.17
File Interpreter ABI Platform
kubejyg-0.3.17-py3-none-any.whl Python 3 none any Details

Total release size: 34.4 kB

Release files / kubejyg-0.3.17.tar.gz

Download URL kubejyg-0.3.17.tar.gz
Size 16.7 kB
Tags Source
SHA-256 checksum
How to use checksums
8890436f78011499a72ae33550e7f017083815b6c7f623540b2ba818d855942d
BLAKE2b-256 checksum
How to use checksums
6b816257699de8af1834a3b7727761a8449e4136fba53aaac4ce9eb0c08f7576
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 30, 2025.

Transparency log

Release files / kubejyg-0.3.17-py3-none-any.whl

Download URL kubejyg-0.3.17-py3-none-any.whl
Size 17.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
238fb0f8a62a1f0a1e81c003402e99357cc2bd85b6dac391b96f0999628a69e7
BLAKE2b-256 checksum
How to use checksums
739142d5ef10b97a0005506eec8013f428152d9303633dfa5b280ff527823821
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 30, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.17 This release

2 release files

0.2.17

2 release files

0.0.16

2 release files

0.0.15

2 release files

0.0.14

2 release files

0.0.13

2 release files

0.0.12

2 release files

0.0.11

2 release files

0.0.10

2 release files

0.0.9

2 release files

0.0.8

2 release files

0.0.7

2 release files

0.0.6

2 release files

0.0.5

2 release files

0.0.4

2 release files

0.0.3

2 release files

0.0.2

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page