Skip to content

cub k8s types

cub k8s types

List the Kubernetes resource types stored in ConfigHub

Synopsis

List the Kubernetes resource types present in ConfigHub Units, with how many resources, Units, and Spaces each spans.

This answers "what is actually in here?" — useful before a fleet-wide query, and for discovering which custom resource types a cluster's configuration uses. It accepts the same filters as "cub k8s get" and, optionally, the same type argument to narrow the survey.

Examples:

  # Every resource type in a space
  cub k8s types --space my-space

  # Every resource type across the organization
  cub k8s types --space "*"

  # Everything except CustomResourceDefinitions
  cub k8s types all --space "*"

  # Types delivered to one target
  cub k8s types --target prod-use2/prod-use2-oci

  # Just the type names, for scripting
  cub k8s types --space "*" -o name
cub k8s types [<type>[,<type>...]] [flags]

Options

      --component string              the Component of --variant, when that names the variant alone; --variant <component>/<variant> says the same in one flag
      --filter string                 Filter entity to apply to the list. Specify as 'space/filter' for cross-space filters or just 'filter' for current space. Supports both slugs and UUIDs. The filter will be combined with any --where clause using AND logic. Examples: "production-filters/security-check", "my-filter-uuid", "validation-rules"
  -h, --help                          help for types
      --include-hidden string[="*"]   Also select hidden entities, to list or to act on: those hidden for the given HiddenReasons, comma-separated, as in --include-hidden=BackingUnit, or for any reason when given no value or "*". ConfigHub/YAML Units, which hold the configuration of other entities, are hidden with the reason BackingUnit. A --where naming entities by Slug or ID selects them whether hidden or not
  -n, --namespace string              only resources in this Kubernetes namespace
      --no-headers                    Don't print headers for table output
  -o, --output string                 Output format. One of: json, yaml, name, wide, mutations, jq=<expr>, yq=<expr>, custom-columns=<spec>
      --quiet                         No default output.
      --space string                  space to operate in, by slug or UUID. Omitted, a list or bulk operation spans the organization and a single entity is named as <space>/<slug>
      --target strings                only Units bound to these targets, as space-slug/target-slug (can be repeated or comma-separated); implies --space '*' unless --space is given
      --variant string                variant to operate in, as <component>/<variant>, or as <variant> with --component: the space naming that Component whose Variant label is <variant>. The same scope as --space, named by what it is rather than by the space's slug; the two cannot be combined
      --verbose                       Detailed output, additive with default output
      --where string                  Filter expression using SQL-inspired syntax. Supports conjunctions with AND. String operators: =, !=, <, >, <=, >=, LIKE, NOT LIKE, ILIKE, ~~, !~~, ~, ~*, !~, !~*. Pattern matching with LIKE/ILIKE uses % and _ wildcards. Regex operators (~, ~*, !~, !~*) support POSIX regular expressions. A related entity is referenced by prefix, as in "UpstreamUnit.Slug = 'base'"; when the reference names a list, a * segment matches any element, as in "FromLink.*.Slug = 'upgrade-app'". Examples: "Slug LIKE 'app-%'", "DisplayName ILIKE '%backend%'", "Slug ~ '^[a-z]+-[0-9]+$'"
      --where-resource string         additional filter on individual resources, ANDed with the resource type; e.g. "spec.replicas > 1"

Options inherited from parent commands

      --context string   The context to use for this command
      --debug            Debug output

SEE ALSO