Skip to content

kubectl explain not showing spec field documentation for eventlisteners, triggertemplates, interceptors, etc. #1834

@kaleal

Description

@kaleal

Expected Behavior

When running kubectl explain eventlistener the spec field documentation is not shown. Several other objects have the same issue. Perhaps there is a common cause.

Actual Behavior

Only apiVersion, kind, and metadata are shown.

$ kubectl explain eventlistener
GROUP:      triggers.tekton.dev
KIND:       EventListener
VERSION:    v1beta1

DESCRIPTION:
    <empty>
FIELDS:
  apiVersion	<string>
    APIVersion defines the versioned schema of this representation of an object.
    Servers should convert recognized schemas to the latest internal value, and
    may reject unrecognized values. More info:
    https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources

  kind	<string>
    Kind is a string value representing the REST resource this object
    represents. Servers may infer this from the endpoint the client submits
    requests to. Cannot be updated. In CamelCase. More info:
    https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds

  metadata	<ObjectMeta>
    Standard object's metadata. More info:
    https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
$ kubectl explain eventlistener.spec
GROUP:      triggers.tekton.dev
KIND:       EventListener
VERSION:    v1beta1

error: field "spec" does not exist

Steps to Reproduce the Problem

  1. Run kubectl explain clusterinterceptors
  2. Run kubectl explain clustertriggerbindings
  3. Run kubectl explain eventlisteners
  4. Run kubectl explain interceptors
  5. Run kubectl explain triggerbindings
  6. Run kubectl explain triggers
  7. Run kubectl explain triggertemplates

Additional Info

  • Kubernetes version:

    Output of kubectl version:

$ kubectl version
Client Version: v1.32.0
Kustomize Version: v5.5.0
Server Version: v1.32.0
  • Tekton Pipeline version:

    Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'

v0.70.0

For the others objects it seems to be working fine. The example below shows the pipeline documentation.

$ kubectl explain pipeline.spec.params.type
GROUP:      tekton.dev
KIND:       Pipeline
VERSION:    v1

FIELD: type <string>


DESCRIPTION:
    Type is the user-specified type of the parameter. The possible types
    are currently "string", "array" and "object", and "string" is the default.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions