Use the REST API to manage protected branches.

Use the REST API to interact with GitHub Apps

Use the REST API to retrieve and update code scanning alerts from a repository.

Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Hide navigatio...

expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

expand all collapse all Getting started Vespa Overview Features Vespa CLI vespa vespa activate vespa auth vespa clone...

Use kubectl patch to update Kubernetes API objects in place. Do a strategic merge patch or a JSON merge patch.

Glossary This glossary is intended to be a comprehensive, standardized list of Kubernetes terminology. It includes te...

FEATURE STATE: Kubernetes v1.22 [stable] (enabled by default: true) Kubernetes supports multiple appliers collaborating to manage the fields of a single object. Server-Side Apply provides an optional mechanism for your cluster's control plane to track changes to an object's fields. At the level of a specific resource, Server-Side Apply records and tracks information about control over the fields of that object. Server-Side Apply helps users and controllers manage their resources through declarative configuration.

This page provides an overview of authentication in Kubernetes, with a focus on authentication to the Kubernetes API. Users in Kubernetes All Kubernetes clusters have two categories of users: service accounts managed by Kubernetes, and normal users. It is assumed that a cluster-independent service manages normal users in the following ways: an administrator distributing private keys a user store like Keystone or Google Accounts a file with a list of usernames and passwords In this regard, Kubernetes does not have objects which represent normal user accounts.