This topic discusses multiple ways to interact with clusters. Accessing for the first time with kubectl When accessing the Kubernetes API for the first time, we suggest using the Kubernetes CLI, kubectl. To access a cluster, you need to know the location of the cluster and have credentials to access it. Typically, this is automatically set-up when you work through a Getting started guide, or someone else set up the cluster and provided you with credentials and a location.| Kubernetes
This section of the Kubernetes documentation contains references. API Reference Glossary - a comprehensive, standardized list of Kubernetes terminology Kubernetes API Reference One-page API Reference for Kubernetes v1.32 Using The Kubernetes API - overview of the API for Kubernetes. API access control - details on how Kubernetes controls API access Well-Known Labels, Annotations and Taints Officially supported client libraries To call the Kubernetes API from a programming language, you can us...| Kubernetes
The OpenAPI Specification defines a standard interface to RESTful APIs which allows both humans and computers to understand service capabilities without access to source code, documentation, or network traffic inspection.| swagger.io
Custom resources are extensions of the Kubernetes API. This page discusses when to add a custom resource to your Kubernetes cluster and when to use a standalone service. It describes the two methods for adding custom resources and how to choose between them. Custom resources A resource is an endpoint in the Kubernetes API that stores a collection of API objects of a certain kind; for example, the built-in pods resource contains a collection of Pod objects.| Kubernetes
Swagger UI allows development team to visualize and interact with the API’s resources without having any of the implementation logic in place. Learn more.| swagger.io