Kubernetes (K8s)

The k8s.io/kubectl repository serves two primary purposes:

1. Issue Tracking: It is used to track issues specifically for the kubectl CLI distributed with the main Kubernetes project.
2. Client Library Packages: It contains Go packages intended for use by client programs. These packages are vendored into the main k8s.io/kubernetes repository to power the kubectl CLI client and are available for external developers to build client-side tools.

The cri-streaming module provides the Kubernetes Container Runtime Interface (CRI) streaming server implementation. It is specifically designed to handle the following operations:

• Exec: Executing commands within a container.
• Attach: Attaching to a running container.
• PortForward: Forwarding ports to a container.

This module serves as a dedicated, runtime-focused import target, allowing consumers to access CRI streaming functionality without needing to depend on the entire k8s.io/kubelet module surface.

Pod Security Admission provides the implementation for enforcing Pod Security Standards, which are a set of best-practice profiles for running pods securely in a cluster.

This project includes:

• Codified profile definitions for the standards.
• The PodSecurity admission controller (available as both a library and a webhook) to enforce these standards.
• Testing resources to validate that enforcement is working correctly.

For detailed design rationale and history, refer to the KEP: sig-auth/2579-psp-replacement.

Dynamic Resource Allocation (DRA) is a Kubernetes feature designed to provide more flexible and granular resource management. This repository contains the packages required to implement and interact with the DRA feature set.

Note on usage: This specific repository is a staged, read-only version used for importing packages. For development, issues, or pull requests, you must use the main Kubernetes repository at https://github.com/kubernetes/kubernetes.

ExternalJWT provides proto APIs designed to allow plugging in external JSON Web Token (JWT) signing and key management services into Kubernetes. This enables delegating the responsibility of signing service account tokens to an external provider rather than managing keys directly within the Kubernetes control plane.

For the underlying design rationale and architectural details, refer to KEP 740.

The client-go library provides several packages for interacting with a Kubernetes cluster:

• kubernetes: Contains the clientset used to access the standard Kubernetes API.
• discovery: Used to discover which APIs are supported by a specific Kubernetes API server.
• dynamic: Provides a dynamic client capable of performing generic operations on arbitrary Kubernetes API objects (useful when the schema is not known at compile time).
• plugin/pkg/client/auth: Contains optional authentication plugins for obtaining credentials from external sources.
• transport: Used to set up authentication and establish connections.
• tools/cache: A utility package useful when writing Kubernetes controllers.

Kubernetes version 1.8 introduces new features, enhancements, and bug fixes.

• Initial Installations: Refer to the Kubernetes documentation Setup topics for guidance on choosing the right solution.
• Upgrades: If upgrading from a previous version, review the Before Upgrading section in the release notes for required actions.
• Release Details: Changes are organized by Special Interest Groups (SIGs).