Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 1. Metadata APIs

1.1. APIRequestCount [apiserver.openshift.io/v1]
Copy link

Description
APIRequestCount tracks requests made to an API. The instance name must be of the form resource.version.group, matching the resource. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).
Type
object

1.2. Binding [v1]
Copy link

Description
Binding ties one object to another; for example, a pod is bound to a node by a scheduler.
Type
object

1.3. ComponentStatus [v1]
Copy link

Description
ComponentStatus (and ComponentStatusList) holds the cluster validation info. Deprecated: This API is deprecated in v1.19+
Type
object

1.4. ConfigMap [v1]
Copy link

Description
ConfigMap holds configuration data for pods to consume.
Type
object

1.5. ControllerRevision [apps/v1]
Copy link

Description
ControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.
Type
object

1.6. Event [events.k8s.io/v1]
Copy link

Description
Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.
Type
object

1.7. Event [v1]
Copy link

Description
Event is a report of an event somewhere in the cluster. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.
Type
object

1.8. Lease [coordination.k8s.io/v1]
Copy link

Description
Lease defines a lease concept.
Type
object

1.9. Namespace [v1]
Copy link

Description
Namespace provides a scope for Names. Use of multiple namespaces is optional.
Type
object
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat