kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
website/static/docs/reference/generated/kubernetes-api/v1.11/index.html

48559 lines
3.5 MiB
Executable File
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!DOCTYPE html>
<HTML>
<HEAD>
<META charset="UTF-8">
<TITLE>Kubernetes API Reference Docs</TITLE>
<LINK rel="shortcut icon" href="favicon.ico" type="image/vnd.microsoft.icon">
<LINK rel="stylesheet" href="css/bootstrap.min.css">
<LINK rel="stylesheet" href="css/font-awesome.min.css" type="text/css">
<LINK rel="stylesheet" href="css/stylesheet.css" type="text/css">
</HEAD>
<BODY>
<DIV id="sidebar-wrapper" class="side-nav side-bar-nav">
<UL>
<LI class="nav-level-1 strong-nav"><A href="#-strong-api-overview-strong-" class="nav-item"><STRONG>Overview</STRONG></A></LI>
</UL>
<UL>
<LI class="nav-level-1 strong-nav"><A href="#-strong-workloads-apis-strong-" class="nav-item"><STRONG>WORKLOADS APIS</STRONG></A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#container-v1-core" class="nav-item">Container v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#cronjob-v1beta1-batch" class="nav-item">CronJob v1beta1 batch</A></LI>
<UL id="cronjob-v1beta1-batch-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-cronjob-v1beta1-batch-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-cronjob-v1beta1-batch-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-cronjob-v1beta1-batch" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-cronjob-v1beta1-batch" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-cronjob-v1beta1-batch" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-cronjob-v1beta1-batch" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-cronjob-v1beta1-batch" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-cronjob-v1beta1-batch-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-cronjob-v1beta1-batch-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-cronjob-v1beta1-batch" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-cronjob-v1beta1-batch" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-cronjob-v1beta1-batch" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-cronjob-v1beta1-batch" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-cronjob-v1beta1-batch" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-cronjob-v1beta1-batch" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-cronjob-v1beta1-batch-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-cronjob-v1beta1-batch-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-cronjob-v1beta1-batch" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-cronjob-v1beta1-batch" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-cronjob-v1beta1-batch" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#daemonset-v1-apps" class="nav-item">DaemonSet v1 apps</A></LI>
<UL id="daemonset-v1-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-daemonset-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-daemonset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-daemonset-v1-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-daemonset-v1-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-daemonset-v1-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-daemonset-v1-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-daemonset-v1-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-daemonset-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-daemonset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-daemonset-v1-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-daemonset-v1-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-daemonset-v1-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-daemonset-v1-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-daemonset-v1-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-daemonset-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-daemonset-v1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-daemonset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-daemonset-v1-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-daemonset-v1-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-daemonset-v1-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#deployment-v1-apps" class="nav-item">Deployment v1 apps</A></LI>
<UL id="deployment-v1-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-deployment-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-deployment-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-deployment-v1-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-deployment-v1-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-deployment-v1-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-deployment-v1-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-deployment-v1-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-deployment-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-deployment-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-deployment-v1-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-deployment-v1-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-deployment-v1-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-deployment-v1-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-deployment-v1-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-deployment-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-deployment-v1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-deployment-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-deployment-v1-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-deployment-v1-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-deployment-v1-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-deployment-v1-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-deployment-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-deployment-v1-apps" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-deployment-v1-apps" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-deployment-v1-apps" class="nav-item">Patch Scale</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#job-v1-batch" class="nav-item">Job v1 batch</A></LI>
<UL id="job-v1-batch-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-job-v1-batch-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-job-v1-batch-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-job-v1-batch" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-job-v1-batch" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-job-v1-batch" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-job-v1-batch" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-job-v1-batch" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-job-v1-batch-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-job-v1-batch-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-job-v1-batch" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-job-v1-batch" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-job-v1-batch" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-job-v1-batch" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-job-v1-batch" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-job-v1-batch" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-job-v1-batch-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-job-v1-batch-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-job-v1-batch" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-job-v1-batch" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-job-v1-batch" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#pod-v1-core" class="nav-item">Pod v1 core</A></LI>
<UL id="pod-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-pod-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-pod-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#create-eviction-pod-v1-core" class="nav-item">Create Eviction</A></LI>
<LI class="nav-level-2"><A href="#patch-pod-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-pod-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-pod-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-pod-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-pod-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-pod-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-pod-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-pod-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-pod-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-pod-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-pod-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-pod-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-pod-v1-core" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-pod-v1-core" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-pod-v1-core" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-proxy-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Proxy Operations</STRONG></A></LI>
<UL id="-strong-proxy-operations-pod-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-connect-portforward-pod-v1-core" class="nav-item">Create Connect Portforward</A></LI>
<LI class="nav-level-2"><A href="#create-connect-proxy-pod-v1-core" class="nav-item">Create Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#create-connect-proxy-path-pod-v1-core" class="nav-item">Create Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#delete-connect-proxy-pod-v1-core" class="nav-item">Delete Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#delete-connect-proxy-path-pod-v1-core" class="nav-item">Delete Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#get-connect-portforward-pod-v1-core" class="nav-item">Get Connect Portforward</A></LI>
<LI class="nav-level-2"><A href="#get-connect-proxy-pod-v1-core" class="nav-item">Get Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#get-connect-proxy-path-pod-v1-core" class="nav-item">Get Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#head-connect-proxy-pod-v1-core" class="nav-item">Head Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#head-connect-proxy-path-pod-v1-core" class="nav-item">Head Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#replace-connect-proxy-pod-v1-core" class="nav-item">Replace Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#replace-connect-proxy-path-pod-v1-core" class="nav-item">Replace Connect Proxy Path</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-pod-v1-core-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-pod-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-log-pod-v1-core" class="nav-item">Read Log</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#replicaset-v1-apps" class="nav-item">ReplicaSet v1 apps</A></LI>
<UL id="replicaset-v1-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-replicaset-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-replicaset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-replicaset-v1-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-replicaset-v1-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-replicaset-v1-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-replicaset-v1-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-replicaset-v1-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-replicaset-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-replicaset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-replicaset-v1-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-replicaset-v1-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-replicaset-v1-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-replicaset-v1-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-replicaset-v1-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-replicaset-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-replicaset-v1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-replicaset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-replicaset-v1-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-replicaset-v1-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-replicaset-v1-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-replicaset-v1-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-replicaset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-replicaset-v1-apps" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-replicaset-v1-apps" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-replicaset-v1-apps" class="nav-item">Patch Scale</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#replicationcontroller-v1-core" class="nav-item">ReplicationController v1 core</A></LI>
<UL id="replicationcontroller-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-replicationcontroller-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-replicationcontroller-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-replicationcontroller-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-replicationcontroller-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-replicationcontroller-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-replicationcontroller-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-replicationcontroller-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-replicationcontroller-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-replicationcontroller-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-replicationcontroller-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-replicationcontroller-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-replicationcontroller-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-replicationcontroller-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-replicationcontroller-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-replicationcontroller-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-replicationcontroller-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-replicationcontroller-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-replicationcontroller-v1-core" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-replicationcontroller-v1-core" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-replicationcontroller-v1-core" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-replicationcontroller-v1-core-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-replicationcontroller-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-replicationcontroller-v1-core" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-replicationcontroller-v1-core" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-replicationcontroller-v1-core" class="nav-item">Patch Scale</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#statefulset-v1-apps" class="nav-item">StatefulSet v1 apps</A></LI>
<UL id="statefulset-v1-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-statefulset-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-statefulset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-statefulset-v1-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-statefulset-v1-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-statefulset-v1-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-statefulset-v1-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-statefulset-v1-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-statefulset-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-statefulset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-statefulset-v1-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-statefulset-v1-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-statefulset-v1-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-statefulset-v1-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-statefulset-v1-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-statefulset-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-statefulset-v1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-statefulset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-statefulset-v1-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-statefulset-v1-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-statefulset-v1-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-statefulset-v1-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-statefulset-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-statefulset-v1-apps" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-statefulset-v1-apps" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-statefulset-v1-apps" class="nav-item">Patch Scale</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1 strong-nav"><A href="#-strong-service-apis-strong-" class="nav-item"><STRONG>SERVICE APIS</STRONG></A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#endpoints-v1-core" class="nav-item">Endpoints v1 core</A></LI>
<UL id="endpoints-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-endpoints-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-endpoints-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-endpoints-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-endpoints-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-endpoints-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-endpoints-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-endpoints-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-endpoints-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-endpoints-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-endpoints-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-endpoints-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-endpoints-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-endpoints-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-endpoints-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-endpoints-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#ingress-v1beta1-extensions" class="nav-item">Ingress v1beta1 extensions</A></LI>
<UL id="ingress-v1beta1-extensions-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-ingress-v1beta1-extensions-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-ingress-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-ingress-v1beta1-extensions" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-ingress-v1beta1-extensions" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-ingress-v1beta1-extensions" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-ingress-v1beta1-extensions" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-ingress-v1beta1-extensions" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-ingress-v1beta1-extensions-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-ingress-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-ingress-v1beta1-extensions" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-ingress-v1beta1-extensions" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-ingress-v1beta1-extensions" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-ingress-v1beta1-extensions" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-ingress-v1beta1-extensions" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-ingress-v1beta1-extensions" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-ingress-v1beta1-extensions-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-ingress-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-ingress-v1beta1-extensions" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-ingress-v1beta1-extensions" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-ingress-v1beta1-extensions" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#service-v1-core" class="nav-item">Service v1 core</A></LI>
<UL id="service-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-service-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-service-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-service-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-service-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-service-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-service-v1-core" class="nav-item">Delete</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-service-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-service-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-service-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-service-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-service-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-service-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-service-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-service-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-service-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-service-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-service-v1-core" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-service-v1-core" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-service-v1-core" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-proxy-operations-service-v1-core-strong-" class="nav-item"><STRONG>Proxy Operations</STRONG></A></LI>
<UL id="-strong-proxy-operations-service-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-connect-proxy-service-v1-core" class="nav-item">Create Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#create-connect-proxy-path-service-v1-core" class="nav-item">Create Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#delete-connect-proxy-service-v1-core" class="nav-item">Delete Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#delete-connect-proxy-path-service-v1-core" class="nav-item">Delete Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#get-connect-proxy-service-v1-core" class="nav-item">Get Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#get-connect-proxy-path-service-v1-core" class="nav-item">Get Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#head-connect-proxy-service-v1-core" class="nav-item">Head Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#head-connect-proxy-path-service-v1-core" class="nav-item">Head Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#replace-connect-proxy-service-v1-core" class="nav-item">Replace Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#replace-connect-proxy-path-service-v1-core" class="nav-item">Replace Connect Proxy Path</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1 strong-nav"><A href="#-strong-config-and-storage-apis-strong-" class="nav-item"><STRONG>CONFIG AND STORAGE APIS</STRONG></A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#configmap-v1-core" class="nav-item">ConfigMap v1 core</A></LI>
<UL id="configmap-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-configmap-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-configmap-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-configmap-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-configmap-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-configmap-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-configmap-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-configmap-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-configmap-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-configmap-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-configmap-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-configmap-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-configmap-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-configmap-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-configmap-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-configmap-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#secret-v1-core" class="nav-item">Secret v1 core</A></LI>
<UL id="secret-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-secret-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-secret-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-secret-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-secret-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-secret-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-secret-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-secret-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-secret-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-secret-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-secret-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-secret-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-secret-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-secret-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-secret-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-secret-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#persistentvolumeclaim-v1-core" class="nav-item">PersistentVolumeClaim v1 core</A></LI>
<UL id="persistentvolumeclaim-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-persistentvolumeclaim-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-persistentvolumeclaim-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-persistentvolumeclaim-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-persistentvolumeclaim-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-persistentvolumeclaim-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-persistentvolumeclaim-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-persistentvolumeclaim-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-persistentvolumeclaim-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-persistentvolumeclaim-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-persistentvolumeclaim-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-persistentvolumeclaim-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-persistentvolumeclaim-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-persistentvolumeclaim-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-persistentvolumeclaim-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-persistentvolumeclaim-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-persistentvolumeclaim-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-persistentvolumeclaim-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-persistentvolumeclaim-v1-core" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-persistentvolumeclaim-v1-core" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-persistentvolumeclaim-v1-core" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#storageclass-v1-storage-k8s-io" class="nav-item">StorageClass v1 storage.k8s.io</A></LI>
<UL id="storageclass-v1-storage-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-storageclass-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-storageclass-v1-storage-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-storageclass-v1-storage-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-storageclass-v1-storage-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-storageclass-v1-storage-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-storageclass-v1-storage-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-storageclass-v1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-storageclass-v1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-storageclass-v1-storage-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-storageclass-v1-storage-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-storageclass-v1-storage-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-storageclass-v1-storage-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-storageclass-v1-storage-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#volume-v1-core" class="nav-item">Volume v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#volumeattachment-v1beta1-storage-k8s-io" class="nav-item">VolumeAttachment v1beta1 storage.k8s.io</A></LI>
<UL id="volumeattachment-v1beta1-storage-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-volumeattachment-v1beta1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-volumeattachment-v1beta1-storage-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-volumeattachment-v1beta1-storage-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-volumeattachment-v1beta1-storage-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-volumeattachment-v1beta1-storage-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-volumeattachment-v1beta1-storage-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-volumeattachment-v1beta1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-volumeattachment-v1beta1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-volumeattachment-v1beta1-storage-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-volumeattachment-v1beta1-storage-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-volumeattachment-v1beta1-storage-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-volumeattachment-v1beta1-storage-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-volumeattachment-v1beta1-storage-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1 strong-nav"><A href="#-strong-metadata-apis-strong-" class="nav-item"><STRONG>METADATA APIS</STRONG></A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#controllerrevision-v1-apps" class="nav-item">ControllerRevision v1 apps</A></LI>
<UL id="controllerrevision-v1-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-controllerrevision-v1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-controllerrevision-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-controllerrevision-v1-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-controllerrevision-v1-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-controllerrevision-v1-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-controllerrevision-v1-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-controllerrevision-v1-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-controllerrevision-v1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-controllerrevision-v1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-controllerrevision-v1-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-controllerrevision-v1-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-controllerrevision-v1-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-controllerrevision-v1-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-controllerrevision-v1-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-controllerrevision-v1-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">CustomResourceDefinition v1beta1 apiextensions.k8s.io</A></LI>
<UL id="customresourcedefinition-v1beta1-apiextensions-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-customresourcedefinition-v1beta1-apiextensions-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-customresourcedefinition-v1beta1-apiextensions-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-customresourcedefinition-v1beta1-apiextensions-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-customresourcedefinition-v1beta1-apiextensions-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-customresourcedefinition-v1beta1-apiextensions-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-customresourcedefinition-v1beta1-apiextensions-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-customresourcedefinition-v1beta1-apiextensions-k8s-io" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#event-v1-core" class="nav-item">Event v1 core</A></LI>
<UL id="event-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-event-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-event-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-event-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-event-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-event-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-event-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-event-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-event-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-event-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-event-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-event-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-event-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-event-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-event-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-event-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#limitrange-v1-core" class="nav-item">LimitRange v1 core</A></LI>
<UL id="limitrange-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-limitrange-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-limitrange-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-limitrange-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-limitrange-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-limitrange-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-limitrange-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-limitrange-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-limitrange-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-limitrange-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-limitrange-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-limitrange-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-limitrange-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-limitrange-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-limitrange-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-limitrange-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#horizontalpodautoscaler-v1-autoscaling" class="nav-item">HorizontalPodAutoscaler v1 autoscaling</A></LI>
<UL id="horizontalpodautoscaler-v1-autoscaling-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-horizontalpodautoscaler-v1-autoscaling" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-horizontalpodautoscaler-v1-autoscaling" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-horizontalpodautoscaler-v1-autoscaling" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">InitializerConfiguration v1alpha1 admissionregistration.k8s.io</A></LI>
<UL id="initializerconfiguration-v1alpha1-admissionregistration-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-initializerconfiguration-v1alpha1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-initializerconfiguration-v1alpha1-admissionregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-initializerconfiguration-v1alpha1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-initializerconfiguration-v1alpha1-admissionregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-initializerconfiguration-v1alpha1-admissionregistration-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">MutatingWebhookConfiguration v1beta1 admissionregistration.k8s.io</A></LI>
<UL id="mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">ValidatingWebhookConfiguration v1beta1 admissionregistration.k8s.io</A></LI>
<UL id="validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#podtemplate-v1-core" class="nav-item">PodTemplate v1 core</A></LI>
<UL id="podtemplate-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-podtemplate-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-podtemplate-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-podtemplate-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-podtemplate-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-podtemplate-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-podtemplate-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-podtemplate-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-podtemplate-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-podtemplate-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-podtemplate-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-podtemplate-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-podtemplate-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-podtemplate-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-podtemplate-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-podtemplate-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#poddisruptionbudget-v1beta1-policy" class="nav-item">PodDisruptionBudget v1beta1 policy</A></LI>
<UL id="poddisruptionbudget-v1beta1-policy-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-poddisruptionbudget-v1beta1-policy-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-poddisruptionbudget-v1beta1-policy-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-poddisruptionbudget-v1beta1-policy" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-poddisruptionbudget-v1beta1-policy" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-poddisruptionbudget-v1beta1-policy" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-poddisruptionbudget-v1beta1-policy" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-poddisruptionbudget-v1beta1-policy" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-poddisruptionbudget-v1beta1-policy-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-poddisruptionbudget-v1beta1-policy-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-poddisruptionbudget-v1beta1-policy" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-poddisruptionbudget-v1beta1-policy" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-poddisruptionbudget-v1beta1-policy" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-poddisruptionbudget-v1beta1-policy" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-poddisruptionbudget-v1beta1-policy" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-poddisruptionbudget-v1beta1-policy" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-poddisruptionbudget-v1beta1-policy-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-poddisruptionbudget-v1beta1-policy-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-poddisruptionbudget-v1beta1-policy" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-poddisruptionbudget-v1beta1-policy" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-poddisruptionbudget-v1beta1-policy" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">PriorityClass v1beta1 scheduling.k8s.io</A></LI>
<UL id="priorityclass-v1beta1-scheduling-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-priorityclass-v1beta1-scheduling-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-priorityclass-v1beta1-scheduling-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-priorityclass-v1beta1-scheduling-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-priorityclass-v1beta1-scheduling-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-priorityclass-v1beta1-scheduling-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#podpreset-v1alpha1-settings-k8s-io" class="nav-item">PodPreset v1alpha1 settings.k8s.io</A></LI>
<UL id="podpreset-v1alpha1-settings-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-podpreset-v1alpha1-settings-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-podpreset-v1alpha1-settings-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-podpreset-v1alpha1-settings-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-podpreset-v1alpha1-settings-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-podpreset-v1alpha1-settings-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-podpreset-v1alpha1-settings-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-podpreset-v1alpha1-settings-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-podpreset-v1alpha1-settings-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-podpreset-v1alpha1-settings-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-podpreset-v1alpha1-settings-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-podpreset-v1alpha1-settings-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-podpreset-v1alpha1-settings-k8s-io" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-podpreset-v1alpha1-settings-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-podpreset-v1alpha1-settings-k8s-io" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-podpreset-v1alpha1-settings-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#podsecuritypolicy-v1beta1-extensions" class="nav-item">PodSecurityPolicy v1beta1 extensions</A></LI>
<UL id="podsecuritypolicy-v1beta1-extensions-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-podsecuritypolicy-v1beta1-extensions-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-podsecuritypolicy-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-podsecuritypolicy-v1beta1-extensions" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-podsecuritypolicy-v1beta1-extensions" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-podsecuritypolicy-v1beta1-extensions" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-podsecuritypolicy-v1beta1-extensions" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-podsecuritypolicy-v1beta1-extensions" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-podsecuritypolicy-v1beta1-extensions-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-podsecuritypolicy-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-podsecuritypolicy-v1beta1-extensions" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-podsecuritypolicy-v1beta1-extensions" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-podsecuritypolicy-v1beta1-extensions" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-podsecuritypolicy-v1beta1-extensions" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1 strong-nav"><A href="#-strong-cluster-apis-strong-" class="nav-item"><STRONG>CLUSTER APIS</STRONG></A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#apiservice-v1-apiregistration-k8s-io" class="nav-item">APIService v1 apiregistration.k8s.io</A></LI>
<UL id="apiservice-v1-apiregistration-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-apiservice-v1-apiregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-apiservice-v1-apiregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-apiservice-v1-apiregistration-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-apiservice-v1-apiregistration-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-apiservice-v1-apiregistration-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-apiservice-v1-apiregistration-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-apiservice-v1-apiregistration-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-apiservice-v1-apiregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-apiservice-v1-apiregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-apiservice-v1-apiregistration-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-apiservice-v1-apiregistration-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-apiservice-v1-apiregistration-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-apiservice-v1-apiregistration-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-apiservice-v1-apiregistration-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-apiservice-v1-apiregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-apiservice-v1-apiregistration-k8s-io" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-apiservice-v1-apiregistration-k8s-io" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-apiservice-v1-apiregistration-k8s-io" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#binding-v1-core" class="nav-item">Binding v1 core</A></LI>
<UL id="binding-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-binding-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-binding-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-binding-v1-core" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">CertificateSigningRequest v1beta1 certificates.k8s.io</A></LI>
<UL id="certificatesigningrequest-v1beta1-certificates-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-certificatesigningrequest-v1beta1-certificates-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-certificatesigningrequest-v1beta1-certificates-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-certificatesigningrequest-v1beta1-certificates-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-certificatesigningrequest-v1beta1-certificates-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-certificatesigningrequest-v1beta1-certificates-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-certificatesigningrequest-v1beta1-certificates-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-certificatesigningrequest-v1beta1-certificates-k8s-io" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">ClusterRole v1 rbac.authorization.k8s.io</A></LI>
<UL id="clusterrole-v1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-clusterrole-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-clusterrole-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-clusterrole-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">ClusterRoleBinding v1 rbac.authorization.k8s.io</A></LI>
<UL id="clusterrolebinding-v1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-clusterrolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#componentstatus-v1-core" class="nav-item">ComponentStatus v1 core</A></LI>
<UL id="componentstatus-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-componentstatus-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-componentstatus-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-componentstatus-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-componentstatus-v1-core" class="nav-item">List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#localsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">LocalSubjectAccessReview v1 authorization.k8s.io</A></LI>
<UL id="localsubjectaccessreview-v1-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-localsubjectaccessreview-v1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-localsubjectaccessreview-v1-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-localsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#namespace-v1-core" class="nav-item">Namespace v1 core</A></LI>
<UL id="namespace-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-namespace-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-namespace-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-namespace-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-namespace-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-namespace-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-namespace-v1-core" class="nav-item">Delete</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-namespace-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-namespace-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-namespace-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-namespace-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-namespace-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-namespace-v1-core" class="nav-item">Watch List</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-namespace-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-namespace-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-namespace-v1-core" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-namespace-v1-core" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-namespace-v1-core" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#node-v1-core" class="nav-item">Node v1 core</A></LI>
<UL id="node-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-node-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-node-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-node-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-node-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-node-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-node-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-node-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-node-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-node-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-node-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-node-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-node-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-node-v1-core" class="nav-item">Watch List</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-node-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-node-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-node-v1-core" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-node-v1-core" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-node-v1-core" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-proxy-operations-node-v1-core-strong-" class="nav-item"><STRONG>Proxy Operations</STRONG></A></LI>
<UL id="-strong-proxy-operations-node-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-connect-proxy-node-v1-core" class="nav-item">Create Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#create-connect-proxy-path-node-v1-core" class="nav-item">Create Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#delete-connect-proxy-node-v1-core" class="nav-item">Delete Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#delete-connect-proxy-path-node-v1-core" class="nav-item">Delete Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#get-connect-proxy-node-v1-core" class="nav-item">Get Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#get-connect-proxy-path-node-v1-core" class="nav-item">Get Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#head-connect-proxy-node-v1-core" class="nav-item">Head Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#head-connect-proxy-path-node-v1-core" class="nav-item">Head Connect Proxy Path</A></LI>
<LI class="nav-level-2"><A href="#replace-connect-proxy-node-v1-core" class="nav-item">Replace Connect Proxy</A></LI>
<LI class="nav-level-2"><A href="#replace-connect-proxy-path-node-v1-core" class="nav-item">Replace Connect Proxy Path</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#persistentvolume-v1-core" class="nav-item">PersistentVolume v1 core</A></LI>
<UL id="persistentvolume-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-persistentvolume-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-persistentvolume-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-persistentvolume-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-persistentvolume-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-persistentvolume-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-persistentvolume-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-persistentvolume-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-persistentvolume-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-persistentvolume-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-persistentvolume-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-persistentvolume-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-persistentvolume-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-persistentvolume-v1-core" class="nav-item">Watch List</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-persistentvolume-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-persistentvolume-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-persistentvolume-v1-core" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-persistentvolume-v1-core" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-persistentvolume-v1-core" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#resourcequota-v1-core" class="nav-item">ResourceQuota v1 core</A></LI>
<UL id="resourcequota-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-resourcequota-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-resourcequota-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-resourcequota-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-resourcequota-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-resourcequota-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-resourcequota-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-resourcequota-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-resourcequota-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-resourcequota-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-resourcequota-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-resourcequota-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-resourcequota-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-resourcequota-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-resourcequota-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-resourcequota-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-resourcequota-v1-core-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-resourcequota-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-resourcequota-v1-core" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-resourcequota-v1-core" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-resourcequota-v1-core" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#role-v1-rbac-authorization-k8s-io" class="nav-item">Role v1 rbac.authorization.k8s.io</A></LI>
<UL id="role-v1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-role-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-role-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-role-v1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-role-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-role-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-role-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-role-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-role-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-role-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-role-v1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-role-v1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-role-v1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-role-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-role-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-role-v1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">RoleBinding v1 rbac.authorization.k8s.io</A></LI>
<UL id="rolebinding-v1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-rolebinding-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-rolebinding-v1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#selfsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">SelfSubjectAccessReview v1 authorization.k8s.io</A></LI>
<UL id="selfsubjectaccessreview-v1-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-selfsubjectaccessreview-v1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-selfsubjectaccessreview-v1-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-selfsubjectaccessreview-v1-authorization-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#selfsubjectrulesreview-v1-authorization-k8s-io" class="nav-item">SelfSubjectRulesReview v1 authorization.k8s.io</A></LI>
<UL id="selfsubjectrulesreview-v1-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-selfsubjectrulesreview-v1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-selfsubjectrulesreview-v1-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-selfsubjectrulesreview-v1-authorization-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#serviceaccount-v1-core" class="nav-item">ServiceAccount v1 core</A></LI>
<UL id="serviceaccount-v1-core-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-serviceaccount-v1-core-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-serviceaccount-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-serviceaccount-v1-core" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-serviceaccount-v1-core" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-serviceaccount-v1-core" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-serviceaccount-v1-core" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-serviceaccount-v1-core" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-serviceaccount-v1-core-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-serviceaccount-v1-core-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-serviceaccount-v1-core" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-serviceaccount-v1-core" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-serviceaccount-v1-core" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-serviceaccount-v1-core" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-serviceaccount-v1-core" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-serviceaccount-v1-core" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#subjectaccessreview-v1-authorization-k8s-io" class="nav-item">SubjectAccessReview v1 authorization.k8s.io</A></LI>
<UL id="subjectaccessreview-v1-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-subjectaccessreview-v1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-subjectaccessreview-v1-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-subjectaccessreview-v1-authorization-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#tokenreview-v1-authentication-k8s-io" class="nav-item">TokenReview v1 authentication.k8s.io</A></LI>
<UL id="tokenreview-v1-authentication-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-tokenreview-v1-authentication-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-tokenreview-v1-authentication-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-tokenreview-v1-authentication-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#networkpolicy-v1-networking-k8s-io" class="nav-item">NetworkPolicy v1 networking.k8s.io</A></LI>
<UL id="networkpolicy-v1-networking-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-networkpolicy-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-networkpolicy-v1-networking-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-networkpolicy-v1-networking-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-networkpolicy-v1-networking-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-networkpolicy-v1-networking-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-networkpolicy-v1-networking-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-networkpolicy-v1-networking-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-networkpolicy-v1-networking-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-networkpolicy-v1-networking-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-networkpolicy-v1-networking-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-networkpolicy-v1-networking-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-networkpolicy-v1-networking-k8s-io" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-networkpolicy-v1-networking-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-networkpolicy-v1-networking-k8s-io" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-networkpolicy-v1-networking-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1 strong-nav"><A href="#-strong-definitions-strong-" class="nav-item"><STRONG>DEFINITIONS</STRONG></A></LI>
</UL>
<UL id="-strong-definitions-strong--nav" style="display: none;">
<UL>
<LI class="nav-level-2"><A href="#apigroup-v1-meta" class="nav-item">APIGroup v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#apiresource-v1-meta" class="nav-item">APIResource v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#apiservicecondition-v1-apiregistration-k8s-io" class="nav-item">APIServiceCondition v1 apiregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#apiversions-v1-meta" class="nav-item">APIVersions v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#awselasticblockstorevolumesource-v1-core" class="nav-item">AWSElasticBlockStoreVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#affinity-v1-core" class="nav-item">Affinity v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#aggregationrule-v1-rbac-authorization-k8s-io" class="nav-item">AggregationRule v1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#allowedflexvolume-v1beta1-extensions" class="nav-item">AllowedFlexVolume v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#allowedhostpath-v1beta1-extensions" class="nav-item">AllowedHostPath v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#attachedvolume-v1-core" class="nav-item">AttachedVolume v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#azurediskvolumesource-v1-core" class="nav-item">AzureDiskVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#azurefilepersistentvolumesource-v1-core" class="nav-item">AzureFilePersistentVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#azurefilevolumesource-v1-core" class="nav-item">AzureFileVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#csipersistentvolumesource-v1-core" class="nav-item">CSIPersistentVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#capabilities-v1-core" class="nav-item">Capabilities v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#cephfspersistentvolumesource-v1-core" class="nav-item">CephFSPersistentVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#cephfsvolumesource-v1-core" class="nav-item">CephFSVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#certificatesigningrequestcondition-v1beta1-certificates-k8s-io" class="nav-item">CertificateSigningRequestCondition v1beta1 certificates.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#cinderpersistentvolumesource-v1-core" class="nav-item">CinderPersistentVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#cindervolumesource-v1-core" class="nav-item">CinderVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#clientipconfig-v1-core" class="nav-item">ClientIPConfig v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#componentcondition-v1-core" class="nav-item">ComponentCondition v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#configmapenvsource-v1-core" class="nav-item">ConfigMapEnvSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#configmapkeyselector-v1-core" class="nav-item">ConfigMapKeySelector v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#configmapnodeconfigsource-v1-core" class="nav-item">ConfigMapNodeConfigSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#configmapprojection-v1-core" class="nav-item">ConfigMapProjection v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#configmapvolumesource-v1-core" class="nav-item">ConfigMapVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#containerimage-v1-core" class="nav-item">ContainerImage v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#containerport-v1-core" class="nav-item">ContainerPort v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#containerstate-v1-core" class="nav-item">ContainerState v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#containerstaterunning-v1-core" class="nav-item">ContainerStateRunning v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#containerstateterminated-v1-core" class="nav-item">ContainerStateTerminated v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#containerstatewaiting-v1-core" class="nav-item">ContainerStateWaiting v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#crossversionobjectreference-v1-autoscaling" class="nav-item">CrossVersionObjectReference v1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#customresourcecolumndefinition-v1beta1-apiextensions-k8s-io" class="nav-item">CustomResourceColumnDefinition v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#customresourcedefinitioncondition-v1beta1-apiextensions-k8s-io" class="nav-item">CustomResourceDefinitionCondition v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#customresourcedefinitionnames-v1beta1-apiextensions-k8s-io" class="nav-item">CustomResourceDefinitionNames v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#customresourcedefinitionversion-v1beta1-apiextensions-k8s-io" class="nav-item">CustomResourceDefinitionVersion v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#customresourcesubresourcescale-v1beta1-apiextensions-k8s-io" class="nav-item">CustomResourceSubresourceScale v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#customresourcesubresourcestatus-v1beta1-apiextensions-k8s-io" class="nav-item">CustomResourceSubresourceStatus v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#customresourcesubresources-v1beta1-apiextensions-k8s-io" class="nav-item">CustomResourceSubresources v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#customresourcevalidation-v1beta1-apiextensions-k8s-io" class="nav-item">CustomResourceValidation v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#daemonendpoint-v1-core" class="nav-item">DaemonEndpoint v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#daemonsetcondition-v1-apps" class="nav-item">DaemonSetCondition v1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#daemonsetupdatestrategy-v1-apps" class="nav-item">DaemonSetUpdateStrategy v1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#deleteoptions-v1-meta" class="nav-item">DeleteOptions v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#deploymentcondition-v1-apps" class="nav-item">DeploymentCondition v1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#downwardapiprojection-v1-core" class="nav-item">DownwardAPIProjection v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#downwardapivolumefile-v1-core" class="nav-item">DownwardAPIVolumeFile v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#downwardapivolumesource-v1-core" class="nav-item">DownwardAPIVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#emptydirvolumesource-v1-core" class="nav-item">EmptyDirVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#endpointaddress-v1-core" class="nav-item">EndpointAddress v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#endpointport-v1-core" class="nav-item">EndpointPort v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#endpointsubset-v1-core" class="nav-item">EndpointSubset v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#envfromsource-v1-core" class="nav-item">EnvFromSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#envvar-v1-core" class="nav-item">EnvVar v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#envvarsource-v1-core" class="nav-item">EnvVarSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#eventseries-v1-core" class="nav-item">EventSeries v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#eventsource-v1-core" class="nav-item">EventSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#eviction-v1beta1-policy" class="nav-item">Eviction v1beta1 policy</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#execaction-v1-core" class="nav-item">ExecAction v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#externaldocumentation-v1beta1-apiextensions-k8s-io" class="nav-item">ExternalDocumentation v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#externalmetricsource-v2beta1-autoscaling" class="nav-item">ExternalMetricSource v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#externalmetricstatus-v2beta1-autoscaling" class="nav-item">ExternalMetricStatus v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#fcvolumesource-v1-core" class="nav-item">FCVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#fsgroupstrategyoptions-v1beta1-extensions" class="nav-item">FSGroupStrategyOptions v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#flexpersistentvolumesource-v1-core" class="nav-item">FlexPersistentVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#flexvolumesource-v1-core" class="nav-item">FlexVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#flockervolumesource-v1-core" class="nav-item">FlockerVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#gcepersistentdiskvolumesource-v1-core" class="nav-item">GCEPersistentDiskVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#gitrepovolumesource-v1-core" class="nav-item">GitRepoVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#glusterfsvolumesource-v1-core" class="nav-item">GlusterfsVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#groupversionfordiscovery-v1-meta" class="nav-item">GroupVersionForDiscovery v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#httpgetaction-v1-core" class="nav-item">HTTPGetAction v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#httpheader-v1-core" class="nav-item">HTTPHeader v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#httpingresspath-v1beta1-extensions" class="nav-item">HTTPIngressPath v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#httpingressrulevalue-v1beta1-extensions" class="nav-item">HTTPIngressRuleValue v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#handler-v1-core" class="nav-item">Handler v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#horizontalpodautoscalercondition-v2beta1-autoscaling" class="nav-item">HorizontalPodAutoscalerCondition v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#hostalias-v1-core" class="nav-item">HostAlias v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#hostpathvolumesource-v1-core" class="nav-item">HostPathVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#hostportrange-v1beta1-extensions" class="nav-item">HostPortRange v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#idrange-v1beta1-extensions" class="nav-item">IDRange v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#ipblock-v1-networking-k8s-io" class="nav-item">IPBlock v1 networking.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#iscsipersistentvolumesource-v1-core" class="nav-item">ISCSIPersistentVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#iscsivolumesource-v1-core" class="nav-item">ISCSIVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#ingressbackend-v1beta1-extensions" class="nav-item">IngressBackend v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#ingressrule-v1beta1-extensions" class="nav-item">IngressRule v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#ingresstls-v1beta1-extensions" class="nav-item">IngressTLS v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#initializer-v1-meta" class="nav-item">Initializer v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#initializers-v1-meta" class="nav-item">Initializers v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#json-v1beta1-apiextensions-k8s-io" class="nav-item">JSON v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#jsonschemaprops-v1beta1-apiextensions-k8s-io" class="nav-item">JSONSchemaProps v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#jsonschemapropsorarray-v1beta1-apiextensions-k8s-io" class="nav-item">JSONSchemaPropsOrArray v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#jsonschemapropsorbool-v1beta1-apiextensions-k8s-io" class="nav-item">JSONSchemaPropsOrBool v1beta1 apiextensions.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#jobcondition-v1-batch" class="nav-item">JobCondition v1 batch</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#jobtemplatespec-v1beta1-batch" class="nav-item">JobTemplateSpec v1beta1 batch</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#keytopath-v1-core" class="nav-item">KeyToPath v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#labelselector-v1-meta" class="nav-item">LabelSelector v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#labelselectorrequirement-v1-meta" class="nav-item">LabelSelectorRequirement v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#lifecycle-v1-core" class="nav-item">Lifecycle v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#limitrangeitem-v1-core" class="nav-item">LimitRangeItem v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#listmeta-v1-meta" class="nav-item">ListMeta v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#loadbalanceringress-v1-core" class="nav-item">LoadBalancerIngress v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#loadbalancerstatus-v1-core" class="nav-item">LoadBalancerStatus v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#localobjectreference-v1-core" class="nav-item">LocalObjectReference v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#localvolumesource-v1-core" class="nav-item">LocalVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#metricspec-v2beta1-autoscaling" class="nav-item">MetricSpec v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#metricstatus-v2beta1-autoscaling" class="nav-item">MetricStatus v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#microtime-v1-meta" class="nav-item">MicroTime v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nfsvolumesource-v1-core" class="nav-item">NFSVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#networkpolicyegressrule-v1-networking-k8s-io" class="nav-item">NetworkPolicyEgressRule v1 networking.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#networkpolicyingressrule-v1-networking-k8s-io" class="nav-item">NetworkPolicyIngressRule v1 networking.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#networkpolicypeer-v1-networking-k8s-io" class="nav-item">NetworkPolicyPeer v1 networking.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#networkpolicyport-v1-networking-k8s-io" class="nav-item">NetworkPolicyPort v1 networking.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodeaddress-v1-core" class="nav-item">NodeAddress v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodeaffinity-v1-core" class="nav-item">NodeAffinity v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodecondition-v1-core" class="nav-item">NodeCondition v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodeconfigsource-v1-core" class="nav-item">NodeConfigSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodeconfigstatus-v1-core" class="nav-item">NodeConfigStatus v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodedaemonendpoints-v1-core" class="nav-item">NodeDaemonEndpoints v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodeselector-v1-core" class="nav-item">NodeSelector v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodeselectorrequirement-v1-core" class="nav-item">NodeSelectorRequirement v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodeselectorterm-v1-core" class="nav-item">NodeSelectorTerm v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nodesysteminfo-v1-core" class="nav-item">NodeSystemInfo v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nonresourceattributes-v1-authorization-k8s-io" class="nav-item">NonResourceAttributes v1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#nonresourcerule-v1-authorization-k8s-io" class="nav-item">NonResourceRule v1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#objectfieldselector-v1-core" class="nav-item">ObjectFieldSelector v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#objectmeta-v1-meta" class="nav-item">ObjectMeta v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#objectmetricsource-v2beta1-autoscaling" class="nav-item">ObjectMetricSource v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#objectmetricstatus-v2beta1-autoscaling" class="nav-item">ObjectMetricStatus v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#objectreference-v1-core" class="nav-item">ObjectReference v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#ownerreference-v1-meta" class="nav-item">OwnerReference v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#patch-v1-meta" class="nav-item">Patch v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#persistentvolumeclaimcondition-v1-core" class="nav-item">PersistentVolumeClaimCondition v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#persistentvolumeclaimvolumesource-v1-core" class="nav-item">PersistentVolumeClaimVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#photonpersistentdiskvolumesource-v1-core" class="nav-item">PhotonPersistentDiskVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#podaffinity-v1-core" class="nav-item">PodAffinity v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#podaffinityterm-v1-core" class="nav-item">PodAffinityTerm v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#podantiaffinity-v1-core" class="nav-item">PodAntiAffinity v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#podcondition-v1-core" class="nav-item">PodCondition v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#poddnsconfig-v1-core" class="nav-item">PodDNSConfig v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#poddnsconfigoption-v1-core" class="nav-item">PodDNSConfigOption v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#podreadinessgate-v1-core" class="nav-item">PodReadinessGate v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#podsecuritycontext-v1-core" class="nav-item">PodSecurityContext v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#podsmetricsource-v2beta1-autoscaling" class="nav-item">PodsMetricSource v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#podsmetricstatus-v2beta1-autoscaling" class="nav-item">PodsMetricStatus v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#policyrule-v1-rbac-authorization-k8s-io" class="nav-item">PolicyRule v1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#portworxvolumesource-v1-core" class="nav-item">PortworxVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#preconditions-v1-meta" class="nav-item">Preconditions v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#preferredschedulingterm-v1-core" class="nav-item">PreferredSchedulingTerm v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#probe-v1-core" class="nav-item">Probe v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#projectedvolumesource-v1-core" class="nav-item">ProjectedVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#quantity-resource-core" class="nav-item">Quantity resource core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#quobytevolumesource-v1-core" class="nav-item">QuobyteVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#rbdpersistentvolumesource-v1-core" class="nav-item">RBDPersistentVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#rbdvolumesource-v1-core" class="nav-item">RBDVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#replicasetcondition-v1-apps" class="nav-item">ReplicaSetCondition v1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#replicationcontrollercondition-v1-core" class="nav-item">ReplicationControllerCondition v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#resourceattributes-v1-authorization-k8s-io" class="nav-item">ResourceAttributes v1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#resourcefieldselector-v1-core" class="nav-item">ResourceFieldSelector v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#resourcemetricsource-v2beta1-autoscaling" class="nav-item">ResourceMetricSource v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#resourcemetricstatus-v2beta1-autoscaling" class="nav-item">ResourceMetricStatus v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#resourcerequirements-v1-core" class="nav-item">ResourceRequirements v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#resourcerule-v1-authorization-k8s-io" class="nav-item">ResourceRule v1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#roleref-v1-rbac-authorization-k8s-io" class="nav-item">RoleRef v1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#rollbackconfig-v1beta1-apps" class="nav-item">RollbackConfig v1beta1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#rollingupdatestatefulsetstrategy-v1-apps" class="nav-item">RollingUpdateStatefulSetStrategy v1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#rule-v1alpha1-admissionregistration-k8s-io" class="nav-item">Rule v1alpha1 admissionregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#rulewithoperations-v1beta1-admissionregistration-k8s-io" class="nav-item">RuleWithOperations v1beta1 admissionregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#runasuserstrategyoptions-v1beta1-extensions" class="nav-item">RunAsUserStrategyOptions v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#selinuxoptions-v1-core" class="nav-item">SELinuxOptions v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#selinuxstrategyoptions-v1beta1-extensions" class="nav-item">SELinuxStrategyOptions v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#scale-v1-autoscaling" class="nav-item">Scale v1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#scaleiopersistentvolumesource-v1-core" class="nav-item">ScaleIOPersistentVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#scaleiovolumesource-v1-core" class="nav-item">ScaleIOVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#scopeselector-v1-core" class="nav-item">ScopeSelector v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#scopedresourceselectorrequirement-v1-core" class="nav-item">ScopedResourceSelectorRequirement v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#secretenvsource-v1-core" class="nav-item">SecretEnvSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#secretkeyselector-v1-core" class="nav-item">SecretKeySelector v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#secretprojection-v1-core" class="nav-item">SecretProjection v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#secretreference-v1-core" class="nav-item">SecretReference v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#secretvolumesource-v1-core" class="nav-item">SecretVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#securitycontext-v1-core" class="nav-item">SecurityContext v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#serveraddressbyclientcidr-v1-meta" class="nav-item">ServerAddressByClientCIDR v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#serviceaccounttokenprojection-v1-core" class="nav-item">ServiceAccountTokenProjection v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#serviceport-v1-core" class="nav-item">ServicePort v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#servicereference-v1-apiregistration-k8s-io" class="nav-item">ServiceReference v1 apiregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#sessionaffinityconfig-v1-core" class="nav-item">SessionAffinityConfig v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#statefulsetcondition-v1-apps" class="nav-item">StatefulSetCondition v1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#statefulsetupdatestrategy-v1-apps" class="nav-item">StatefulSetUpdateStrategy v1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#status-v1-meta" class="nav-item">Status v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#statuscause-v1-meta" class="nav-item">StatusCause v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#statusdetails-v1-meta" class="nav-item">StatusDetails v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#storageospersistentvolumesource-v1-core" class="nav-item">StorageOSPersistentVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#storageosvolumesource-v1-core" class="nav-item">StorageOSVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#subject-v1-rbac-authorization-k8s-io" class="nav-item">Subject v1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#subjectrulesreviewstatus-v1-authorization-k8s-io" class="nav-item">SubjectRulesReviewStatus v1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#supplementalgroupsstrategyoptions-v1beta1-extensions" class="nav-item">SupplementalGroupsStrategyOptions v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#sysctl-v1-core" class="nav-item">Sysctl v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#tcpsocketaction-v1-core" class="nav-item">TCPSocketAction v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#taint-v1-core" class="nav-item">Taint v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#time-v1-meta" class="nav-item">Time v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#toleration-v1-core" class="nav-item">Toleration v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#topologyselectorlabelrequirement-v1-core" class="nav-item">TopologySelectorLabelRequirement v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#topologyselectorterm-v1-core" class="nav-item">TopologySelectorTerm v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#userinfo-v1-authentication-k8s-io" class="nav-item">UserInfo v1 authentication.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#volumeattachmentsource-v1beta1-storage-k8s-io" class="nav-item">VolumeAttachmentSource v1beta1 storage.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#volumedevice-v1-core" class="nav-item">VolumeDevice v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#volumeerror-v1beta1-storage-k8s-io" class="nav-item">VolumeError v1beta1 storage.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#volumemount-v1-core" class="nav-item">VolumeMount v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#volumenodeaffinity-v1-core" class="nav-item">VolumeNodeAffinity v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#volumeprojection-v1-core" class="nav-item">VolumeProjection v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#vspherevirtualdiskvolumesource-v1-core" class="nav-item">VsphereVirtualDiskVolumeSource v1 core</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#watchevent-v1-meta" class="nav-item">WatchEvent v1 meta</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#webhook-v1beta1-admissionregistration-k8s-io" class="nav-item">Webhook v1beta1 admissionregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#webhookclientconfig-v1beta1-admissionregistration-k8s-io" class="nav-item">WebhookClientConfig v1beta1 admissionregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-2"><A href="#weightedpodaffinityterm-v1-core" class="nav-item">WeightedPodAffinityTerm v1 core</A></LI>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1 strong-nav"><A href="#-strong-old-api-versions-strong-" class="nav-item"><STRONG>OLD API VERSIONS</STRONG></A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">APIService v1beta1 apiregistration.k8s.io</A></LI>
<UL id="apiservice-v1beta1-apiregistration-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-apiservice-v1beta1-apiregistration-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-apiservice-v1beta1-apiregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-apiservice-v1beta1-apiregistration-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-apiservice-v1beta1-apiregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-apiservice-v1beta1-apiregistration-k8s-io-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-apiservice-v1beta1-apiregistration-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-apiservice-v1beta1-apiregistration-k8s-io" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#apiservicecondition-v1beta1-apiregistration-k8s-io" class="nav-item">APIServiceCondition v1beta1 apiregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#aggregationrule-v1beta1-rbac-authorization-k8s-io" class="nav-item">AggregationRule v1beta1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#aggregationrule-v1alpha1-rbac-authorization-k8s-io" class="nav-item">AggregationRule v1alpha1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#allowedflexvolume-v1beta1-policy" class="nav-item">AllowedFlexVolume v1beta1 policy</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#allowedhostpath-v1beta1-policy" class="nav-item">AllowedHostPath v1beta1 policy</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">ClusterRole v1beta1 rbac.authorization.k8s.io</A></LI>
<UL id="clusterrole-v1beta1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clusterrole-v1beta1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-clusterrole-v1beta1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-clusterrole-v1beta1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-clusterrole-v1beta1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-clusterrole-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">ClusterRole v1alpha1 rbac.authorization.k8s.io</A></LI>
<UL id="clusterrole-v1alpha1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clusterrole-v1alpha1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-clusterrole-v1alpha1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-clusterrole-v1alpha1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-clusterrole-v1alpha1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-clusterrole-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">ClusterRoleBinding v1beta1 rbac.authorization.k8s.io</A></LI>
<UL id="clusterrolebinding-v1beta1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clusterrolebinding-v1beta1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-clusterrolebinding-v1beta1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-clusterrolebinding-v1beta1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-clusterrolebinding-v1beta1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-clusterrolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">ClusterRoleBinding v1alpha1 rbac.authorization.k8s.io</A></LI>
<UL id="clusterrolebinding-v1alpha1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#controllerrevision-v1beta2-apps" class="nav-item">ControllerRevision v1beta2 apps</A></LI>
<UL id="controllerrevision-v1beta2-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-controllerrevision-v1beta2-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-controllerrevision-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-controllerrevision-v1beta2-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-controllerrevision-v1beta2-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-controllerrevision-v1beta2-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-controllerrevision-v1beta2-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-controllerrevision-v1beta2-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-controllerrevision-v1beta2-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-controllerrevision-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-controllerrevision-v1beta2-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-controllerrevision-v1beta2-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-controllerrevision-v1beta2-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-controllerrevision-v1beta2-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-controllerrevision-v1beta2-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-controllerrevision-v1beta2-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#controllerrevision-v1beta1-apps" class="nav-item">ControllerRevision v1beta1 apps</A></LI>
<UL id="controllerrevision-v1beta1-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-controllerrevision-v1beta1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-controllerrevision-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-controllerrevision-v1beta1-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-controllerrevision-v1beta1-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-controllerrevision-v1beta1-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-controllerrevision-v1beta1-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-controllerrevision-v1beta1-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-controllerrevision-v1beta1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-controllerrevision-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-controllerrevision-v1beta1-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-controllerrevision-v1beta1-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-controllerrevision-v1beta1-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-controllerrevision-v1beta1-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-controllerrevision-v1beta1-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-controllerrevision-v1beta1-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#cronjob-v2alpha1-batch" class="nav-item">CronJob v2alpha1 batch</A></LI>
<UL id="cronjob-v2alpha1-batch-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-cronjob-v2alpha1-batch-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-cronjob-v2alpha1-batch-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-cronjob-v2alpha1-batch" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-cronjob-v2alpha1-batch" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-cronjob-v2alpha1-batch" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-cronjob-v2alpha1-batch" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-cronjob-v2alpha1-batch" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-cronjob-v2alpha1-batch-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-cronjob-v2alpha1-batch-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-cronjob-v2alpha1-batch" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-cronjob-v2alpha1-batch" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-cronjob-v2alpha1-batch" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-cronjob-v2alpha1-batch" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-cronjob-v2alpha1-batch" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-cronjob-v2alpha1-batch" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-cronjob-v2alpha1-batch-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-cronjob-v2alpha1-batch-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-cronjob-v2alpha1-batch" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-cronjob-v2alpha1-batch" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-cronjob-v2alpha1-batch" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#crossversionobjectreference-v2beta1-autoscaling" class="nav-item">CrossVersionObjectReference v2beta1 autoscaling</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#daemonset-v1beta2-apps" class="nav-item">DaemonSet v1beta2 apps</A></LI>
<UL id="daemonset-v1beta2-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-daemonset-v1beta2-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-daemonset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-daemonset-v1beta2-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-daemonset-v1beta2-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-daemonset-v1beta2-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-daemonset-v1beta2-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-daemonset-v1beta2-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-daemonset-v1beta2-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-daemonset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-daemonset-v1beta2-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-daemonset-v1beta2-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-daemonset-v1beta2-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-daemonset-v1beta2-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-daemonset-v1beta2-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-daemonset-v1beta2-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-daemonset-v1beta2-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-daemonset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-daemonset-v1beta2-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-daemonset-v1beta2-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-daemonset-v1beta2-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#daemonset-v1beta1-extensions" class="nav-item">DaemonSet v1beta1 extensions</A></LI>
<UL id="daemonset-v1beta1-extensions-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-daemonset-v1beta1-extensions-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-daemonset-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-daemonset-v1beta1-extensions" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-daemonset-v1beta1-extensions" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-daemonset-v1beta1-extensions" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-daemonset-v1beta1-extensions" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-daemonset-v1beta1-extensions" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-daemonset-v1beta1-extensions-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-daemonset-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-daemonset-v1beta1-extensions" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-daemonset-v1beta1-extensions" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-daemonset-v1beta1-extensions" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-daemonset-v1beta1-extensions" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-daemonset-v1beta1-extensions" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-daemonset-v1beta1-extensions" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-daemonset-v1beta1-extensions-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-daemonset-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-daemonset-v1beta1-extensions" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-daemonset-v1beta1-extensions" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-daemonset-v1beta1-extensions" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#daemonsetcondition-v1beta2-apps" class="nav-item">DaemonSetCondition v1beta2 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#daemonsetcondition-v1beta1-extensions" class="nav-item">DaemonSetCondition v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#daemonsetupdatestrategy-v1beta2-apps" class="nav-item">DaemonSetUpdateStrategy v1beta2 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#daemonsetupdatestrategy-v1beta1-extensions" class="nav-item">DaemonSetUpdateStrategy v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#deployment-v1beta2-apps" class="nav-item">Deployment v1beta2 apps</A></LI>
<UL id="deployment-v1beta2-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-deployment-v1beta2-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-deployment-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-deployment-v1beta2-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-deployment-v1beta2-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-deployment-v1beta2-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-deployment-v1beta2-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-deployment-v1beta2-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-deployment-v1beta2-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-deployment-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-deployment-v1beta2-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-deployment-v1beta2-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-deployment-v1beta2-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-deployment-v1beta2-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-deployment-v1beta2-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-deployment-v1beta2-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-deployment-v1beta2-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-deployment-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-deployment-v1beta2-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-deployment-v1beta2-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-deployment-v1beta2-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-deployment-v1beta2-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-deployment-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-deployment-v1beta2-apps" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-deployment-v1beta2-apps" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-deployment-v1beta2-apps" class="nav-item">Patch Scale</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#deployment-v1beta1-apps" class="nav-item">Deployment v1beta1 apps</A></LI>
<UL id="deployment-v1beta1-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-deployment-v1beta1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-deployment-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-deployment-v1beta1-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-deployment-v1beta1-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-deployment-v1beta1-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-deployment-v1beta1-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-deployment-v1beta1-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-deployment-v1beta1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-deployment-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-deployment-v1beta1-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-deployment-v1beta1-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-deployment-v1beta1-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-deployment-v1beta1-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-deployment-v1beta1-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-deployment-v1beta1-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-deployment-v1beta1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-deployment-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-deployment-v1beta1-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-deployment-v1beta1-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-deployment-v1beta1-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-deployment-v1beta1-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-deployment-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-deployment-v1beta1-apps" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-deployment-v1beta1-apps" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-deployment-v1beta1-apps" class="nav-item">Patch Scale</A></LI>
<LI class="nav-level-2"><A href="#rollback-deployment-v1beta1-apps" class="nav-item">Rollback</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#deployment-v1beta1-extensions" class="nav-item">Deployment v1beta1 extensions</A></LI>
<UL id="deployment-v1beta1-extensions-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-deployment-v1beta1-extensions-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-deployment-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-deployment-v1beta1-extensions" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-deployment-v1beta1-extensions" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-deployment-v1beta1-extensions" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-deployment-v1beta1-extensions" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-deployment-v1beta1-extensions" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-deployment-v1beta1-extensions-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-deployment-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-deployment-v1beta1-extensions" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-deployment-v1beta1-extensions" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-deployment-v1beta1-extensions" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-deployment-v1beta1-extensions" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-deployment-v1beta1-extensions" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-deployment-v1beta1-extensions" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-deployment-v1beta1-extensions-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-deployment-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-deployment-v1beta1-extensions" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-deployment-v1beta1-extensions" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-deployment-v1beta1-extensions" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-deployment-v1beta1-extensions-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-deployment-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-deployment-v1beta1-extensions" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-deployment-v1beta1-extensions" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-deployment-v1beta1-extensions" class="nav-item">Patch Scale</A></LI>
<LI class="nav-level-2"><A href="#rollback-deployment-v1beta1-extensions" class="nav-item">Rollback</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#deploymentcondition-v1beta2-apps" class="nav-item">DeploymentCondition v1beta2 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#deploymentcondition-v1beta1-apps" class="nav-item">DeploymentCondition v1beta1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#deploymentcondition-v1beta1-extensions" class="nav-item">DeploymentCondition v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#event-v1beta1-events-k8s-io" class="nav-item">Event v1beta1 events.k8s.io</A></LI>
<UL id="event-v1beta1-events-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-event-v1beta1-events-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-event-v1beta1-events-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-event-v1beta1-events-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-event-v1beta1-events-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-event-v1beta1-events-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-event-v1beta1-events-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-event-v1beta1-events-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-event-v1beta1-events-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-event-v1beta1-events-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-event-v1beta1-events-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-event-v1beta1-events-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-event-v1beta1-events-k8s-io" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-event-v1beta1-events-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-event-v1beta1-events-k8s-io" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-event-v1beta1-events-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#eventseries-v1beta1-events-k8s-io" class="nav-item">EventSeries v1beta1 events.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#fsgroupstrategyoptions-v1beta1-policy" class="nav-item">FSGroupStrategyOptions v1beta1 policy</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">HorizontalPodAutoscaler v2beta1 autoscaling</A></LI>
<UL id="horizontalpodautoscaler-v2beta1-autoscaling-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-horizontalpodautoscaler-v2beta1-autoscaling" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#hostportrange-v1beta1-policy" class="nav-item">HostPortRange v1beta1 policy</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#idrange-v1beta1-policy" class="nav-item">IDRange v1beta1 policy</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#ipblock-v1beta1-extensions" class="nav-item">IPBlock v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#initializer-v1alpha1-admissionregistration-k8s-io" class="nav-item">Initializer v1alpha1 admissionregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#jobtemplatespec-v2alpha1-batch" class="nav-item">JobTemplateSpec v2alpha1 batch</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#localsubjectaccessreview-v1beta1-authorization-k8s-io" class="nav-item">LocalSubjectAccessReview v1beta1 authorization.k8s.io</A></LI>
<UL id="localsubjectaccessreview-v1beta1-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-localsubjectaccessreview-v1beta1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-localsubjectaccessreview-v1beta1-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-localsubjectaccessreview-v1beta1-authorization-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#networkpolicy-v1beta1-extensions" class="nav-item">NetworkPolicy v1beta1 extensions</A></LI>
<UL id="networkpolicy-v1beta1-extensions-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-networkpolicy-v1beta1-extensions-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-networkpolicy-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-networkpolicy-v1beta1-extensions" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-networkpolicy-v1beta1-extensions" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-networkpolicy-v1beta1-extensions" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-networkpolicy-v1beta1-extensions" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-networkpolicy-v1beta1-extensions" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-networkpolicy-v1beta1-extensions-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-networkpolicy-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-networkpolicy-v1beta1-extensions" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-networkpolicy-v1beta1-extensions" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-networkpolicy-v1beta1-extensions" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-networkpolicy-v1beta1-extensions" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-networkpolicy-v1beta1-extensions" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-networkpolicy-v1beta1-extensions" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#networkpolicyegressrule-v1beta1-extensions" class="nav-item">NetworkPolicyEgressRule v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#networkpolicyingressrule-v1beta1-extensions" class="nav-item">NetworkPolicyIngressRule v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#networkpolicypeer-v1beta1-extensions" class="nav-item">NetworkPolicyPeer v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#networkpolicyport-v1beta1-extensions" class="nav-item">NetworkPolicyPort v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#nonresourceattributes-v1beta1-authorization-k8s-io" class="nav-item">NonResourceAttributes v1beta1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#nonresourcerule-v1beta1-authorization-k8s-io" class="nav-item">NonResourceRule v1beta1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#podsecuritypolicy-v1beta1-policy" class="nav-item">PodSecurityPolicy v1beta1 policy</A></LI>
<UL id="podsecuritypolicy-v1beta1-policy-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-podsecuritypolicy-v1beta1-policy-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-podsecuritypolicy-v1beta1-policy-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-podsecuritypolicy-v1beta1-policy" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-podsecuritypolicy-v1beta1-policy" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-podsecuritypolicy-v1beta1-policy" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-podsecuritypolicy-v1beta1-policy" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-podsecuritypolicy-v1beta1-policy" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-podsecuritypolicy-v1beta1-policy-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-podsecuritypolicy-v1beta1-policy-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-podsecuritypolicy-v1beta1-policy" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-podsecuritypolicy-v1beta1-policy" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-podsecuritypolicy-v1beta1-policy" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-podsecuritypolicy-v1beta1-policy" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#policyrule-v1beta1-rbac-authorization-k8s-io" class="nav-item">PolicyRule v1beta1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#policyrule-v1alpha1-rbac-authorization-k8s-io" class="nav-item">PolicyRule v1alpha1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">PriorityClass v1alpha1 scheduling.k8s.io</A></LI>
<UL id="priorityclass-v1alpha1-scheduling-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-priorityclass-v1alpha1-scheduling-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-priorityclass-v1alpha1-scheduling-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-priorityclass-v1alpha1-scheduling-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-priorityclass-v1alpha1-scheduling-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-priorityclass-v1alpha1-scheduling-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#replicaset-v1beta2-apps" class="nav-item">ReplicaSet v1beta2 apps</A></LI>
<UL id="replicaset-v1beta2-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-replicaset-v1beta2-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-replicaset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-replicaset-v1beta2-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-replicaset-v1beta2-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-replicaset-v1beta2-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-replicaset-v1beta2-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-replicaset-v1beta2-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-replicaset-v1beta2-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-replicaset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-replicaset-v1beta2-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-replicaset-v1beta2-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-replicaset-v1beta2-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-replicaset-v1beta2-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-replicaset-v1beta2-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-replicaset-v1beta2-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-replicaset-v1beta2-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-replicaset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-replicaset-v1beta2-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-replicaset-v1beta2-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-replicaset-v1beta2-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-replicaset-v1beta2-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-replicaset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-replicaset-v1beta2-apps" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-replicaset-v1beta2-apps" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-replicaset-v1beta2-apps" class="nav-item">Patch Scale</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#replicaset-v1beta1-extensions" class="nav-item">ReplicaSet v1beta1 extensions</A></LI>
<UL id="replicaset-v1beta1-extensions-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-replicaset-v1beta1-extensions-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-replicaset-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-replicaset-v1beta1-extensions" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-replicaset-v1beta1-extensions" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-replicaset-v1beta1-extensions" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-replicaset-v1beta1-extensions" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-replicaset-v1beta1-extensions" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-replicaset-v1beta1-extensions-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-replicaset-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-replicaset-v1beta1-extensions" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-replicaset-v1beta1-extensions" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-replicaset-v1beta1-extensions" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-replicaset-v1beta1-extensions" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-replicaset-v1beta1-extensions" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-replicaset-v1beta1-extensions" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-replicaset-v1beta1-extensions-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-replicaset-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-replicaset-v1beta1-extensions" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-replicaset-v1beta1-extensions" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-replicaset-v1beta1-extensions" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-replicaset-v1beta1-extensions-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-replicaset-v1beta1-extensions-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-replicaset-v1beta1-extensions" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-replicaset-v1beta1-extensions" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-replicaset-v1beta1-extensions" class="nav-item">Patch Scale</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#replicasetcondition-v1beta2-apps" class="nav-item">ReplicaSetCondition v1beta2 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#replicasetcondition-v1beta1-extensions" class="nav-item">ReplicaSetCondition v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#resourceattributes-v1beta1-authorization-k8s-io" class="nav-item">ResourceAttributes v1beta1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#resourcerule-v1beta1-authorization-k8s-io" class="nav-item">ResourceRule v1beta1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Role v1beta1 rbac.authorization.k8s.io</A></LI>
<UL id="role-v1beta1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-role-v1beta1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-role-v1beta1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-role-v1beta1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-role-v1beta1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-role-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Role v1alpha1 rbac.authorization.k8s.io</A></LI>
<UL id="role-v1alpha1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-role-v1alpha1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-role-v1alpha1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-role-v1alpha1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-role-v1alpha1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-role-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">RoleBinding v1beta1 rbac.authorization.k8s.io</A></LI>
<UL id="rolebinding-v1beta1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-rolebinding-v1beta1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-rolebinding-v1beta1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-rolebinding-v1beta1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-rolebinding-v1beta1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-rolebinding-v1beta1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">RoleBinding v1alpha1 rbac.authorization.k8s.io</A></LI>
<UL id="rolebinding-v1alpha1-rbac-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-rolebinding-v1alpha1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-rolebinding-v1alpha1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-rolebinding-v1alpha1-rbac-authorization-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-rolebinding-v1alpha1-rbac-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-rolebinding-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#roleref-v1beta1-rbac-authorization-k8s-io" class="nav-item">RoleRef v1beta1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#roleref-v1alpha1-rbac-authorization-k8s-io" class="nav-item">RoleRef v1alpha1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#rollbackconfig-v1beta1-extensions" class="nav-item">RollbackConfig v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#rollingupdatestatefulsetstrategy-v1beta2-apps" class="nav-item">RollingUpdateStatefulSetStrategy v1beta2 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#rollingupdatestatefulsetstrategy-v1beta1-apps" class="nav-item">RollingUpdateStatefulSetStrategy v1beta1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#runasuserstrategyoptions-v1beta1-policy" class="nav-item">RunAsUserStrategyOptions v1beta1 policy</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#selinuxstrategyoptions-v1beta1-policy" class="nav-item">SELinuxStrategyOptions v1beta1 policy</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#scale-v1beta2-apps" class="nav-item">Scale v1beta2 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#scale-v1beta1-apps" class="nav-item">Scale v1beta1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#scale-v1beta1-extensions" class="nav-item">Scale v1beta1 extensions</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#selfsubjectaccessreview-v1beta1-authorization-k8s-io" class="nav-item">SelfSubjectAccessReview v1beta1 authorization.k8s.io</A></LI>
<UL id="selfsubjectaccessreview-v1beta1-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-selfsubjectaccessreview-v1beta1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-selfsubjectaccessreview-v1beta1-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-selfsubjectaccessreview-v1beta1-authorization-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#selfsubjectrulesreview-v1beta1-authorization-k8s-io" class="nav-item">SelfSubjectRulesReview v1beta1 authorization.k8s.io</A></LI>
<UL id="selfsubjectrulesreview-v1beta1-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-selfsubjectrulesreview-v1beta1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-selfsubjectrulesreview-v1beta1-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-selfsubjectrulesreview-v1beta1-authorization-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#servicereference-v1beta1-admissionregistration-k8s-io" class="nav-item">ServiceReference v1beta1 admissionregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#servicereference-v1beta1-apiregistration-k8s-io" class="nav-item">ServiceReference v1beta1 apiregistration.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#statefulset-v1beta2-apps" class="nav-item">StatefulSet v1beta2 apps</A></LI>
<UL id="statefulset-v1beta2-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-statefulset-v1beta2-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-statefulset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-statefulset-v1beta2-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-statefulset-v1beta2-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-statefulset-v1beta2-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-statefulset-v1beta2-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-statefulset-v1beta2-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-statefulset-v1beta2-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-statefulset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-statefulset-v1beta2-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-statefulset-v1beta2-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-statefulset-v1beta2-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-statefulset-v1beta2-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-statefulset-v1beta2-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-statefulset-v1beta2-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-statefulset-v1beta2-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-statefulset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-statefulset-v1beta2-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-statefulset-v1beta2-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-statefulset-v1beta2-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-statefulset-v1beta2-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-statefulset-v1beta2-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-statefulset-v1beta2-apps" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-statefulset-v1beta2-apps" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-statefulset-v1beta2-apps" class="nav-item">Patch Scale</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#statefulset-v1beta1-apps" class="nav-item">StatefulSet v1beta1 apps</A></LI>
<UL id="statefulset-v1beta1-apps-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-statefulset-v1beta1-apps-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-statefulset-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-statefulset-v1beta1-apps" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-statefulset-v1beta1-apps" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-statefulset-v1beta1-apps" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-statefulset-v1beta1-apps" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-statefulset-v1beta1-apps" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-statefulset-v1beta1-apps-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-statefulset-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-statefulset-v1beta1-apps" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-statefulset-v1beta1-apps" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#list-all-namespaces-statefulset-v1beta1-apps" class="nav-item">List All Namespaces</A></LI>
<LI class="nav-level-2"><A href="#watch-statefulset-v1beta1-apps" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-statefulset-v1beta1-apps" class="nav-item">Watch List</A></LI>
<LI class="nav-level-2"><A href="#watch-list-all-namespaces-statefulset-v1beta1-apps" class="nav-item">Watch List All Namespaces</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-status-operations-statefulset-v1beta1-apps-strong-" class="nav-item"><STRONG>Status Operations</STRONG></A></LI>
<UL id="-strong-status-operations-statefulset-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#patch-status-statefulset-v1beta1-apps" class="nav-item">Patch Status</A></LI>
<LI class="nav-level-2"><A href="#read-status-statefulset-v1beta1-apps" class="nav-item">Read Status</A></LI>
<LI class="nav-level-2"><A href="#replace-status-statefulset-v1beta1-apps" class="nav-item">Replace Status</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-misc-operations-statefulset-v1beta1-apps-strong-" class="nav-item"><STRONG>Misc Operations</STRONG></A></LI>
<UL id="-strong-misc-operations-statefulset-v1beta1-apps-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-scale-statefulset-v1beta1-apps" class="nav-item">Read Scale</A></LI>
<LI class="nav-level-2"><A href="#replace-scale-statefulset-v1beta1-apps" class="nav-item">Replace Scale</A></LI>
<LI class="nav-level-2"><A href="#patch-scale-statefulset-v1beta1-apps" class="nav-item">Patch Scale</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#statefulsetcondition-v1beta2-apps" class="nav-item">StatefulSetCondition v1beta2 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#statefulsetcondition-v1beta1-apps" class="nav-item">StatefulSetCondition v1beta1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#statefulsetupdatestrategy-v1beta2-apps" class="nav-item">StatefulSetUpdateStrategy v1beta2 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#statefulsetupdatestrategy-v1beta1-apps" class="nav-item">StatefulSetUpdateStrategy v1beta1 apps</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#storageclass-v1beta1-storage-k8s-io" class="nav-item">StorageClass v1beta1 storage.k8s.io</A></LI>
<UL id="storageclass-v1beta1-storage-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-storageclass-v1beta1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-storageclass-v1beta1-storage-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-storageclass-v1beta1-storage-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-storageclass-v1beta1-storage-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-storageclass-v1beta1-storage-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-storageclass-v1beta1-storage-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-storageclass-v1beta1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-storageclass-v1beta1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-storageclass-v1beta1-storage-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-storageclass-v1beta1-storage-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-storageclass-v1beta1-storage-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-storageclass-v1beta1-storage-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-storageclass-v1beta1-storage-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#subject-v1beta1-rbac-authorization-k8s-io" class="nav-item">Subject v1beta1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#subject-v1alpha1-rbac-authorization-k8s-io" class="nav-item">Subject v1alpha1 rbac.authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#subjectaccessreview-v1beta1-authorization-k8s-io" class="nav-item">SubjectAccessReview v1beta1 authorization.k8s.io</A></LI>
<UL id="subjectaccessreview-v1beta1-authorization-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-subjectaccessreview-v1beta1-authorization-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-subjectaccessreview-v1beta1-authorization-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-subjectaccessreview-v1beta1-authorization-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#subjectrulesreviewstatus-v1beta1-authorization-k8s-io" class="nav-item">SubjectRulesReviewStatus v1beta1 authorization.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#supplementalgroupsstrategyoptions-v1beta1-policy" class="nav-item">SupplementalGroupsStrategyOptions v1beta1 policy</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#tokenreview-v1beta1-authentication-k8s-io" class="nav-item">TokenReview v1beta1 authentication.k8s.io</A></LI>
<UL id="tokenreview-v1beta1-authentication-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-tokenreview-v1beta1-authentication-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-tokenreview-v1beta1-authentication-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-tokenreview-v1beta1-authentication-k8s-io" class="nav-item">Create</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#userinfo-v1beta1-authentication-k8s-io" class="nav-item">UserInfo v1beta1 authentication.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">VolumeAttachment v1alpha1 storage.k8s.io</A></LI>
<UL id="volumeattachment-v1alpha1-storage-k8s-io-nav" style="display: none;">
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-write-operations-volumeattachment-v1alpha1-storage-k8s-io-strong-" class="nav-item"><STRONG>Write Operations</STRONG></A></LI>
<UL id="-strong-write-operations-volumeattachment-v1alpha1-storage-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#create-volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">Create</A></LI>
<LI class="nav-level-2"><A href="#patch-volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">Patch</A></LI>
<LI class="nav-level-2"><A href="#replace-volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">Replace</A></LI>
<LI class="nav-level-2"><A href="#delete-volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">Delete</A></LI>
<LI class="nav-level-2"><A href="#delete-collection-volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">Delete Collection</A></LI>
</UL>
</UL>
<UL>
<LI class="nav-level-2 strong-nav"><A href="#-strong-read-operations-volumeattachment-v1alpha1-storage-k8s-io-strong-" class="nav-item"><STRONG>Read Operations</STRONG></A></LI>
<UL id="-strong-read-operations-volumeattachment-v1alpha1-storage-k8s-io-strong--nav" style="display: none;">
<LI class="nav-level-2"><A href="#read-volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">Read</A></LI>
<LI class="nav-level-2"><A href="#list-volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">List</A></LI>
<LI class="nav-level-2"><A href="#watch-volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">Watch</A></LI>
<LI class="nav-level-2"><A href="#watch-list-volumeattachment-v1alpha1-storage-k8s-io" class="nav-item">Watch List</A></LI>
</UL>
</UL>
</UL>
</UL>
<UL>
<LI class="nav-level-1"><A href="#volumeattachmentsource-v1alpha1-storage-k8s-io" class="nav-item">VolumeAttachmentSource v1alpha1 storage.k8s.io</A></LI>
</UL>
<UL>
<LI class="nav-level-1"><A href="#volumeerror-v1alpha1-storage-k8s-io" class="nav-item">VolumeError v1alpha1 storage.k8s.io</A></LI>
</UL>
<BR/><DIV class="copyright"><a href="https://github.com/kubernetes/kubernetes">Copyright 2016 The Kubernetes Authors.</a></DIV></DIV>
<DIV id="wrapper">
<DIV id="page-content-wrapper" class="body-content container-fluid">
<H1 id="-strong-api-overview-strong-"><STRONG>API OVERVIEW</STRONG></H1>
<P>Welcome to the Kubernetes API. You can use the Kubernetes API to read
and write Kubernetes resource objects via a Kubernetes API endpoint.</P>
<H2 id="resource-categories">Resource Categories</H2>
<P>This is a high-level overview of the basic types of resources provide by the Kubernetes API and their primary functions.</P>
<P><B>Workloads</B> are objects you use to manage and run your containers on the cluster.</P>
<P><B>Discovery &amp; LB</B> resources are objects you use to "stitch" your workloads together into an externally accessible, load-balanced Service.</P>
<P><B>Config &amp; Storage</B> resources are objects you use to inject initialization data into your applications, and to persist data that is external to your container.</P>
<P><B>Cluster</B> resources objects define how the cluster itself is configured; these are typically used only by cluster operators.</P>
<P><B>Metadata</B> resources are objects you use to configure the behavior of other resources within the cluster, such as <code>HorizontalPodAutoscaler</code> for scaling workloads.</P>
<HR />
<H2 id="resource-objects">Resource Objects</H2>
<P>Resource objects typically have 3 components:</P>
<UL>
<LI><B>Resource ObjectMeta</B>: This is metadata about the resource, such as its name, type, api version, annotations, and labels. This contains
fields that maybe updated both by the end user and the system (e.g. annotations).</LI>
<LI><B>ResourceSpec</B>: This is defined by the user and describes the desired state of system. Fill this in when creating or updating an object.</LI>
<LI><B>ResourceStatus</B>: This is filled in by the server and reports the current state of the system. In most cases, users don't need to change this.</LI>
</UL>
<HR />
<H2 id="resource-operations">Resource Operations</H2>
<P>Most resources provide the following Operations:</P>
<H4 id="resource-operations-create">Create</H4>
<P>Create operations will create the resource in the storage backend. After a resource is create the system will apply
the desired state.</P>
<H4 id="resource-operations-update">Update</H4>
<P>Updates come in 2 forms: <B>Replace</B> and <B>Patch</B>:
<UL>
<LI><B>Replace</B>:
Replacing a resource object will update the resource by replacing the existing spec with the provided one. For
read-then-write operations this is safe because an optimistic lock failure will occur if the resource was modified
between the read and write. <I>Note</I>: The <I>ResourceStatus</I> will be ignored by the system and will not be updated.
To update the status, one must invoke the specific status update operation.<BR />
Note: Replacing a resource object may not result immediately in changes being propagated to downstream objects. For instance
replacing a <CODE>ConfigMap</CODE> or <CODE>Secret</CODE> resource will not result in all <I>Pod</I>s seeing the changes unless the <I>Pod</I>s are
restarted out of band.</P></LI>
<LI><B>Patch</B>:
Patch will apply a change to a specific field. How the change is merged is defined per field. Lists may either be
replaced or merged. Merging lists will not preserve ordering.<BR />
<B>Patches will never cause optimistic locking failures, and the last write will win.</B> Patches are recommended
when the full state is not read before an update, or when failing on optimistic locking is undesirable. <I>When patching
complex types, arrays and maps, how the patch is applied is defined on a per-field basis and may either replace
the field's current value, or merge the contents into the current value.</I></LI>
</UL>
<H4 id="resource-operations-read">Read</H4>
<P>Reads come in 3 forms: <B>Get</B>, <B>List</B> and <B>Watch</B>:<P>
<UL>
<LI><B>Get</B>: Get will retrieve a specific resource object by name.</LI>
<LI><B>List</B>: List will retrieve all resource objects of a specific type within a namespace, and the results can be restricted to resources matching a selector query.<BR />
<B>List All Namespaces</B>: Like <B>List</B> but retrieves resources across all namespaces.</LI>
<LI><B>Watch</B>: Watch will stream results for an object(s) as it is updated. Similar to a callback, watch is used to respond to resource changes.</LI>
</UL>
<H4 id="resource-operations-read">Delete</H4>
<P>Delete will delete a resource. Depending on the specific resource, child objects may or may not be garbage collected by the server. See
notes on specific resource objects for details.</P>
<H4 id="resource-operations-additional">Additional Operations</H4>
<P>Resources may define additional operations specific to that resource type.</P>
<UL>
<LI><B>Rollback</B>: Rollback a PodTemplate to a previous version. Only available for some resource types.</LI>
<LI><B>Read / Write Scale</B>: Read or Update the number of replicas for the given resource. Only available for some resource types.</LI>
<LI><B>Read / Write Status</B>: Read or Update the Status for a resource object. The Status can only changed through these update operations.</LI>
</UL>
<HR />
<H1 id="-strong-workloads-apis-strong-"><STRONG>Workloads APIs</STRONG></H1>
<H1 id="container-v1-core">Container v1 core</H1>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#kubectl-container-v1-core" aria-controls="kubectl-container-v1-core"
aria-expanded="false">kubectl example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#curl-container-v1-core" aria-controls="curl-container-v1-core"
aria-expanded="false">curl example</BUTTON>
<DIV class="collapse" id="kubectl-container-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Container Config to run nginx (must be embedded in a PodSpec to run).</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-yaml">
name: nginx
# Run the nginx:1.10 image
image: nginx:1.10
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="curl-container-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Container Config to run nginx (must be embedded in a PodSpec to run).</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-yaml">
name: nginx
# Run the nginx:1.10 image
image: nginx:1.10
</CODE></PRE></DIV></DIV></DIV>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Container</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-warning col-md-8"><P><I class="fa fa-warning"></I> <B>Warning:</B></P><P>Containers are only ever created within the context of a <a href="#pod-v1-core">Pod</a>. This is usually done using a Controller. See Controllers: <a href="#deployment-v1beta1-apps">Deployment</a>, <a href="#job-v1-batch">Job</a>, or <a href="#statefulset-v1beta1-apps">StatefulSet</a></P></DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>args</CODE><BR /><I>string array</I></TD><TD>Arguments to the entrypoint. The docker image&#39;s CMD is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell</TD></TR>
<TR><TD><CODE>command</CODE><BR /><I>string array</I></TD><TD>Entrypoint array. Not executed within a shell. The docker image&#39;s ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container&#39;s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Cannot be updated. More info: https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell</TD></TR>
<TR><TD><CODE>env</CODE><BR /><I><a href="#envvar-v1-core">EnvVar</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of environment variables to set in the container. Cannot be updated.</TD></TR>
<TR><TD><CODE>envFrom</CODE><BR /><I><a href="#envfromsource-v1-core">EnvFromSource</a> array</I></TD><TD>List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.</TD></TR>
<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>Docker image name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.</TD></TR>
<TR><TD><CODE>imagePullPolicy</CODE><BR /><I>string</I></TD><TD>Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images</TD></TR>
<TR><TD><CODE>lifecycle</CODE><BR /><I><a href="#lifecycle-v1-core">Lifecycle</a></I></TD><TD>Actions that the management system should take in response to container lifecycle events. Cannot be updated.</TD></TR>
<TR><TD><CODE>livenessProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Periodic probe of container liveness. Container will be restarted if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the container specified as a DNS_LABEL. Each container in a pod must have a unique name (DNS_LABEL). Cannot be updated.</TD></TR>
<TR><TD><CODE>ports</CODE><BR /><I><a href="#containerport-v1-core">ContainerPort</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>containerPort</I></TD><TD>List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default &#34;0.0.0.0&#34; address inside a container will be accessible from the network. Cannot be updated.</TD></TR>
<TR><TD><CODE>readinessProbe</CODE><BR /><I><a href="#probe-v1-core">Probe</a></I></TD><TD>Periodic probe of container service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcerequirements-v1-core">ResourceRequirements</a></I></TD><TD>Compute Resources required by this container. Cannot be updated. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources</TD></TR>
<TR><TD><CODE>securityContext</CODE><BR /><I><a href="#securitycontext-v1-core">SecurityContext</a></I></TD><TD>Security options the pod should run with. More info: https://kubernetes.io/docs/concepts/policy/security-context/ More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/</TD></TR>
<TR><TD><CODE>stdin</CODE><BR /><I>boolean</I></TD><TD>Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.</TD></TR>
<TR><TD><CODE>stdinOnce</CODE><BR /><I>boolean</I></TD><TD>Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, at which time stdin is closed and remains closed until the container is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false</TD></TR>
<TR><TD><CODE>terminationMessagePath</CODE><BR /><I>string</I></TD><TD>Optional: Path at which the file to which the container&#39;s termination message will be written is mounted into the container&#39;s filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. Defaults to /dev/termination-log. Cannot be updated.</TD></TR>
<TR><TD><CODE>terminationMessagePolicy</CODE><BR /><I>string</I></TD><TD>Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.</TD></TR>
<TR><TD><CODE>tty</CODE><BR /><I>boolean</I></TD><TD>Whether this container should allocate a TTY for itself, also requires &#39;stdin&#39; to be true. Default is false.</TD></TR>
<TR><TD><CODE>volumeDevices</CODE><BR /><I><a href="#volumedevice-v1-core">VolumeDevice</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>devicePath</I></TD><TD>volumeDevices is the list of block devices to be used by the container. This is an alpha feature and may change in the future.</TD></TR>
<TR><TD><CODE>volumeMounts</CODE><BR /><I><a href="#volumemount-v1-core">VolumeMount</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>mountPath</I></TD><TD>Pod volumes to mount into the container&#39;s filesystem. Cannot be updated.</TD></TR>
<TR><TD><CODE>workingDir</CODE><BR /><I>string</I></TD><TD>Container&#39;s working directory. If not specified, the container runtime&#39;s default will be used, which might be configured in the container image. Cannot be updated.</TD></TR>
</TBODY>
</TABLE>
<H3 id="containerstatus-v1-core">ContainerStatus v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podstatus-v1-core">PodStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>containerID</CODE><BR /><I>string</I></TD><TD>Container&#39;s ID in the format &#39;docker://&lt;container_id&gt;&#39;.</TD></TR>
<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>The image the container is running. More info: https://kubernetes.io/docs/concepts/containers/images</TD></TR>
<TR><TD><CODE>imageID</CODE><BR /><I>string</I></TD><TD>ImageID of the container&#39;s image.</TD></TR>
<TR><TD><CODE>lastState</CODE><BR /><I><a href="#containerstate-v1-core">ContainerState</a></I></TD><TD>Details about the container&#39;s last termination condition.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>This must be a DNS_LABEL. Each container in a pod must have a unique name. Cannot be updated.</TD></TR>
<TR><TD><CODE>ready</CODE><BR /><I>boolean</I></TD><TD>Specifies whether the container has passed its readiness probe.</TD></TR>
<TR><TD><CODE>restartCount</CODE><BR /><I>integer</I></TD><TD>The number of times the container has been restarted, currently based on the number of dead containers that have not yet been removed. Note that this is calculated from dead containers. But those containers are subject to garbage collection. This value will get capped at 5 by GC.</TD></TR>
<TR><TD><CODE>state</CODE><BR /><I><a href="#containerstate-v1-core">ContainerState</a></I></TD><TD>Details about the container&#39;s current condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="cronjob-v1beta1-batch">CronJob v1beta1 batch</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CronJob</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#cronjob-v2alpha1-batch">v2alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjoblist-v1beta1-batch">CronJobList [batch/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#cronjobspec-v1beta1-batch">CronJobSpec</a></I></TD><TD>Specification of the desired behavior of a cron job, including the schedule. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#cronjobstatus-v1beta1-batch">CronJobStatus</a></I></TD><TD>Current status of a cron job. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="cronjobspec-v1beta1-batch">CronJobSpec v1beta1 batch</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjob-v1beta1-batch">CronJob [batch/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>concurrencyPolicy</CODE><BR /><I>string</I></TD><TD>Specifies how to treat concurrent executions of a Job. Valid values are: - &#34;Allow&#34; (default): allows CronJobs to run concurrently; - &#34;Forbid&#34;: forbids concurrent runs, skipping next run if previous run hasn&#39;t finished yet; - &#34;Replace&#34;: cancels currently running job and replaces it with a new one</TD></TR>
<TR><TD><CODE>failedJobsHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of failed finished jobs to retain. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.</TD></TR>
<TR><TD><CODE>jobTemplate</CODE><BR /><I><a href="#jobtemplatespec-v1beta1-batch">JobTemplateSpec</a></I></TD><TD>Specifies the job that will be created when executing a CronJob.</TD></TR>
<TR><TD><CODE>schedule</CODE><BR /><I>string</I></TD><TD>The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.</TD></TR>
<TR><TD><CODE>startingDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>Optional deadline in seconds for starting the job if it misses scheduled time for any reason. Missed jobs executions will be counted as failed ones.</TD></TR>
<TR><TD><CODE>successfulJobsHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of successful finished jobs to retain. This is a pointer to distinguish between explicit zero and not specified. Defaults to 3.</TD></TR>
<TR><TD><CODE>suspend</CODE><BR /><I>boolean</I></TD><TD>This flag tells the controller to suspend subsequent executions, it does not apply to already started executions. Defaults to false.</TD></TR>
</TBODY>
</TABLE>
<H3 id="cronjobstatus-v1beta1-batch">CronJobStatus v1beta1 batch</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjob-v1beta1-batch">CronJob [batch/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>active</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a> array</I></TD><TD>A list of pointers to currently running jobs.</TD></TR>
<TR><TD><CODE>lastScheduleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Information when was the last time the job was successfully scheduled.</TD></TR>
</TBODY>
</TABLE>
<H3 id="cronjoblist-v1beta1-batch">CronJobList v1beta1 batch</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#cronjob-v1beta1-batch">CronJob</a> array</I></TD><TD>items is the list of CronJobs.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-cronjob-v1beta1-batch-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-cronjob-v1beta1-batch">Create</H2>
<P>create a CronJob</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/batch/v1beta1/namespaces/{namespace}/cronjobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-cronjob-v1beta1-batch">Patch</H2>
<P>partially update the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-cronjob-v1beta1-batch">Replace</H2>
<P>replace the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-cronjob-v1beta1-batch">Delete</H2>
<P>delete a CronJob</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-cronjob-v1beta1-batch">Delete Collection</H2>
<P>delete collection of CronJob</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/batch/v1beta1/namespaces/{namespace}/cronjobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-cronjob-v1beta1-batch-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-cronjob-v1beta1-batch">Read</H2>
<P>read the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-cronjob-v1beta1-batch">List</H2>
<P>list or watch objects of kind CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1beta1/namespaces/{namespace}/cronjobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjoblist-v1beta1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-cronjob-v1beta1-batch">List All Namespaces</H2>
<P>list or watch objects of kind CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1beta1/cronjobs</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjoblist-v1beta1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-cronjob-v1beta1-batch">Watch</H2>
<P>watch changes to an object of kind CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1beta1/watch/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-cronjob-v1beta1-batch">Watch List</H2>
<P>watch individual changes to a list of CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1beta1/watch/namespaces/{namespace}/cronjobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-cronjob-v1beta1-batch">Watch List All Namespaces</H2>
<P>watch individual changes to a list of CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1beta1/watch/cronjobs</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-cronjob-v1beta1-batch-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-cronjob-v1beta1-batch">Patch Status</H2>
<P>partially update status of the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-cronjob-v1beta1-batch">Read Status</H2>
<P>read status of the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-cronjob-v1beta1-batch">Replace Status</H2>
<P>replace status of the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/batch/v1beta1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#cronjob-v1beta1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="daemonset-v1-apps">DaemonSet v1 apps</H1>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#kubectl-daemonset-v1-apps" aria-controls="kubectl-daemonset-v1-apps"
aria-expanded="false">kubectl example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#curl-daemonset-v1-apps" aria-controls="curl-daemonset-v1-apps"
aria-expanded="false">curl example</BUTTON>
<DIV class="collapse" id="kubectl-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">DaemonSet Config to print the `hostname` on each Node in the cluster every 10 seconds.</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-yaml">
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
# Unique key of the DaemonSet instance
name: daemonset-example
spec:
template:
metadata:
labels:
app: daemonset-example
spec:
containers:
# This container is run once on each Node in the cluster
- name: daemonset-example
image: ubuntu:trusty
command:
- /bin/sh
args:
- -c
# This script is run through `sh -c &lt;script&gt;`
- &gt;-
while [ true ]; do
echo &#34;DaemonSet running on $(hostname)&#34; ;
sleep 10 ;
done
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="curl-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">DaemonSet Config to print the `hostname` on each Node in the cluster every 10 seconds.</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-yaml">
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
# Unique key of the DaemonSet instance
name: daemonset-example
spec:
template:
metadata:
labels:
app: daemonset-example
spec:
containers:
# This container is run once on each Node in the cluster
- name: daemonset-example
image: ubuntu:trusty
command:
- /bin/sh
args:
- -c
# This script is run through `sh -c &lt;script&gt;`
- &gt;-
while [ true ]; do
echo &#34;DaemonSet running on $(hostname)&#34; ;
sleep 10 ;
done
</CODE></PRE></DIV></DIV></DIV>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DaemonSet</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#daemonset-v1beta2-apps">v1beta2</a>
<a href="#daemonset-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetlist-v1-apps">DaemonSetList [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#daemonsetspec-v1-apps">DaemonSetSpec</a></I></TD><TD>The desired behavior of this daemon set. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#daemonsetstatus-v1-apps">DaemonSetStatus</a></I></TD><TD>The current status of this daemon set. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="daemonsetspec-v1-apps">DaemonSetSpec v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonset-v1-apps">DaemonSet [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over pods that are managed by the daemon set. Must match in order to be controlled. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>An object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template&#39;s node selector (or on every node if no node selector is specified). More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
<TR><TD><CODE>updateStrategy</CODE><BR /><I><a href="#daemonsetupdatestrategy-v1-apps">DaemonSetUpdateStrategy</a></I></TD><TD>An update strategy to replace existing DaemonSet pods with new pods.</TD></TR>
</TBODY>
</TABLE>
<H3 id="daemonsetstatus-v1-apps">DaemonSetStatus v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonset-v1-apps">DaemonSet [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#daemonsetcondition-v1-apps">DaemonSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a DaemonSet&#39;s current state.</TD></TR>
<TR><TD><CODE>currentNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
<TR><TD><CODE>desiredNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
<TR><TD><CODE>numberAvailable</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)</TD></TR>
<TR><TD><CODE>numberMisscheduled</CODE><BR /><I>integer</I></TD><TD>The number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
<TR><TD><CODE>numberReady</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.</TD></TR>
<TR><TD><CODE>numberUnavailable</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The most recent generation observed by the daemon set controller.</TD></TR>
<TR><TD><CODE>updatedNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The total number of nodes that are running updated daemon pod</TD></TR>
</TBODY>
</TABLE>
<H3 id="daemonsetlist-v1-apps">DaemonSetList v1 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#daemonset-v1-apps">DaemonSet</a> array</I></TD><TD>A list of daemon sets.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H3 id="rollingupdatedaemonset-v1-apps">RollingUpdateDaemonSet v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetupdatestrategy-v1-apps">DaemonSetUpdateStrategy [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxUnavailable</CODE></TD><TD>The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-daemonset-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-daemonset-v1-apps">Create</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-create-daemonset-v1-apps" aria-controls="req-kubectl-create-daemonset-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-create-daemonset-v1-apps" aria-controls="req-curl-create-daemonset-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-create-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
name: daemonset-example
spec:
template:
metadata:
labels:
app: daemonset-example
spec:
containers:
- name: daemonset-example
image: ubuntu:trusty
command:
- /bin/sh
args:
- -c
- >-
while [ true ]; do
echo "DaemonSet running on $(hostname)" ;
sleep 10 ;
done
' | kubectl create -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-create-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X POST -H 'Content-Type: application/yaml' --data '
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
name: daemonset-example
spec:
template:
metadata:
labels:
app: daemonset-example
spec:
containers:
- name: daemonset-example
image: ubuntu:trusty
command:
- /bin/sh
args:
- -c
- >-
while [ true ]; do
echo "DaemonSet running on $(hostname)" ;
sleep 10 ;
done
' http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-create-daemonset-v1-apps" aria-controls="res-kubectl-create-daemonset-v1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-create-daemonset-v1-apps" aria-controls="res-curl-create-daemonset-v1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-create-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
daemonset "daemonset-example" created
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-create-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "DaemonSet",
"apiVersion": "extensions/v1beta1",
"metadata": {
"name": "daemonset-example",
"namespace": "default",
"selfLink": "/apis/extensions/v1beta1/namespaces/default/daemonsets/daemonset-example",
"uid": "65552ced-b0e2-11e6-aef0-42010af00229",
"resourceVersion": "3558",
"generation": 1,
"creationTimestamp": "2016-11-22T18:35:09Z",
"labels": {
"app": "daemonset-example"
}
},
"spec": {
"selector": {
"matchLabels": {
"app": "daemonset-example"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "daemonset-example"
}
},
"spec": {
"containers": [
{
"name": "daemonset-example",
"image": "ubuntu:trusty",
"command": [
"/bin/sh"
],
"args": [
"-c",
"while [ true ]; do echo \"DaemonSet running on $(hostname)\" ; sleep 10 ; done"
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
}
},
"status": {
"currentNumberScheduled": 0,
"numberMisscheduled": 0,
"desiredNumberScheduled": 0
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>create a DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-daemonset-v1-apps">Patch</H2>
<P>partially update the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-daemonset-v1-apps">Replace</H2>
<P>replace the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-daemonset-v1-apps">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-delete-daemonset-v1-apps" aria-controls="req-kubectl-delete-daemonset-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-delete-daemonset-v1-apps" aria-controls="req-curl-delete-daemonset-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-delete-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl delete daemonset daemonset-example
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-delete-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
gracePeriodSeconds: 0
orphanDependents: false
' 'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets/daemonset-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-delete-daemonset-v1-apps" aria-controls="res-kubectl-delete-daemonset-v1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-delete-daemonset-v1-apps" aria-controls="res-curl-delete-daemonset-v1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-delete-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
daemonset "daemonset-example" deleted
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-delete-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"code": 200
}
</CODE></PRE></DIV></DIV></DIV>
<P>delete a DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-daemonset-v1-apps">Delete Collection</H2>
<P>delete collection of DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-daemonset-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-daemonset-v1-apps">Read</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-read-daemonset-v1-apps" aria-controls="req-kubectl-read-daemonset-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-read-daemonset-v1-apps" aria-controls="req-curl-read-daemonset-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-read-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get daemonset daemonset-example -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-read-daemonset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/daemonsets/daemonset-example
</CODE></PRE></DIV></DIV></DIV>
<P>read the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-daemonset-v1-apps">List</H2>
<P>list or watch objects of kind DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonsetlist-v1-apps">DaemonSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-daemonset-v1-apps">List All Namespaces</H2>
<P>list or watch objects of kind DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/daemonsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonsetlist-v1-apps">DaemonSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-daemonset-v1-apps">Watch</H2>
<P>watch changes to an object of kind DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-daemonset-v1-apps">Watch List</H2>
<P>watch individual changes to a list of DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-daemonset-v1-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/daemonsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-daemonset-v1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-daemonset-v1-apps">Patch Status</H2>
<P>partially update status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-daemonset-v1-apps">Read Status</H2>
<P>read status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-daemonset-v1-apps">Replace Status</H2>
<P>replace status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/daemonsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#daemonset-v1-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="deployment-v1-apps">Deployment v1 apps</H1>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#kubectl-deployment-v1-apps" aria-controls="kubectl-deployment-v1-apps"
aria-expanded="false">kubectl example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#curl-deployment-v1-apps" aria-controls="curl-deployment-v1-apps"
aria-expanded="false">curl example</BUTTON>
<DIV class="collapse" id="kubectl-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Deployment Config to run 3 nginx instances (max rollback set to 10 revisions).</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-yaml">
apiVersion: apps/v1beta1
kind: Deployment
metadata:
# Unique key of the Deployment instance
name: deployment-example
spec:
# 3 Pods should exist at all times.
replicas: 3
template:
metadata:
labels:
# Apply this label to pods and default
# the Deployment label selector to this value
app: nginx
spec:
containers:
- name: nginx
# Run this image
image: nginx:1.10
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="curl-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Deployment Config to run 3 nginx instances (max rollback set to 10 revisions).</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-yaml">
apiVersion: apps/v1beta1
kind: Deployment
metadata:
# Unique key of the Deployment instance
name: deployment-example
spec:
# 3 Pods should exist at all times.
replicas: 3
template:
metadata:
labels:
# Apply this label to pods and default
# the Deployment label selector to this value
app: nginx
spec:
containers:
- name: nginx
# Run this image
image: nginx:1.10
</CODE></PRE></DIV></DIV></DIV>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Deployment</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#deployment-v1beta2-apps">v1beta2</a>
<a href="#deployment-v1beta1-apps">v1beta1</a>
<a href="#deployment-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentlist-v1-apps">DeploymentList [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#deploymentspec-v1-apps">DeploymentSpec</a></I></TD><TD>Specification of the desired behavior of the Deployment.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#deploymentstatus-v1-apps">DeploymentStatus</a></I></TD><TD>Most recently observed status of the Deployment.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentspec-v1-apps">DeploymentSpec v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deployment-v1-apps">Deployment [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
<TR><TD><CODE>paused</CODE><BR /><I>boolean</I></TD><TD>Indicates that the deployment is paused.</TD></TR>
<TR><TD><CODE>progressDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. Defaults to 600s.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment. It must match the pod template&#39;s labels.</TD></TR>
<TR><TD><CODE>strategy</CODE><BR /><I><a href="#deploymentstrategy-v1-apps">DeploymentStrategy</a></I></TD><TD>The deployment strategy to use to replace existing pods with new ones.</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template describes the pods that will be created.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentstatus-v1-apps">DeploymentStatus v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deployment-v1-apps">Deployment [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.</TD></TR>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#deploymentcondition-v1-apps">DeploymentCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a deployment&#39;s current state.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The generation observed by the deployment controller.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of ready pods targeted by this deployment.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment (their labels match the selector).</TD></TR>
<TR><TD><CODE>unavailableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.</TD></TR>
<TR><TD><CODE>updatedReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment that have the desired template spec.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentlist-v1-apps">DeploymentList v1 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#deployment-v1-apps">Deployment</a> array</I></TD><TD>Items is the list of Deployments.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentstrategy-v1-apps">DeploymentStrategy v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentspec-v1-apps">DeploymentSpec [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatedeployment-v1-apps">RollingUpdateDeployment</a></I></TD><TD>Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment. Can be &#34;Recreate&#34; or &#34;RollingUpdate&#34;. Default is RollingUpdate.</TD></TR>
</TBODY>
</TABLE>
<H3 id="rollingupdatedeployment-v1-apps">RollingUpdateDeployment v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentstrategy-v1-apps">DeploymentStrategy [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxSurge</CODE></TD><TD>The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new ReplicaSet can be scaled up further, ensuring that total number of pods running at any time during the update is at most 130% of desired pods.</TD></TR>
<TR><TD><CODE>maxUnavailable</CODE></TD><TD>The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old ReplicaSet can be scaled down further, followed by scaling up the new ReplicaSet, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-deployment-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-deployment-v1-apps">Create</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-create-deployment-v1-apps" aria-controls="req-kubectl-create-deployment-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-create-deployment-v1-apps" aria-controls="req-curl-create-deployment-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-create-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.10
ports:
- containerPort: 80
' | kubectl create -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-create-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X POST -H 'Content-Type: application/yaml' --data '
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.10
ports:
- containerPort: 80
' http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-create-deployment-v1-apps" aria-controls="res-kubectl-create-deployment-v1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-create-deployment-v1-apps" aria-controls="res-curl-create-deployment-v1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-create-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" created
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-create-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
"resourceVersion": "2118306",
"generation": 1,
"creationTimestamp": "2016-10-28T01:53:19Z",
"labels": {
"app": "nginx"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {}
}
</CODE></PRE></DIV></DIV></DIV>
<P>create a Deployment</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-deployment-v1-apps">Patch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-patch-deployment-v1-apps" aria-controls="req-kubectl-patch-deployment-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-patch-deployment-v1-apps" aria-controls="req-curl-patch-deployment-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-patch-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl patch deployment deployment-example -p \
'{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.11"}]}}}}'
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-patch-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PATCH -H 'Content-Type: application/strategic-merge-patch+json' --data '
{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.11"}]}}}}' \
'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-patch-deployment-v1-apps" aria-controls="res-kubectl-patch-deployment-v1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-patch-deployment-v1-apps" aria-controls="res-curl-patch-deployment-v1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-patch-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
"deployment-example" patched
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-patch-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "5dc3a8e6-b0ee-11e6-aef0-42010af00229",
"resourceVersion": "164489",
"generation": 11,
"creationTimestamp": "2016-11-22T20:00:50Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "5"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.11",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {
"observedGeneration": 10,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>partially update the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-deployment-v1-apps">Replace</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-replace-deployment-v1-apps" aria-controls="req-kubectl-replace-deployment-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-replace-deployment-v1-apps" aria-controls="req-curl-replace-deployment-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-replace-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.11
ports:
- containerPort: 80
' | kubectl replace -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-replace-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PUT -H 'Content-Type: application/yaml' --data '
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.11
ports:
- containerPort: 80
' http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-replace-deployment-v1-apps" aria-controls="res-kubectl-replace-deployment-v1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-replace-deployment-v1-apps" aria-controls="res-curl-replace-deployment-v1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-replace-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" replaced
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-replace-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
"resourceVersion": "2119082",
"generation": 5,
"creationTimestamp": "2016-10-28T01:53:19Z",
"labels": {
"app": "nginx"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.11",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>replace the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-deployment-v1-apps">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-delete-deployment-v1-apps" aria-controls="req-kubectl-delete-deployment-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-delete-deployment-v1-apps" aria-controls="req-curl-delete-deployment-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-delete-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl delete deployment deployment-example
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-delete-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
gracePeriodSeconds: 0
orphanDependents: false
' 'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-delete-deployment-v1-apps" aria-controls="res-kubectl-delete-deployment-v1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-delete-deployment-v1-apps" aria-controls="res-curl-delete-deployment-v1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-delete-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" deleted
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-delete-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"code": 200
}
</CODE></PRE></DIV></DIV></DIV>
<P>delete a Deployment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-deployment-v1-apps">Delete Collection</H2>
<P>delete collection of Deployment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-deployment-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-deployment-v1-apps">Read</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-read-deployment-v1-apps" aria-controls="req-kubectl-read-deployment-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-read-deployment-v1-apps" aria-controls="req-curl-read-deployment-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-read-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment deployment-example -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-read-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-read-deployment-v1-apps" aria-controls="res-kubectl-read-deployment-v1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-read-deployment-v1-apps" aria-controls="res-curl-read-deployment-v1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-read-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-read-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>read the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-deployment-v1-apps">List</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-list-deployment-v1-apps" aria-controls="req-kubectl-list-deployment-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-list-deployment-v1-apps" aria-controls="req-curl-list-deployment-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-list-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-list-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1/namespaces/default/deployments'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-list-deployment-v1-apps" aria-controls="res-kubectl-list-deployment-v1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-list-deployment-v1-apps" aria-controls="res-curl-list-deployment-v1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-list-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "List",
"apiVersion": "v1",
"metadata": {},
"items": [
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "docs",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
"uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
"resourceVersion": "1924126",
"generation": 21,
"creationTimestamp": "2016-10-13T16:06:00Z",
"labels": {
"run": "docs"
},
"annotations": {
"deployment.kubernetes.io/revision": "10",
"replicatingperfection.net/push-image": "true"
}
},
"spec": {
"replicas": 1,
"selector": {
"matchLabels": {
"run": "docs"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"auto-pushed-image-pwittrock/api-docs": "1477496453",
"run": "docs"
}
},
"spec": {
"containers": [
{
"name": "docs",
"image": "pwittrock/api-docs:v9",
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 21,
"replicas": 1,
"updatedReplicas": 1,
"availableReplicas": 1
}
},
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-list-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "List",
"apiVersion": "v1",
"metadata": {},
"items": [
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "docs",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
"uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
"resourceVersion": "1924126",
"generation": 21,
"creationTimestamp": "2016-10-13T16:06:00Z",
"labels": {
"run": "docs"
},
"annotations": {
"deployment.kubernetes.io/revision": "10",
"replicatingperfection.net/push-image": "true"
}
},
"spec": {
"replicas": 1,
"selector": {
"matchLabels": {
"run": "docs"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"auto-pushed-image-pwittrock/api-docs": "1477496453",
"run": "docs"
}
},
"spec": {
"containers": [
{
"name": "docs",
"image": "pwittrock/api-docs:v9",
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 21,
"replicas": 1,
"updatedReplicas": 1,
"availableReplicas": 1
}
},
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<P>list or watch objects of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deploymentlist-v1-apps">DeploymentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-deployment-v1-apps">List All Namespaces</H2>
<P>list or watch objects of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/deployments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deploymentlist-v1-apps">DeploymentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-deployment-v1-apps">Watch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-watch-deployment-v1-apps" aria-controls="req-kubectl-watch-deployment-v1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-watch-deployment-v1-apps" aria-controls="req-curl-watch-deployment-v1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-watch-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment deployment-example --watch -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-watch-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1/watch/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-watch-deployment-v1-apps" aria-controls="res-kubectl-watch-deployment-v1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-watch-deployment-v1-apps" aria-controls="res-curl-watch-deployment-v1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-watch-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
"resourceVersion": "2128095",
"generation": 2,
"creationTimestamp": "2016-10-28T03:34:12Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "3"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 2,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-watch-deployment-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
"resourceVersion": "2128095",
"generation": 2,
"creationTimestamp": "2016-10-28T03:34:12Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "3"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 2,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>watch changes to an object of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-deployment-v1-apps">Watch List</H2>
<P>watch individual changes to a list of Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-deployment-v1-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/deployments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-deployment-v1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-deployment-v1-apps">Patch Status</H2>
<P>partially update status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-deployment-v1-apps">Read Status</H2>
<P>read status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-deployment-v1-apps">Replace Status</H2>
<P>replace status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deployment-v1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-deployment-v1-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-deployment-v1-apps">Read Scale</H2>
<P>read scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-deployment-v1-apps">Replace Scale</H2>
<P>replace scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-deployment-v1-apps">Patch Scale</H2>
<P>partially update scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="job-v1-batch">Job v1 batch</H1>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#kubectl-job-v1-batch" aria-controls="kubectl-job-v1-batch"
aria-expanded="false">kubectl example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#curl-job-v1-batch" aria-controls="curl-job-v1-batch"
aria-expanded="false">curl example</BUTTON>
<DIV class="collapse" id="kubectl-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Job Config to print pi up to 2000 digits (then exit).</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-yaml">
apiVersion: batch/v1
kind: Job
metadata:
# Unique key of the Job instance
name: example-job
spec:
template:
metadata:
name: example-job
spec:
containers:
- name: pi
image: perl
command: [&#34;perl&#34;]
args: [&#34;-Mbignum=bpi&#34;, &#34;-wle&#34;, &#34;print bpi(2000)&#34;]
# Do not restart containers after they exit
restartPolicy: Never
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="curl-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Job Config to print pi up to 2000 digits (then exit).</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-yaml">
apiVersion: batch/v1
kind: Job
metadata:
# Unique key of the Job instance
name: example-job
spec:
template:
metadata:
name: example-job
spec:
containers:
- name: pi
image: perl
command: [&#34;perl&#34;]
args: [&#34;-Mbignum=bpi&#34;, &#34;-wle&#34;, &#34;print bpi(2000)&#34;]
# Do not restart containers after they exit
restartPolicy: Never
</CODE></PRE></DIV></DIV></DIV>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Job</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#joblist-v1-batch">JobList [batch/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#jobspec-v1-batch">JobSpec</a></I></TD><TD>Specification of the desired behavior of a job. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#jobstatus-v1-batch">JobStatus</a></I></TD><TD>Current status of a job. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="jobspec-v1-batch">JobSpec v1 batch</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#job-v1-batch">Job [batch/v1]</a></LI>
<LI><a href="#jobtemplatespec-v1beta1-batch">JobTemplateSpec [batch/v1beta1]</a></LI>
<LI><a href="#jobtemplatespec-v2alpha1-batch">JobTemplateSpec [batch/v2alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>activeDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>Specifies the duration in seconds relative to the startTime that the job may be active before the system tries to terminate it; value must be positive integer</TD></TR>
<TR><TD><CODE>backoffLimit</CODE><BR /><I>integer</I></TD><TD>Specifies the number of retries before marking this job failed. Defaults to 6</TD></TR>
<TR><TD><CODE>completions</CODE><BR /><I>integer</I></TD><TD>Specifies the desired number of successfully finished pods the job should be run with. Setting to nil means that the success of any pod signals the success of all pods, and allows parallelism to have any positive value. Setting to 1 means that parallelism is limited to 1 and the success of that pod signals the success of the job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/</TD></TR>
<TR><TD><CODE>manualSelector</CODE><BR /><I>boolean</I></TD><TD>manualSelector controls generation of pod labels and pod selectors. Leave `manualSelector` unset unless you are certain what you are doing. When false or unset, the system pick labels unique to this job and appends those labels to the pod template. When true, the user is responsible for picking unique labels and specifying the selector. Failure to pick a unique label may cause this and other jobs to not function correctly. However, You may see `manualSelector=true` in jobs that were created with the old `extensions/v1beta1` API. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#specifying-your-own-pod-selector</TD></TR>
<TR><TD><CODE>parallelism</CODE><BR /><I>integer</I></TD><TD>Specifies the maximum desired number of pods the job should run at any given time. The actual number of pods running in steady state will be less than this number when ((.spec.completions - .status.successful) &lt; .spec.parallelism), i.e. when the work left to do is less than max parallelism. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over pods that should match the pod count. Normally, the system sets this field for you. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Describes the pod that will be created when executing a job. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/</TD></TR>
</TBODY>
</TABLE>
<H3 id="jobstatus-v1-batch">JobStatus v1 batch</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#job-v1-batch">Job [batch/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>active</CODE><BR /><I>integer</I></TD><TD>The number of actively running pods.</TD></TR>
<TR><TD><CODE>completionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Represents time when the job was completed. It is not guaranteed to be set in happens-before order across separate operations. It is represented in RFC3339 form and is in UTC.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#jobcondition-v1-batch">JobCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>The latest available observations of an object&#39;s current state. More info: https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/</TD></TR>
<TR><TD><CODE>failed</CODE><BR /><I>integer</I></TD><TD>The number of pods which reached phase Failed.</TD></TR>
<TR><TD><CODE>startTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Represents time when the job was acknowledged by the job controller. It is not guaranteed to be set in happens-before order across separate operations. It is represented in RFC3339 form and is in UTC.</TD></TR>
<TR><TD><CODE>succeeded</CODE><BR /><I>integer</I></TD><TD>The number of pods which reached phase Succeeded.</TD></TR>
</TBODY>
</TABLE>
<H3 id="joblist-v1-batch">JobList v1 batch</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#job-v1-batch">Job</a> array</I></TD><TD>items is the list of Jobs.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-job-v1-batch-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-job-v1-batch">Create</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-create-job-v1-batch" aria-controls="req-kubectl-create-job-v1-batch"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-create-job-v1-batch" aria-controls="req-curl-create-job-v1-batch"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-create-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: batch/v1
kind: Job
metadata:
name: example-job
spec:
template:
metadata:
name: example-job
spec:
containers:
- name: pi
image: perl
command: ["perl", "-Mbignum=bpi", "-wle", "print bpi(2000)"]
restartPolicy: Never
' | kubectl create -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-create-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X POST -H 'Content-Type: application/yaml' --data '
apiVersion: batch/v1
kind: Job
metadata:
name: example-job
spec:
template:
metadata:
name: example-job
spec:
containers:
- name: pi
image: perl
command: ["perl", "-Mbignum=bpi", "-wle", "print bpi(2000)"]
restartPolicy: Never
' http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-create-job-v1-batch" aria-controls="res-kubectl-create-job-v1-batch"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-create-job-v1-batch" aria-controls="res-curl-create-job-v1-batch"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-create-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
job "example-job" created
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-create-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Job",
"apiVersion": "batch/v1",
"metadata": {
"name": "example-job",
"namespace": "default",
"selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
"uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"resourceVersion": "7479",
"creationTimestamp": "2016-11-04T18:45:25Z"
},
"spec": {
"parallelism": 1,
"completions": 1,
"selector": {
"matchLabels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
}
},
"template": {
"metadata": {
"name": "example-job",
"creationTimestamp": null,
"labels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"job-name": "example-job"
}
},
"spec": {
"containers": [
{
"name": "pi",
"image": "perl",
"command": [
"perl",
"-Mbignum=bpi",
"-wle",
"print bpi(2000)"
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Never",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
}
},
"status": {}
}
</CODE></PRE></DIV></DIV></DIV>
<P>create a Job</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/batch/v1/namespaces/{namespace}/jobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#job-v1-batch">Job</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-job-v1-batch">Patch</H2>
<P>partially update the specified Job</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-job-v1-batch">Replace</H2>
<P>replace the specified Job</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#job-v1-batch">Job</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-job-v1-batch">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-delete-job-v1-batch" aria-controls="req-kubectl-delete-job-v1-batch"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-delete-job-v1-batch" aria-controls="req-curl-delete-job-v1-batch"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-delete-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl delete job example-job
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-delete-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
gracePeriodSeconds: 0
orphanDependents: false
' 'http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs/example-job'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-delete-job-v1-batch" aria-controls="res-kubectl-delete-job-v1-batch"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-delete-job-v1-batch" aria-controls="res-curl-delete-job-v1-batch"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-delete-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
job "example-job" deleted
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-delete-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"code": 200
}
</CODE></PRE></DIV></DIV></DIV>
<P>delete a Job</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-job-v1-batch">Delete Collection</H2>
<P>delete collection of Job</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/batch/v1/namespaces/{namespace}/jobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-job-v1-batch-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-job-v1-batch">Read</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-read-job-v1-batch" aria-controls="req-kubectl-read-job-v1-batch"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-read-job-v1-batch" aria-controls="req-curl-read-job-v1-batch"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-read-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get job example-job -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-read-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs/example-job
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-read-job-v1-batch" aria-controls="res-kubectl-read-job-v1-batch"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-read-job-v1-batch" aria-controls="res-curl-read-job-v1-batch"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-read-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "Job",
"apiVersion": "batch/v1",
"metadata": {
"name": "example-job",
"namespace": "default",
"selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
"uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"resourceVersion": "7482",
"creationTimestamp": "2016-11-04T18:45:25Z"
},
"spec": {
"parallelism": 1,
"completions": 1,
"selector": {
"matchLabels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
}
},
"template": {
"metadata": {
"name": "example-job",
"creationTimestamp": null,
"labels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"job-name": "example-job"
}
},
"spec": {
"containers": [
{
"name": "pi",
"image": "perl",
"command": [
"perl",
"-Mbignum=bpi",
"-wle",
"print bpi(2000)"
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Never",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
}
},
"status": {
"startTime": "2016-11-04T18:45:25Z",
"active": 1
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-read-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Job",
"apiVersion": "batch/v1",
"metadata": {
"name": "example-job",
"namespace": "default",
"selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
"uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"resourceVersion": "7482",
"creationTimestamp": "2016-11-04T18:45:25Z"
},
"spec": {
"parallelism": 1,
"completions": 1,
"selector": {
"matchLabels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
}
},
"template": {
"metadata": {
"name": "example-job",
"creationTimestamp": null,
"labels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"job-name": "example-job"
}
},
"spec": {
"containers": [
{
"name": "pi",
"image": "perl",
"command": [
"perl",
"-Mbignum=bpi",
"-wle",
"print bpi(2000)"
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Never",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
}
},
"status": {
"startTime": "2016-11-04T18:45:25Z",
"active": 1
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>read the specified Job</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1/namespaces/{namespace}/jobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-job-v1-batch">List</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-list-job-v1-batch" aria-controls="req-kubectl-list-job-v1-batch"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-list-job-v1-batch" aria-controls="req-curl-list-job-v1-batch"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-list-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get job -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-list-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/batch/v1/namespaces/default/jobs'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-list-job-v1-batch" aria-controls="res-kubectl-list-job-v1-batch"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-list-job-v1-batch" aria-controls="res-curl-list-job-v1-batch"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-list-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "JobList",
"apiVersion": "batch/v1",
"metadata": {
"selfLink": "/apis/batch/v1/namespaces/default/jobs",
"resourceVersion": "7589"
},
"items": [
{
"metadata": {
"name": "",
"namespace": "default",
"selfLink": "/apis/batch/v1/namespaces/default/jobs/",
"uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"resourceVersion": "7482",
"creationTimestamp": "2016-11-04T18:45:25Z"
},
"spec": {
"parallelism": 1,
"completions": 1,
"selector": {
"matchLabels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
}
},
"template": {
"metadata": {
"name": "",
"creationTimestamp": null,
"labels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"job-name": ""
}
},
"spec": {
"containers": [
{
"name": "pi",
"image": "perl",
"command": [
"perl",
"-Mbignum=bpi",
"-wle",
"print bpi(2000)"
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Never",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
}
},
"status": {
"startTime": "2016-11-04T18:45:25Z",
"active": 1
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-list-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "JobList",
"apiVersion": "batch/v1",
"metadata": {
"selfLink": "/apis/batch/v1/namespaces/default/jobs",
"resourceVersion": "7589"
},
"items": [
{
"metadata": {
"name": "",
"namespace": "default",
"selfLink": "/apis/batch/v1/namespaces/default/jobs/",
"uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"resourceVersion": "7482",
"creationTimestamp": "2016-11-04T18:45:25Z"
},
"spec": {
"parallelism": 1,
"completions": 1,
"selector": {
"matchLabels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
}
},
"template": {
"metadata": {
"name": "",
"creationTimestamp": null,
"labels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"job-name": ""
}
},
"spec": {
"containers": [
{
"name": "pi",
"image": "perl",
"command": [
"perl",
"-Mbignum=bpi",
"-wle",
"print bpi(2000)"
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Never",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
}
},
"status": {
"startTime": "2016-11-04T18:45:25Z",
"active": 1
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<P>list or watch objects of kind Job</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1/namespaces/{namespace}/jobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#joblist-v1-batch">JobList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-job-v1-batch">List All Namespaces</H2>
<P>list or watch objects of kind Job</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1/jobs</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#joblist-v1-batch">JobList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-job-v1-batch">Watch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-watch-job-v1-batch" aria-controls="req-kubectl-watch-job-v1-batch"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-watch-job-v1-batch" aria-controls="req-curl-watch-job-v1-batch"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-watch-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get job example-job --watch -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-watch-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/batch/v1/watch/namespaces/default/jobs/example-job'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-watch-job-v1-batch" aria-controls="res-kubectl-watch-job-v1-batch"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-watch-job-v1-batch" aria-controls="res-curl-watch-job-v1-batch"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-watch-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Job",
"apiVersion": "batch/v1",
"metadata": {
"name": "example-job",
"namespace": "default",
"selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
"uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"resourceVersion": "7482",
"creationTimestamp": "2016-11-04T18:45:25Z"
},
"spec": {
"parallelism": 1,
"completions": 1,
"selector": {
"matchLabels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
}
},
"template": {
"metadata": {
"name": "example-job",
"creationTimestamp": null,
"labels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"job-name": "example-job"
}
},
"spec": {
"containers": [
{
"name": "pi",
"image": "perl",
"command": [
"perl",
"-Mbignum=bpi",
"-wle",
"print bpi(2000)"
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Never",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
}
},
"status": {
"startTime": "2016-11-04T18:45:25Z",
"active": 1
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-watch-job-v1-batch">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Job",
"apiVersion": "batch/v1",
"metadata": {
"name": "example-job",
"namespace": "default",
"selfLink": "/apis/batch/v1/namespaces/default/jobs/example-job",
"uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"resourceVersion": "7482",
"creationTimestamp": "2016-11-04T18:45:25Z"
},
"spec": {
"parallelism": 1,
"completions": 1,
"selector": {
"matchLabels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7"
}
},
"template": {
"metadata": {
"name": "example-job",
"creationTimestamp": null,
"labels": {
"controller-uid": "d93a3569-a2be-11e6-a008-fa043d458cc7",
"job-name": "example-job"
}
},
"spec": {
"containers": [
{
"name": "pi",
"image": "perl",
"command": [
"perl",
"-Mbignum=bpi",
"-wle",
"print bpi(2000)"
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Never",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
}
},
"status": {
"startTime": "2016-11-04T18:45:25Z",
"active": 1
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>watch changes to an object of kind Job</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/jobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-job-v1-batch">Watch List</H2>
<P>watch individual changes to a list of Job</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1/watch/namespaces/{namespace}/jobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-job-v1-batch">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Job</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1/watch/jobs</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-job-v1-batch-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-job-v1-batch">Patch Status</H2>
<P>partially update status of the specified Job</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-job-v1-batch">Read Status</H2>
<P>read status of the specified Job</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-job-v1-batch">Replace Status</H2>
<P>replace status of the specified Job</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Job</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#job-v1-batch">Job</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#job-v1-batch">Job</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="pod-v1-core">Pod v1 core</H1>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#kubectl-pod-v1-core" aria-controls="kubectl-pod-v1-core"
aria-expanded="false">kubectl example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#curl-pod-v1-core" aria-controls="curl-pod-v1-core"
aria-expanded="false">curl example</BUTTON>
<DIV class="collapse" id="kubectl-pod-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Pod Config to print "Hello World".</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-yaml">
apiVersion: v1
kind: Pod
metadata:
name: pod-example
spec:
containers:
- name: ubuntu
image: ubuntu:trusty
command: [&#34;echo&#34;]
args: [&#34;Hello World&#34;]
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="curl-pod-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Pod Config to print "Hello World".</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-yaml">
apiVersion: v1
kind: Pod
metadata:
name: pod-example
spec:
containers:
- name: ubuntu
image: ubuntu:trusty
command: [&#34;echo&#34;]
args: [&#34;Hello World&#34;]
</CODE></PRE></DIV></DIV></DIV>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Pod</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-warning col-md-8"><P><I class="fa fa-warning"></I> <B>Warning:</B></P><P>It is recommended that users create Pods only through a Controller, and not directly. See Controllers: <a href="#deployment-v1beta1-apps">Deployment</a>, <a href="#job-v1-batch">Job</a>, or <a href="#statefulset-v1beta1-apps">StatefulSet</a>.</P></DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podlist-v1-core">PodList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#podspec-v1-core">PodSpec</a></I></TD><TD>Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#podstatus-v1-core">PodStatus</a></I></TD><TD>Most recently observed status of the pod. This data may not be up to date. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="podspec-v1-core">PodSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#pod-v1-core">Pod [core/v1]</a></LI>
<LI><a href="#podtemplatespec-v1-core">PodTemplateSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>activeDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>Optional duration in seconds the pod may be active on the node relative to StartTime before the system will actively try to mark it failed and kill associated containers. Value must be a positive integer.</TD></TR>
<TR><TD><CODE>affinity</CODE><BR /><I><a href="#affinity-v1-core">Affinity</a></I></TD><TD>If specified, the pod&#39;s scheduling constraints</TD></TR>
<TR><TD><CODE>automountServiceAccountToken</CODE><BR /><I>boolean</I></TD><TD>AutomountServiceAccountToken indicates whether a service account token should be automatically mounted.</TD></TR>
<TR><TD><CODE>containers</CODE><BR /><I><a href="#container-v1-core">Container</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of containers belonging to the pod. Containers cannot currently be added or removed. There must be at least one container in a Pod. Cannot be updated.</TD></TR>
<TR><TD><CODE>dnsConfig</CODE><BR /><I><a href="#poddnsconfig-v1-core">PodDNSConfig</a></I></TD><TD>Specifies the DNS parameters of a pod. Parameters specified here will be merged to the generated DNS configuration based on DNSPolicy.</TD></TR>
<TR><TD><CODE>dnsPolicy</CODE><BR /><I>string</I></TD><TD>Set DNS policy for the pod. Defaults to &#34;ClusterFirst&#34;. Valid values are &#39;ClusterFirstWithHostNet&#39;, &#39;ClusterFirst&#39;, &#39;Default&#39; or &#39;None&#39;. DNS parameters given in DNSConfig will be merged with the policy selected with DNSPolicy. To have DNS options set along with hostNetwork, you have to specify DNS policy explicitly to &#39;ClusterFirstWithHostNet&#39;.</TD></TR>
<TR><TD><CODE>hostAliases</CODE><BR /><I><a href="#hostalias-v1-core">HostAlias</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>ip</I></TD><TD>HostAliases is an optional list of hosts and IPs that will be injected into the pod&#39;s hosts file if specified. This is only valid for non-hostNetwork pods.</TD></TR>
<TR><TD><CODE>hostIPC</CODE><BR /><I>boolean</I></TD><TD>Use the host&#39;s ipc namespace. Optional: Default to false.</TD></TR>
<TR><TD><CODE>hostNetwork</CODE><BR /><I>boolean</I></TD><TD>Host networking requested for this pod. Use the host&#39;s network namespace. If this option is set, the ports that will be used must be specified. Default to false.</TD></TR>
<TR><TD><CODE>hostPID</CODE><BR /><I>boolean</I></TD><TD>Use the host&#39;s pid namespace. Optional: Default to false.</TD></TR>
<TR><TD><CODE>hostname</CODE><BR /><I>string</I></TD><TD>Specifies the hostname of the Pod If not specified, the pod&#39;s hostname will be set to a system-defined value.</TD></TR>
<TR><TD><CODE>imagePullSecrets</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>ImagePullSecrets is an optional list of references to secrets in the same namespace to use for pulling any of the images used by this PodSpec. If specified, these secrets will be passed to individual puller implementations for them to use. For example, in the case of docker, only DockerConfig type secrets are honored. More info: https://kubernetes.io/docs/concepts/containers/images#specifying-imagepullsecrets-on-a-pod</TD></TR>
<TR><TD><CODE>initContainers</CODE><BR /><I><a href="#container-v1-core">Container</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed and is handled according to its restartPolicy. The name for an init container or normal container must be unique among all containers. Init containers may not have Lifecycle actions, Readiness probes, or Liveness probes. The resourceRequirements of an init container are taken into account during scheduling by finding the highest request/limit for each resource type, and then using the max of of that value or the sum of the normal containers. Limits are applied to init containers in a similar fashion. Init containers cannot currently be added or removed. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/</TD></TR>
<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>NodeName is a request to schedule this pod onto a specific node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits resource requirements.</TD></TR>
<TR><TD><CODE>nodeSelector</CODE><BR /><I>object</I></TD><TD>NodeSelector is a selector which must be true for the pod to fit on a node. Selector which must match a node&#39;s labels for the pod to be scheduled on that node. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/</TD></TR>
<TR><TD><CODE>priority</CODE><BR /><I>integer</I></TD><TD>The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.</TD></TR>
<TR><TD><CODE>priorityClassName</CODE><BR /><I>string</I></TD><TD>If specified, indicates the pod&#39;s priority. &#34;system-node-critical&#34; and &#34;system-cluster-critical&#34; are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.</TD></TR>
<TR><TD><CODE>readinessGates</CODE><BR /><I><a href="#podreadinessgate-v1-core">PodReadinessGate</a> array</I></TD><TD>If specified, all readiness gates will be evaluated for pod readiness. A pod is ready when all its containers are ready AND all conditions specified in the readiness gates have status equal to &#34;True&#34; More info: https://github.com/kubernetes/community/blob/master/keps/sig-network/0007-pod-ready%2B%2B.md</TD></TR>
<TR><TD><CODE>restartPolicy</CODE><BR /><I>string</I></TD><TD>Restart policy for all containers within the pod. One of Always, OnFailure, Never. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy</TD></TR>
<TR><TD><CODE>schedulerName</CODE><BR /><I>string</I></TD><TD>If specified, the pod will be dispatched by specified scheduler. If not specified, the pod will be dispatched by default scheduler.</TD></TR>
<TR><TD><CODE>securityContext</CODE><BR /><I><a href="#podsecuritycontext-v1-core">PodSecurityContext</a></I></TD><TD>SecurityContext holds pod-level security attributes and common container settings. Optional: Defaults to empty. See type description for default values of each field.</TD></TR>
<TR><TD><CODE>serviceAccount</CODE><BR /><I>string</I></TD><TD>DeprecatedServiceAccount is a depreciated alias for ServiceAccountName. Deprecated: Use serviceAccountName instead.</TD></TR>
<TR><TD><CODE>serviceAccountName</CODE><BR /><I>string</I></TD><TD>ServiceAccountName is the name of the ServiceAccount to use to run this pod. More info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/</TD></TR>
<TR><TD><CODE>shareProcessNamespace</CODE><BR /><I>boolean</I></TD><TD>Share a single process namespace between all of the containers in a pod. When this is set containers will be able to view and signal processes from other containers in the same pod, and the first process in each container will not be assigned PID 1. HostPID and ShareProcessNamespace cannot both be set. Optional: Default to false. This field is alpha-level and is honored only by servers that enable the PodShareProcessNamespace feature.</TD></TR>
<TR><TD><CODE>subdomain</CODE><BR /><I>string</I></TD><TD>If specified, the fully qualified Pod hostname will be &#34;&lt;hostname&gt;.&lt;subdomain&gt;.&lt;pod namespace&gt;.svc.&lt;cluster domain&gt;&#34;. If not specified, the pod will not have a domainname at all.</TD></TR>
<TR><TD><CODE>terminationGracePeriodSeconds</CODE><BR /><I>integer</I></TD><TD>Optional duration in seconds the pod needs to terminate gracefully. May be decreased in delete request. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period will be used instead. The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal. Set this value longer than the expected cleanup time for your process. Defaults to 30 seconds.</TD></TR>
<TR><TD><CODE>tolerations</CODE><BR /><I><a href="#toleration-v1-core">Toleration</a> array</I></TD><TD>If specified, the pod&#39;s tolerations.</TD></TR>
<TR><TD><CODE>volumes</CODE><BR /><I><a href="#volume-v1-core">Volume</a> array</I><BR /><B>patch strategy</B>: <I>merge,retainKeys</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of volumes that can be mounted by containers belonging to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes</TD></TR>
</TBODY>
</TABLE>
<H3 id="podstatus-v1-core">PodStatus v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#pod-v1-core">Pod [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#podcondition-v1-core">PodCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Current service state of pod. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditions</TD></TR>
<TR><TD><CODE>containerStatuses</CODE><BR /><I><a href="#containerstatus-v1-core">ContainerStatus</a> array</I></TD><TD>The list has one entry per container in the manifest. Each entry is currently the output of `docker inspect`. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status</TD></TR>
<TR><TD><CODE>hostIP</CODE><BR /><I>string</I></TD><TD>IP address of the host to which the pod is assigned. Empty if not yet scheduled.</TD></TR>
<TR><TD><CODE>initContainerStatuses</CODE><BR /><I><a href="#containerstatus-v1-core">ContainerStatus</a> array</I></TD><TD>The list has one entry per init container in the manifest. The most recent successful init container will have ready = true, the most recently started container will have startTime set. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-and-container-status</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about why the pod is in this condition.</TD></TR>
<TR><TD><CODE>nominatedNodeName</CODE><BR /><I>string</I></TD><TD>nominatedNodeName is set only when this pod preempts other pods on the node, but it cannot be scheduled right away as preemption victims receive their graceful termination periods. This field does not guarantee that the pod will be scheduled on this node. Scheduler may decide to place the pod elsewhere if other nodes become available sooner. Scheduler may also decide to give the resources on this node to a higher priority pod that is created after preemption. As a result, this field may be different than PodSpec.nodeName when the pod is scheduled.</TD></TR>
<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>The phase of a Pod is a simple, high-level summary of where the Pod is in its lifecycle. The conditions array, the reason and message fields, and the individual container status arrays contain more detail about the pod&#39;s status. There are five possible phase values: Pending: The pod has been accepted by the Kubernetes system, but one or more of the container images has not been created. This includes time before being scheduled as well as time spent downloading images over the network, which could take a while. Running: The pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. Succeeded: All containers in the pod have terminated in success, and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated in failure. The container either exited with non-zero status or was terminated by the system. Unknown: For some reason the state of the pod could not be obtained, typically due to an error in communicating with the host of the pod. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-phase</TD></TR>
<TR><TD><CODE>podIP</CODE><BR /><I>string</I></TD><TD>IP address allocated to the pod. Routable at least within the cluster. Empty if not yet allocated.</TD></TR>
<TR><TD><CODE>qosClass</CODE><BR /><I>string</I></TD><TD>The Quality of Service (QOS) classification assigned to the pod based on resource requirements See PodQOSClass type for available QOS classes More info: https://git.k8s.io/community/contributors/design-proposals/node/resource-qos.md</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>A brief CamelCase message indicating details about why the pod is in this state. e.g. &#39;Evicted&#39;</TD></TR>
<TR><TD><CODE>startTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>RFC 3339 date and time at which the object was acknowledged by the Kubelet. This is before the Kubelet pulled the container image(s) for the pod.</TD></TR>
</TBODY>
</TABLE>
<H3 id="podlist-v1-core">PodList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#pod-v1-core">Pod</a> array</I></TD><TD>List of pods. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-pod-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-pod-v1-core">Create</H2>
<P>create a Pod</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/pods</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="create-eviction-pod-v1-core">Create Eviction</H2>
<P>create eviction of a Pod</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/eviction</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Eviction</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#eviction-v1beta1-policy">Eviction</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#eviction-v1beta1-policy">Eviction</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#eviction-v1beta1-policy">Eviction</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#eviction-v1beta1-policy">Eviction</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-pod-v1-core">Patch</H2>
<P>partially update the specified Pod</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/pods/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-pod-v1-core">Replace</H2>
<P>replace the specified Pod</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-pod-v1-core">Delete</H2>
<P>delete a Pod</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/pods/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-pod-v1-core">Delete Collection</H2>
<P>delete collection of Pod</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/pods</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-pod-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-pod-v1-core">Read</H2>
<P>read the specified Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-pod-v1-core">List</H2>
<P>list or watch objects of kind Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/pods</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podlist-v1-core">PodList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-pod-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/pods</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podlist-v1-core">PodList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-pod-v1-core">Watch</H2>
<P>watch changes to an object of kind Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/pods/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-pod-v1-core">Watch List</H2>
<P>watch individual changes to a list of Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/pods</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-pod-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/pods</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-pod-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-pod-v1-core">Patch Status</H2>
<P>partially update status of the specified Pod</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/pods/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-pod-v1-core">Read Status</H2>
<P>read status of the specified Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-pod-v1-core">Replace Status</H2>
<P>replace status of the specified Pod</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#pod-v1-core">Pod</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-proxy-operations-pod-v1-core-strong-"><STRONG>Proxy Operations</STRONG></H2>
<H2 id="create-connect-portforward-pod-v1-core">Create Connect Portforward</H2>
<P>connect POST requests to portforward of Pod</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/portforward</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ports</CODE></TD><TD>List of ports to forward Required when using WebSockets</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="create-connect-proxy-pod-v1-core">Create Connect Proxy</H2>
<P>connect POST requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="create-connect-proxy-path-pod-v1-core">Create Connect Proxy Path</H2>
<P>connect POST requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-connect-proxy-pod-v1-core">Delete Connect Proxy</H2>
<P>connect DELETE requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-connect-proxy-path-pod-v1-core">Delete Connect Proxy Path</H2>
<P>connect DELETE requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="get-connect-portforward-pod-v1-core">Get Connect Portforward</H2>
<P>connect GET requests to portforward of Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/portforward</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ports</CODE></TD><TD>List of ports to forward Required when using WebSockets</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="get-connect-proxy-pod-v1-core">Get Connect Proxy</H2>
<P>connect GET requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="get-connect-proxy-path-pod-v1-core">Get Connect Proxy Path</H2>
<P>connect GET requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="head-connect-proxy-pod-v1-core">Head Connect Proxy</H2>
<P>connect HEAD requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>HEAD /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="head-connect-proxy-path-pod-v1-core">Head Connect Proxy Path</H2>
<P>connect HEAD requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>HEAD /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-connect-proxy-pod-v1-core">Replace Connect Proxy</H2>
<P>connect PUT requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-connect-proxy-path-pod-v1-core">Replace Connect Proxy Path</H2>
<P>connect PUT requests to proxy of Pod</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/pods/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to pod.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-pod-v1-core-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-log-pod-v1-core">Read Log</H2>
<P>read log of the specified Pod</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/pods/{name}/log</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Pod</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>container</CODE></TD><TD>The container for which to stream logs. Defaults to only container if there is one container in the pod.</TD></TR>
<TR><TD><CODE>follow</CODE></TD><TD>Follow the log stream of the pod. Defaults to false.</TD></TR>
<TR><TD><CODE>limitBytes</CODE></TD><TD>If set, the number of bytes to read from the server before terminating the log output. This may not display a complete final line of logging, and may return slightly more or slightly less than the specified limit.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>previous</CODE></TD><TD>Return previous terminated container logs. Defaults to false.</TD></TR>
<TR><TD><CODE>sinceSeconds</CODE></TD><TD>A relative time in seconds before the current time from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified.</TD></TR>
<TR><TD><CODE>tailLines</CODE></TD><TD>If set, the number of lines from the end of the logs to show. If not specified, logs are shown from the creation of the container or sinceSeconds or sinceTime</TD></TR>
<TR><TD><CODE>timestamps</CODE></TD><TD>If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="replicaset-v1-apps">ReplicaSet v1 apps</H1>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#kubectl-replicaset-v1-apps" aria-controls="kubectl-replicaset-v1-apps"
aria-expanded="false">kubectl example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#curl-replicaset-v1-apps" aria-controls="curl-replicaset-v1-apps"
aria-expanded="false">curl example</BUTTON>
<DIV class="collapse" id="kubectl-replicaset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">ReplicaSet Config to run 3 nginx instances.</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-yaml">
apiVersion: extensions/v1beta1
kind: ReplicaSet
metadata:
# Unique key of the ReplicaSet instance
name: replicaset-example
spec:
# 3 Pods should exist at all times.
replicas: 3
template:
metadata:
labels:
app: nginx
spec:
containers:
# Run the nginx image
- name: nginx
image: nginx:1.10
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="curl-replicaset-v1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">ReplicaSet Config to run 3 nginx instances.</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-yaml">
apiVersion: extensions/v1beta1
kind: ReplicaSet
metadata:
# Unique key of the ReplicaSet instance
name: replicaset-example
spec:
# 3 Pods should exist at all times.
replicas: 3
template:
metadata:
labels:
app: nginx
spec:
containers:
# Run the nginx image
- name: nginx
image: nginx:1.10
</CODE></PRE></DIV></DIV></DIV>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ReplicaSet</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-warning col-md-8"><P><I class="fa fa-warning"></I> <B>Warning:</B></P><P>In many cases it is recommended to create a <a href="#deployment-v1beta1-apps">Deployment</a> instead of ReplicaSet.</P></DIV>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#replicaset-v1beta2-apps">v1beta2</a>
<a href="#replicaset-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicasetlist-v1-apps">ReplicaSetList [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>If the Labels of a ReplicaSet are empty, they are defaulted to be the same as the Pod(s) that the ReplicaSet manages. Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#replicasetspec-v1-apps">ReplicaSetSpec</a></I></TD><TD>Spec defines the specification of the desired behavior of the ReplicaSet. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#replicasetstatus-v1-apps">ReplicaSetStatus</a></I></TD><TD>Status is the most recently observed status of the ReplicaSet. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicasetspec-v1-apps">ReplicaSetSpec v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicaset-v1-apps">ReplicaSet [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selector is a label query over pods that should match the replica count. Label keys and values that must match in order to be controlled by this replica set. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template is the object that describes the pod that will be created if insufficient replicas are detected. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicasetstatus-v1-apps">ReplicaSetStatus v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicaset-v1-apps">ReplicaSet [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>The number of available replicas (ready for at least minReadySeconds) for this replica set.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#replicasetcondition-v1-apps">ReplicaSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a replica set&#39;s current state.</TD></TR>
<TR><TD><CODE>fullyLabeledReplicas</CODE><BR /><I>integer</I></TD><TD>The number of pods that have labels matching the labels of the pod template of the replicaset.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>ObservedGeneration reflects the generation of the most recently observed ReplicaSet.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>The number of ready replicas for this replica set.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicasetlist-v1-apps">ReplicaSetList v1 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#replicaset-v1-apps">ReplicaSet</a> array</I></TD><TD>List of ReplicaSets. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-replicaset-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-replicaset-v1-apps">Create</H2>
<P>create a ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-replicaset-v1-apps">Patch</H2>
<P>partially update the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-replicaset-v1-apps">Replace</H2>
<P>replace the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-replicaset-v1-apps">Delete</H2>
<P>delete a ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-replicaset-v1-apps">Delete Collection</H2>
<P>delete collection of ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-replicaset-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-replicaset-v1-apps">Read</H2>
<P>read the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-replicaset-v1-apps">List</H2>
<P>list or watch objects of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicasetlist-v1-apps">ReplicaSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-replicaset-v1-apps">List All Namespaces</H2>
<P>list or watch objects of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/replicasets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicasetlist-v1-apps">ReplicaSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-replicaset-v1-apps">Watch</H2>
<P>watch changes to an object of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-replicaset-v1-apps">Watch List</H2>
<P>watch individual changes to a list of ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-replicaset-v1-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/replicasets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-replicaset-v1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-replicaset-v1-apps">Patch Status</H2>
<P>partially update status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-replicaset-v1-apps">Read Status</H2>
<P>read status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-replicaset-v1-apps">Replace Status</H2>
<P>replace status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicaset-v1-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-replicaset-v1-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-replicaset-v1-apps">Read Scale</H2>
<P>read scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-replicaset-v1-apps">Replace Scale</H2>
<P>replace scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-replicaset-v1-apps">Patch Scale</H2>
<P>partially update scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/replicasets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="replicationcontroller-v1-core">ReplicationController v1 core</H1>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#kubectl-replicationcontroller-v1-core" aria-controls="kubectl-replicationcontroller-v1-core"
aria-expanded="false">kubectl example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#curl-replicationcontroller-v1-core" aria-controls="curl-replicationcontroller-v1-core"
aria-expanded="false">curl example</BUTTON>
<DIV class="collapse" id="kubectl-replicationcontroller-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">ReplicationController Config to run 3 nginx instances.</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-yaml">
apiVersion: v1
kind: ReplicationController
metadata:
# Unique key of the ReplicationController instance
name: replicationcontroller-example
spec:
# 3 Pods should exist at all times.
replicas: 3
template:
metadata:
labels:
app: nginx
spec:
containers:
# Run the nginx image
- name: nginx
image: nginx:1.10
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="curl-replicationcontroller-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">ReplicationController Config to run 3 nginx instances.</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-yaml">
apiVersion: v1
kind: ReplicationController
metadata:
# Unique key of the ReplicationController instance
name: replicationcontroller-example
spec:
# 3 Pods should exist at all times.
replicas: 3
template:
metadata:
labels:
app: nginx
spec:
containers:
# Run the nginx image
- name: nginx
image: nginx:1.10
</CODE></PRE></DIV></DIV></DIV>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ReplicationController</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-warning col-md-8"><P><I class="fa fa-warning"></I> <B>Warning:</B></P><P>In many cases it is recommended to create a <a href="#deployment-v1beta1-apps">Deployment</a> instead of a ReplicationController.</P></DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicationcontrollerlist-v1-core">ReplicationControllerList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>If the Labels of a ReplicationController are empty, they are defaulted to be the same as the Pod(s) that the replication controller manages. Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#replicationcontrollerspec-v1-core">ReplicationControllerSpec</a></I></TD><TD>Spec defines the specification of the desired behavior of the replication controller. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#replicationcontrollerstatus-v1-core">ReplicationControllerStatus</a></I></TD><TD>Status is the most recently observed status of the replication controller. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicationcontrollerspec-v1-core">ReplicationControllerSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicationcontroller-v1-core">ReplicationController [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#what-is-a-replicationcontroller</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I>object</I></TD><TD>Selector is a label query over pods that should match the Replicas count. If Selector is empty, it is defaulted to the labels present on the Pod template. Label keys and values that must match in order to be controlled by this replication controller, if empty defaulted to labels on Pod template. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template is the object that describes the pod that will be created if insufficient replicas are detected. This takes precedence over a TemplateRef. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicationcontrollerstatus-v1-core">ReplicationControllerStatus v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicationcontroller-v1-core">ReplicationController [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>The number of available replicas (ready for at least minReadySeconds) for this replication controller.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#replicationcontrollercondition-v1-core">ReplicationControllerCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a replication controller&#39;s current state.</TD></TR>
<TR><TD><CODE>fullyLabeledReplicas</CODE><BR /><I>integer</I></TD><TD>The number of pods that have labels matching the labels of the pod template of the replication controller.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>ObservedGeneration reflects the generation of the most recently observed replication controller.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>The number of ready replicas for this replication controller.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#what-is-a-replicationcontroller</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicationcontrollerlist-v1-core">ReplicationControllerList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#replicationcontroller-v1-core">ReplicationController</a> array</I></TD><TD>List of replication controllers. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-replicationcontroller-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-replicationcontroller-v1-core">Create</H2>
<P>create a ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/replicationcontrollers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-replicationcontroller-v1-core">Patch</H2>
<P>partially update the specified ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-replicationcontroller-v1-core">Replace</H2>
<P>replace the specified ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-replicationcontroller-v1-core">Delete</H2>
<P>delete a ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-replicationcontroller-v1-core">Delete Collection</H2>
<P>delete collection of ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/replicationcontrollers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-replicationcontroller-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-replicationcontroller-v1-core">Read</H2>
<P>read the specified ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-replicationcontroller-v1-core">List</H2>
<P>list or watch objects of kind ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicationcontrollerlist-v1-core">ReplicationControllerList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-replicationcontroller-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/replicationcontrollers</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicationcontrollerlist-v1-core">ReplicationControllerList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-replicationcontroller-v1-core">Watch</H2>
<P>watch changes to an object of kind ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/replicationcontrollers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-replicationcontroller-v1-core">Watch List</H2>
<P>watch individual changes to a list of ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/replicationcontrollers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-replicationcontroller-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/replicationcontrollers</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-replicationcontroller-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-replicationcontroller-v1-core">Patch Status</H2>
<P>partially update status of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-replicationcontroller-v1-core">Read Status</H2>
<P>read status of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-replicationcontroller-v1-core">Replace Status</H2>
<P>replace status of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicationController</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicationcontroller-v1-core">ReplicationController</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-replicationcontroller-v1-core-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-replicationcontroller-v1-core">Read Scale</H2>
<P>read scale of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-replicationcontroller-v1-core">Replace Scale</H2>
<P>replace scale of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-replicationcontroller-v1-core">Patch Scale</H2>
<P>partially update scale of the specified ReplicationController</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/replicationcontrollers/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="statefulset-v1-apps">StatefulSet v1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatefulSet</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#statefulset-v1beta2-apps">v1beta2</a>
<a href="#statefulset-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetlist-v1-apps">StatefulSetList [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#statefulsetspec-v1-apps">StatefulSetSpec</a></I></TD><TD>Spec defines the desired identities of pods in this set.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#statefulsetstatus-v1-apps">StatefulSetStatus</a></I></TD><TD>Status is the current status of Pods in this StatefulSet. This data may be out of date by some window of time.</TD></TR>
</TBODY>
</TABLE>
<H3 id="statefulsetspec-v1-apps">StatefulSetSpec v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulset-v1-apps">StatefulSet [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>podManagementPolicy</CODE><BR /><I>string</I></TD><TD>podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet&#39;s revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is a label query over pods that should match the replica count. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>serviceName</CODE><BR /><I>string</I></TD><TD>serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where &#34;pod-specific-string&#34; is managed by the StatefulSet controller.</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.</TD></TR>
<TR><TD><CODE>updateStrategy</CODE><BR /><I><a href="#statefulsetupdatestrategy-v1-apps">StatefulSetUpdateStrategy</a></I></TD><TD>updateStrategy indicates the StatefulSetUpdateStrategy that will be employed to update Pods in the StatefulSet when a revision is made to Template.</TD></TR>
<TR><TD><CODE>volumeClaimTemplates</CODE><BR /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a> array</I></TD><TD>volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.</TD></TR>
</TBODY>
</TABLE>
<H3 id="statefulsetstatus-v1-apps">StatefulSetStatus v1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulset-v1-apps">StatefulSet [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#statefulsetcondition-v1-apps">StatefulSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a statefulset&#39;s current state.</TD></TR>
<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>currentReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by currentRevision.</TD></TR>
<TR><TD><CODE>currentRevision</CODE><BR /><I>string</I></TD><TD>currentRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [0,currentReplicas).</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet&#39;s generation, which is updated on mutation by the API Server.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>readyReplicas is the number of Pods created by the StatefulSet controller that have a Ready Condition.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>replicas is the number of Pods created by the StatefulSet controller.</TD></TR>
<TR><TD><CODE>updateRevision</CODE><BR /><I>string</I></TD><TD>updateRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [replicas-updatedReplicas,replicas)</TD></TR>
<TR><TD><CODE>updatedReplicas</CODE><BR /><I>integer</I></TD><TD>updatedReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by updateRevision.</TD></TR>
</TBODY>
</TABLE>
<H3 id="statefulsetlist-v1-apps">StatefulSetList v1 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#statefulset-v1-apps">StatefulSet</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-statefulset-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-statefulset-v1-apps">Create</H2>
<P>create a StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-statefulset-v1-apps">Patch</H2>
<P>partially update the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-statefulset-v1-apps">Replace</H2>
<P>replace the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-statefulset-v1-apps">Delete</H2>
<P>delete a StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-statefulset-v1-apps">Delete Collection</H2>
<P>delete collection of StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-statefulset-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-statefulset-v1-apps">Read</H2>
<P>read the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-statefulset-v1-apps">List</H2>
<P>list or watch objects of kind StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulsetlist-v1-apps">StatefulSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-statefulset-v1-apps">List All Namespaces</H2>
<P>list or watch objects of kind StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/statefulsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulsetlist-v1-apps">StatefulSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-statefulset-v1-apps">Watch</H2>
<P>watch changes to an object of kind StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-statefulset-v1-apps">Watch List</H2>
<P>watch individual changes to a list of StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-statefulset-v1-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/statefulsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-statefulset-v1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-statefulset-v1-apps">Patch Status</H2>
<P>partially update status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-statefulset-v1-apps">Read Status</H2>
<P>read status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-statefulset-v1-apps">Replace Status</H2>
<P>replace status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#statefulset-v1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-statefulset-v1-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-statefulset-v1-apps">Read Scale</H2>
<P>read scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-statefulset-v1-apps">Replace Scale</H2>
<P>replace scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-statefulset-v1-apps">Patch Scale</H2>
<P>partially update scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1-autoscaling">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="-strong-service-apis-strong-"><STRONG>Service APIs</STRONG></H1>
<H1 id="endpoints-v1-core">Endpoints v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Endpoints</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#endpointslist-v1-core">EndpointsList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>subsets</CODE><BR /><I><a href="#endpointsubset-v1-core">EndpointSubset</a> array</I></TD><TD>The set of all endpoints is the union of all subsets. Addresses are placed into subsets according to the IPs they share. A single address with multiple ports, some of which are ready and some of which are not (because they come from different containers) will result in the address being displayed in different subsets for the different ports. No address will appear in both Addresses and NotReadyAddresses in the same subset. Sets of addresses and ports that comprise a service.</TD></TR>
</TBODY>
</TABLE>
<H3 id="endpointslist-v1-core">EndpointsList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#endpoints-v1-core">Endpoints</a> array</I></TD><TD>List of endpoints.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-endpoints-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-endpoints-v1-core">Create</H2>
<P>create Endpoints</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/endpoints</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-endpoints-v1-core">Patch</H2>
<P>partially update the specified Endpoints</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/endpoints/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-endpoints-v1-core">Replace</H2>
<P>replace the specified Endpoints</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/endpoints/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-endpoints-v1-core">Delete</H2>
<P>delete Endpoints</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/endpoints/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-endpoints-v1-core">Delete Collection</H2>
<P>delete collection of Endpoints</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/endpoints</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-endpoints-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-endpoints-v1-core">Read</H2>
<P>read the specified Endpoints</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/endpoints/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpoints-v1-core">Endpoints</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-endpoints-v1-core">List</H2>
<P>list or watch objects of kind Endpoints</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/endpoints</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpointslist-v1-core">EndpointsList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-endpoints-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind Endpoints</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/endpoints</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#endpointslist-v1-core">EndpointsList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-endpoints-v1-core">Watch</H2>
<P>watch changes to an object of kind Endpoints</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/endpoints/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Endpoints</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-endpoints-v1-core">Watch List</H2>
<P>watch individual changes to a list of Endpoints</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/endpoints</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-endpoints-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Endpoints</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/endpoints</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="ingress-v1beta1-extensions">Ingress v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Ingress</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingresslist-v1beta1-extensions">IngressList [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#ingressspec-v1beta1-extensions">IngressSpec</a></I></TD><TD>Spec is the desired state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#ingressstatus-v1beta1-extensions">IngressStatus</a></I></TD><TD>Status is the current state of the Ingress. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="ingressspec-v1beta1-extensions">IngressSpec v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingress-v1beta1-extensions">Ingress [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>backend</CODE><BR /><I><a href="#ingressbackend-v1beta1-extensions">IngressBackend</a></I></TD><TD>A default backend capable of servicing requests that don&#39;t match any rule. At least one of &#39;backend&#39; or &#39;rules&#39; must be specified. This field is optional to allow the loadbalancer controller or defaulting logic to specify a global default.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#ingressrule-v1beta1-extensions">IngressRule</a> array</I></TD><TD>A list of host rules used to configure the Ingress. If unspecified, or no rule matches, all traffic is sent to the default backend.</TD></TR>
<TR><TD><CODE>tls</CODE><BR /><I><a href="#ingresstls-v1beta1-extensions">IngressTLS</a> array</I></TD><TD>TLS configuration. Currently the Ingress only supports a single TLS port, 443. If multiple members of this list specify different hosts, they will be multiplexed on the same port according to the hostname specified through the SNI TLS extension, if the ingress controller fulfilling the ingress supports SNI.</TD></TR>
</TBODY>
</TABLE>
<H3 id="ingressstatus-v1beta1-extensions">IngressStatus v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingress-v1beta1-extensions">Ingress [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>loadBalancer</CODE><BR /><I><a href="#loadbalancerstatus-v1-core">LoadBalancerStatus</a></I></TD><TD>LoadBalancer contains the current status of the load-balancer.</TD></TR>
</TBODY>
</TABLE>
<H3 id="ingresslist-v1beta1-extensions">IngressList v1beta1 extensions</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#ingress-v1beta1-extensions">Ingress</a> array</I></TD><TD>Items is the list of Ingress.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-ingress-v1beta1-extensions-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-ingress-v1beta1-extensions">Create</H2>
<P>create an Ingress</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/extensions/v1beta1/namespaces/{namespace}/ingresses</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-ingress-v1beta1-extensions">Patch</H2>
<P>partially update the specified Ingress</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-ingress-v1beta1-extensions">Replace</H2>
<P>replace the specified Ingress</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-ingress-v1beta1-extensions">Delete</H2>
<P>delete an Ingress</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-ingress-v1beta1-extensions">Delete Collection</H2>
<P>delete collection of Ingress</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/ingresses</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-ingress-v1beta1-extensions-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-ingress-v1beta1-extensions">Read</H2>
<P>read the specified Ingress</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-ingress-v1beta1-extensions">List</H2>
<P>list or watch objects of kind Ingress</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/ingresses</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingresslist-v1beta1-extensions">IngressList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-ingress-v1beta1-extensions">List All Namespaces</H2>
<P>list or watch objects of kind Ingress</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/ingresses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingresslist-v1beta1-extensions">IngressList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-ingress-v1beta1-extensions">Watch</H2>
<P>watch changes to an object of kind Ingress</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/ingresses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-ingress-v1beta1-extensions">Watch List</H2>
<P>watch individual changes to a list of Ingress</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/ingresses</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-ingress-v1beta1-extensions">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Ingress</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/ingresses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-ingress-v1beta1-extensions-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-ingress-v1beta1-extensions">Patch Status</H2>
<P>partially update status of the specified Ingress</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-ingress-v1beta1-extensions">Read Status</H2>
<P>read status of the specified Ingress</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-ingress-v1beta1-extensions">Replace Status</H2>
<P>replace status of the specified Ingress</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/ingresses/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Ingress</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#ingress-v1beta1-extensions">Ingress</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="service-v1-core">Service v1 core</H1>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#kubectl-service-v1-core" aria-controls="kubectl-service-v1-core"
aria-expanded="false">kubectl example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#curl-service-v1-core" aria-controls="curl-service-v1-core"
aria-expanded="false">curl example</BUTTON>
<DIV class="collapse" id="kubectl-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Service Config to load balance traffic across all Pods with the app=nginx label. Receives on and sends to port 80. Exposes an externally accessible endpoint.</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-yaml">
kind: Service
apiVersion: v1
metadata:
# Unique key of the Service instance
name: service-example
spec:
ports:
# Accept traffic sent to port 80
- name: http
port: 80
targetPort: 80
selector:
# Loadbalance traffic across Pods matching
# this label selector
app: nginx
# Create an HA proxy in the cloud provider
# with an External IP address - *Only supported
# by some cloud providers*
type: LoadBalancer
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="curl-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Service Config to load balance traffic across all Pods with the app=nginx label. Receives on and sends to port 80. Exposes an externally accessible endpoint.</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-yaml">
kind: Service
apiVersion: v1
metadata:
# Unique key of the Service instance
name: service-example
spec:
ports:
# Accept traffic sent to port 80
- name: http
port: 80
targetPort: 80
selector:
# Loadbalance traffic across Pods matching
# this label selector
app: nginx
# Create an HA proxy in the cloud provider
# with an External IP address - *Only supported
# by some cloud providers*
type: LoadBalancer
</CODE></PRE></DIV></DIV></DIV>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Service</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#servicelist-v1-core">ServiceList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#servicespec-v1-core">ServiceSpec</a></I></TD><TD>Spec defines the behavior of a service. https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#servicestatus-v1-core">ServiceStatus</a></I></TD><TD>Most recently observed status of the service. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="servicespec-v1-core">ServiceSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#service-v1-core">Service [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>clusterIP</CODE><BR /><I>string</I></TD><TD>clusterIP is the IP address of the service and is usually assigned randomly by the master. If an address is specified manually and is not in use by others, it will be allocated to the service; otherwise, creation of the service will fail. This field can not be changed through updates. Valid values are &#34;None&#34;, empty string (&#34;&#34;), or a valid IP address. &#34;None&#34; can be specified for headless services when proxying is not required. Only applies to types ClusterIP, NodePort, and LoadBalancer. Ignored if type is ExternalName. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies</TD></TR>
<TR><TD><CODE>externalIPs</CODE><BR /><I>string array</I></TD><TD>externalIPs is a list of IP addresses for which nodes in the cluster will also accept traffic for this service. These IPs are not managed by Kubernetes. The user is responsible for ensuring that traffic arrives at a node with this IP. A common example is external load-balancers that are not part of the Kubernetes system.</TD></TR>
<TR><TD><CODE>externalName</CODE><BR /><I>string</I></TD><TD>externalName is the external reference that kubedns or equivalent will return as a CNAME record for this service. No proxying will be involved. Must be a valid RFC-1123 hostname (https://tools.ietf.org/html/rfc1123) and requires Type to be ExternalName.</TD></TR>
<TR><TD><CODE>externalTrafficPolicy</CODE><BR /><I>string</I></TD><TD>externalTrafficPolicy denotes if this Service desires to route external traffic to node-local or cluster-wide endpoints. &#34;Local&#34; preserves the client source IP and avoids a second hop for LoadBalancer and Nodeport type services, but risks potentially imbalanced traffic spreading. &#34;Cluster&#34; obscures the client source IP and may cause a second hop to another node, but should have good overall load-spreading.</TD></TR>
<TR><TD><CODE>healthCheckNodePort</CODE><BR /><I>integer</I></TD><TD>healthCheckNodePort specifies the healthcheck nodePort for the service. If not specified, HealthCheckNodePort is created by the service api backend with the allocated nodePort. Will use user-specified nodePort value if specified by the client. Only effects when Type is set to LoadBalancer and ExternalTrafficPolicy is set to Local.</TD></TR>
<TR><TD><CODE>loadBalancerIP</CODE><BR /><I>string</I></TD><TD>Only applies to Service Type: LoadBalancer LoadBalancer will get created with the IP specified in this field. This feature depends on whether the underlying cloud-provider supports specifying the loadBalancerIP when a load balancer is created. This field will be ignored if the cloud-provider does not support the feature.</TD></TR>
<TR><TD><CODE>loadBalancerSourceRanges</CODE><BR /><I>string array</I></TD><TD>If specified and supported by the platform, this will restrict traffic through the cloud-provider load-balancer will be restricted to the specified client IPs. This field will be ignored if the cloud-provider does not support the feature.&#34; More info: https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/</TD></TR>
<TR><TD><CODE>ports</CODE><BR /><I><a href="#serviceport-v1-core">ServicePort</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>port</I></TD><TD>The list of ports that are exposed by this service. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies</TD></TR>
<TR><TD><CODE>publishNotReadyAddresses</CODE><BR /><I>boolean</I></TD><TD>publishNotReadyAddresses, when set to true, indicates that DNS implementations must publish the notReadyAddresses of subsets for the Endpoints associated with the Service. The default value is false. The primary use case for setting this field is to use a StatefulSet&#39;s Headless Service to propagate SRV records for its Pods without respect to their readiness for purpose of peer discovery.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I>object</I></TD><TD>Route service traffic to pods with label keys and values matching this selector. If empty or not present, the service is assumed to have an external process managing its endpoints, which Kubernetes will not modify. Only applies to types ClusterIP, NodePort, and LoadBalancer. Ignored if type is ExternalName. More info: https://kubernetes.io/docs/concepts/services-networking/service/</TD></TR>
<TR><TD><CODE>sessionAffinity</CODE><BR /><I>string</I></TD><TD>Supports &#34;ClientIP&#34; and &#34;None&#34;. Used to maintain session affinity. Enable client IP based session affinity. Must be ClientIP or None. Defaults to None. More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies</TD></TR>
<TR><TD><CODE>sessionAffinityConfig</CODE><BR /><I><a href="#sessionaffinityconfig-v1-core">SessionAffinityConfig</a></I></TD><TD>sessionAffinityConfig contains the configurations of session affinity.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type determines how the Service is exposed. Defaults to ClusterIP. Valid options are ExternalName, ClusterIP, NodePort, and LoadBalancer. &#34;ExternalName&#34; maps to the specified externalName. &#34;ClusterIP&#34; allocates a cluster-internal IP address for load-balancing to endpoints. Endpoints are determined by the selector or if that is not specified, by manual construction of an Endpoints object. If clusterIP is &#34;None&#34;, no virtual IP is allocated and the endpoints are published as a set of endpoints rather than a stable IP. &#34;NodePort&#34; builds on ClusterIP and allocates a port on every node which routes to the clusterIP. &#34;LoadBalancer&#34; builds on NodePort and creates an external load-balancer (if supported in the current cloud) which routes to the clusterIP. More info: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services---service-types</TD></TR>
</TBODY>
</TABLE>
<H3 id="servicestatus-v1-core">ServiceStatus v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#service-v1-core">Service [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>loadBalancer</CODE><BR /><I><a href="#loadbalancerstatus-v1-core">LoadBalancerStatus</a></I></TD><TD>LoadBalancer contains the current status of the load-balancer, if one is present.</TD></TR>
</TBODY>
</TABLE>
<H3 id="servicelist-v1-core">ServiceList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#service-v1-core">Service</a> array</I></TD><TD>List of services</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-service-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-service-v1-core">Create</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-create-service-v1-core" aria-controls="req-kubectl-create-service-v1-core"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-create-service-v1-core" aria-controls="req-curl-create-service-v1-core"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-create-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'kind: Service
apiVersion: v1
metadata:
name: service-example
spec:
ports:
- name: http
port: 80
targetPort: 80
selector:
app: nginx
type: LoadBalancer
' | kubectl create -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-create-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X POST -H 'Content-Type: application/yaml' --data '
kind: Service
apiVersion: v1
metadata:
name: service-example
spec:
ports:
- name: http
port: 80
targetPort: 80
selector:
app: nginx
type: LoadBalancer
' http://127.0.0.1:8001/api/v1/namespaces/default/services
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-create-service-v1-core" aria-controls="res-kubectl-create-service-v1-core"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-create-service-v1-core" aria-controls="res-curl-create-service-v1-core"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-create-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
service "service-example" created
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-create-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Service",
"apiVersion": "v1",
"metadata": {
"name": "service-example",
"namespace": "default",
"selfLink": "/api/v1/namespaces/default/services/service-example",
"uid": "93e5c731-9d30-11e6-9c54-42010a800148",
"resourceVersion": "2205767",
"creationTimestamp": "2016-10-28T17:04:24Z"
},
"spec": {
"ports": [
{
"name": "http",
"protocol": "TCP",
"port": 80,
"targetPort": 80,
"nodePort": 32417
}
],
"selector": {
"app": "nginx"
},
"clusterIP": "10.183.250.161",
"type": "LoadBalancer",
"sessionAffinity": "None"
},
"status": {
"loadBalancer": {}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>create a Service</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/services</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#service-v1-core">Service</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-service-v1-core">Patch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-patch-service-v1-core" aria-controls="req-kubectl-patch-service-v1-core"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-patch-service-v1-core" aria-controls="req-curl-patch-service-v1-core"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-patch-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl patch service -p \
'{"spec":{"ports":[{"name":"http","port":80,"targetPort":8080}]}}'
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-patch-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PATCH -H 'Content-Type: application/strategic-merge-patch+json' --data '
{"spec":{"ports":[{"name":"http","port":80,"targetPort":8080}]}}' \
'http://127.0.0.1:8001/api/v1/namespaces/default/services/'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-patch-service-v1-core" aria-controls="res-kubectl-patch-service-v1-core"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-patch-service-v1-core" aria-controls="res-curl-patch-service-v1-core"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-patch-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
"" patched
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-patch-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Service",
"apiVersion": "v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/api/v1/namespaces/default/services/deployment-example",
"uid": "93e5c731-9d30-11e6-9c54-42010a800148",
"resourceVersion": "2205995",
"creationTimestamp": "2016-10-28T17:04:24Z"
},
"spec": {
"ports": [
{
"name": "http",
"protocol": "TCP",
"port": 80,
"targetPort": 8080,
"nodePort": 32417
}
],
"selector": {
"app": "nginx"
},
"clusterIP": "10.183.250.161",
"type": "LoadBalancer",
"sessionAffinity": "None"
},
"status": {
"loadBalancer": {
"ingress": [
{
"ip": "104.198.186.106"
}
]
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>partially update the specified Service</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/services/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-service-v1-core">Replace</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-replace-service-v1-core" aria-controls="req-kubectl-replace-service-v1-core"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-replace-service-v1-core" aria-controls="req-curl-replace-service-v1-core"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-replace-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: v1
kind: Service
metadata:
name: deployment-example
resourceVersion: "2205995"
spec:
clusterIP: 10.183.250.161
ports:
- name: http
nodePort: 32417
port: 80
protocol: TCP
targetPort: 8080
selector:
app: nginx
sessionAffinity: None
type: LoadBalancer
' | kubectl replace -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-replace-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PUT -H 'Content-Type: application/yaml' --data '
apiVersion: v1
kind: Service
metadata:
name: deployment-example
resourceVersion: "2205995"
spec:
clusterIP: 10.183.250.161
ports:
- name: http
nodePort: 32417
port: 80
protocol: TCP
targetPort: 8080
selector:
app: nginx
sessionAffinity: None
type: LoadBalancer
' http://127.0.0.1:8001/api/v1/namespaces/default/services/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-replace-service-v1-core" aria-controls="res-kubectl-replace-service-v1-core"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-replace-service-v1-core" aria-controls="res-curl-replace-service-v1-core"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-replace-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
service "deployment-example" replaced
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-replace-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Service",
"apiVersion": "v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/api/v1/namespaces/default/services/deployment-example",
"uid": "93e5c731-9d30-11e6-9c54-42010a800148",
"resourceVersion": "2208672",
"creationTimestamp": "2016-10-28T17:04:24Z"
},
"spec": {
"ports": [
{
"name": "http",
"protocol": "TCP",
"port": 80,
"targetPort": 8080,
"nodePort": 32417
}
],
"selector": {
"app": "nginx"
},
"clusterIP": "10.183.250.161",
"type": "LoadBalancer",
"sessionAffinity": "None"
},
"status": {
"loadBalancer": {
"ingress": [
{
"ip": "104.198.186.106"
}
]
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>replace the specified Service</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/services/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#service-v1-core">Service</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-service-v1-core">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-delete-service-v1-core" aria-controls="req-kubectl-delete-service-v1-core"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-delete-service-v1-core" aria-controls="req-curl-delete-service-v1-core"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-delete-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl delete service deployment-example
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-delete-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
gracePeriodSeconds: 0
orphanDependents: false
' 'http://127.0.0.1:8001/api/v1/namespaces/default/services/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-delete-service-v1-core" aria-controls="res-kubectl-delete-service-v1-core"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-delete-service-v1-core" aria-controls="res-curl-delete-service-v1-core"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-delete-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
service "deployment-example" deleted
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-delete-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"code": 200
}
</CODE></PRE></DIV></DIV></DIV>
<P>delete a Service</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/services/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-service-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-service-v1-core">Read</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-read-service-v1-core" aria-controls="req-kubectl-read-service-v1-core"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-read-service-v1-core" aria-controls="req-curl-read-service-v1-core"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-read-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get service deployment-example -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-read-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET http://127.0.0.1:8001/api/v1/namespaces/default/services/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-read-service-v1-core" aria-controls="res-kubectl-read-service-v1-core"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-read-service-v1-core" aria-controls="res-curl-read-service-v1-core"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-read-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "Service",
"apiVersion": "v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/api/v1/namespaces/default/services/deployment-example",
"uid": "93e5c731-9d30-11e6-9c54-42010a800148",
"resourceVersion": "2205995",
"creationTimestamp": "2016-10-28T17:04:24Z"
},
"spec": {
"ports": [
{
"name": "http",
"protocol": "TCP",
"port": 80,
"targetPort": 8080,
"nodePort": 32417
}
],
"selector": {
"app": "nginx"
},
"clusterIP": "10.183.250.161",
"type": "LoadBalancer",
"sessionAffinity": "None"
},
"status": {
"loadBalancer": {
"ingress": [
{
"ip": "104.198.186.106"
}
]
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-read-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Service",
"apiVersion": "v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/api/v1/namespaces/default/services/deployment-example",
"uid": "93e5c731-9d30-11e6-9c54-42010a800148",
"resourceVersion": "2205995",
"creationTimestamp": "2016-10-28T17:04:24Z"
},
"spec": {
"ports": [
{
"name": "http",
"protocol": "TCP",
"port": 80,
"targetPort": 8080,
"nodePort": 32417
}
],
"selector": {
"app": "nginx"
},
"clusterIP": "10.183.250.161",
"type": "LoadBalancer",
"sessionAffinity": "None"
},
"status": {
"loadBalancer": {
"ingress": [
{
"ip": "104.198.186.106"
}
]
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>read the specified Service</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/services/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-service-v1-core">List</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-list-service-v1-core" aria-controls="req-kubectl-list-service-v1-core"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-list-service-v1-core" aria-controls="req-curl-list-service-v1-core"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-list-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get service -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-list-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/api/v1/namespaces/default/services'
</CODE></PRE></DIV></DIV></DIV>
<P>list or watch objects of kind Service</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/services</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#servicelist-v1-core">ServiceList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-service-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind Service</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/services</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#servicelist-v1-core">ServiceList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-service-v1-core">Watch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-watch-service-v1-core" aria-controls="req-kubectl-watch-service-v1-core"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-watch-service-v1-core" aria-controls="req-curl-watch-service-v1-core"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-watch-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get service deployment-example --watch -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-watch-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/api/v1/watch/namespaces/default/services/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-watch-service-v1-core" aria-controls="res-kubectl-watch-service-v1-core"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-watch-service-v1-core" aria-controls="res-curl-watch-service-v1-core"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-watch-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Service",
"apiVersion": "v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/api/v1/namespaces/default/services/deployment-example",
"uid": "93e5c731-9d30-11e6-9c54-42010a800148",
"resourceVersion": "2205995",
"creationTimestamp": "2016-10-28T17:04:24Z"
},
"spec": {
"ports": [
{
"name": "http",
"protocol": "TCP",
"port": 80,
"targetPort": 8080,
"nodePort": 32417
}
],
"selector": {
"app": "nginx"
},
"clusterIP": "10.183.250.161",
"type": "LoadBalancer",
"sessionAffinity": "None"
},
"status": {
"loadBalancer": {
"ingress": [
{
"ip": "104.198.186.106"
}
]
}
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-watch-service-v1-core">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Service",
"apiVersion": "v1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/api/v1/namespaces/default/services/deployment-example",
"uid": "93e5c731-9d30-11e6-9c54-42010a800148",
"resourceVersion": "2205995",
"creationTimestamp": "2016-10-28T17:04:24Z"
},
"spec": {
"ports": [
{
"name": "http",
"protocol": "TCP",
"port": 80,
"targetPort": 8080,
"nodePort": 32417
}
],
"selector": {
"app": "nginx"
},
"clusterIP": "10.183.250.161",
"type": "LoadBalancer",
"sessionAffinity": "None"
},
"status": {
"loadBalancer": {
"ingress": [
{
"ip": "104.198.186.106"
}
]
}
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>watch changes to an object of kind Service</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/services/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-service-v1-core">Watch List</H2>
<P>watch individual changes to a list of Service</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/services</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-service-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Service</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/services</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-service-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-service-v1-core">Patch Status</H2>
<P>partially update status of the specified Service</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/services/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-service-v1-core">Read Status</H2>
<P>read status of the specified Service</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/services/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-service-v1-core">Replace Status</H2>
<P>replace status of the specified Service</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/services/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#service-v1-core">Service</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#service-v1-core">Service</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-proxy-operations-service-v1-core-strong-"><STRONG>Proxy Operations</STRONG></H2>
<H2 id="create-connect-proxy-service-v1-core">Create Connect Proxy</H2>
<P>connect POST requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="create-connect-proxy-path-service-v1-core">Create Connect Proxy Path</H2>
<P>connect POST requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-connect-proxy-service-v1-core">Delete Connect Proxy</H2>
<P>connect DELETE requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-connect-proxy-path-service-v1-core">Delete Connect Proxy Path</H2>
<P>connect DELETE requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="get-connect-proxy-service-v1-core">Get Connect Proxy</H2>
<P>connect GET requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="get-connect-proxy-path-service-v1-core">Get Connect Proxy Path</H2>
<P>connect GET requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="head-connect-proxy-service-v1-core">Head Connect Proxy</H2>
<P>connect HEAD requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>HEAD /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="head-connect-proxy-path-service-v1-core">Head Connect Proxy Path</H2>
<P>connect HEAD requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>HEAD /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-connect-proxy-service-v1-core">Replace Connect Proxy</H2>
<P>connect PUT requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/services/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-connect-proxy-path-service-v1-core">Replace Connect Proxy Path</H2>
<P>connect PUT requests to proxy of Service</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/services/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Service</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the part of URLs that include service endpoints, suffixes, and parameters to use for the current proxy request to service. For example, the whole request URL is http://localhost/api/v1/namespaces/kube-system/services/elasticsearch-logging/_search?q=user:kimchy. Path is _search?q=user:kimchy.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="-strong-config-and-storage-apis-strong-"><STRONG>Config and Storage APIs</STRONG></H1>
<H1 id="configmap-v1-core">ConfigMap v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMap</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#configmaplist-v1-core">ConfigMapList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>binaryData</CODE><BR /><I>object</I></TD><TD>BinaryData contains the binary data. Each key must consist of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;. BinaryData can contain byte sequences that are not in the UTF-8 range. The keys stored in BinaryData must not overlap with the ones in the Data field, this is enforced during validation process. Using this field will require 1.10+ apiserver and kubelet.</TD></TR>
<TR><TD><CODE>data</CODE><BR /><I>object</I></TD><TD>Data contains the configuration data. Each key must consist of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;. Values with non-UTF-8 byte sequences must use the BinaryData field. The keys stored in Data must not overlap with the keys in the BinaryData field, this is enforced during validation process.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H3 id="configmaplist-v1-core">ConfigMapList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#configmap-v1-core">ConfigMap</a> array</I></TD><TD>Items is the list of ConfigMaps.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-configmap-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-configmap-v1-core">Create</H2>
<P>create a ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/configmaps</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-configmap-v1-core">Patch</H2>
<P>partially update the specified ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/configmaps/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-configmap-v1-core">Replace</H2>
<P>replace the specified ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/configmaps/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-configmap-v1-core">Delete</H2>
<P>delete a ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/configmaps/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-configmap-v1-core">Delete Collection</H2>
<P>delete collection of ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/configmaps</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-configmap-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-configmap-v1-core">Read</H2>
<P>read the specified ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/configmaps/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#configmap-v1-core">ConfigMap</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-configmap-v1-core">List</H2>
<P>list or watch objects of kind ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/configmaps</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#configmaplist-v1-core">ConfigMapList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-configmap-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/configmaps</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#configmaplist-v1-core">ConfigMapList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-configmap-v1-core">Watch</H2>
<P>watch changes to an object of kind ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/configmaps/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ConfigMap</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-configmap-v1-core">Watch List</H2>
<P>watch individual changes to a list of ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/configmaps</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-configmap-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ConfigMap</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/configmaps</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="secret-v1-core">Secret v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Secret</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#secretlist-v1-core">SecretList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>data</CODE><BR /><I>object</I></TD><TD>Data contains the secret data. Each key must consist of alphanumeric characters, &#39;-&#39;, &#39;_&#39; or &#39;.&#39;. The serialized form of the secret data is a base64 encoded string, representing the arbitrary (possibly non-string) data value here. Described in https://tools.ietf.org/html/rfc4648#section-4</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>stringData</CODE><BR /><I>object</I></TD><TD>stringData allows specifying non-binary secret data in string form. It is provided as a write-only convenience method. All keys and values are merged into the data field on write, overwriting any existing values. It is never output when reading from the API.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Used to facilitate programmatic handling of secret data.</TD></TR>
</TBODY>
</TABLE>
<H3 id="secretlist-v1-core">SecretList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#secret-v1-core">Secret</a> array</I></TD><TD>Items is a list of secret objects. More info: https://kubernetes.io/docs/concepts/configuration/secret</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-secret-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-secret-v1-core">Create</H2>
<P>create a Secret</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/secrets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-secret-v1-core">Patch</H2>
<P>partially update the specified Secret</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/secrets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-secret-v1-core">Replace</H2>
<P>replace the specified Secret</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/secrets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-secret-v1-core">Delete</H2>
<P>delete a Secret</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/secrets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-secret-v1-core">Delete Collection</H2>
<P>delete collection of Secret</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/secrets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-secret-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-secret-v1-core">Read</H2>
<P>read the specified Secret</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/secrets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#secret-v1-core">Secret</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-secret-v1-core">List</H2>
<P>list or watch objects of kind Secret</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/secrets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#secretlist-v1-core">SecretList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-secret-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind Secret</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/secrets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#secretlist-v1-core">SecretList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-secret-v1-core">Watch</H2>
<P>watch changes to an object of kind Secret</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/secrets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Secret</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-secret-v1-core">Watch List</H2>
<P>watch individual changes to a list of Secret</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/secrets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-secret-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Secret</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/secrets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="persistentvolumeclaim-v1-core">PersistentVolumeClaim v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PersistentVolumeClaim</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-bullhorn"></I> A <a href="#persistentvolume-v1-core">PersistentVolume</a> must be allocated in the cluster to use this.</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList [core/v1]</a></LI>
<LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
<LI><a href="#statefulsetspec-v1beta2-apps">StatefulSetSpec [apps/v1beta2]</a></LI>
<LI><a href="#statefulsetspec-v1beta1-apps">StatefulSetSpec [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec</a></I></TD><TD>Spec defines the desired characteristics of a volume requested by a pod author. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#persistentvolumeclaimstatus-v1-core">PersistentVolumeClaimStatus</a></I></TD><TD>Status represents the current information/status of a persistent volume claim. Read-only. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
</TBODY>
</TABLE>
<H3 id="persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>accessModes</CODE><BR /><I>string array</I></TD><TD>AccessModes contains the desired access modes the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I><a href="#resourcerequirements-v1-core">ResourceRequirements</a></I></TD><TD>Resources represents the minimum resources the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over volumes to consider for binding.</TD></TR>
<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>Name of the StorageClass required by the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1</TD></TR>
<TR><TD><CODE>volumeMode</CODE><BR /><I>string</I></TD><TD>volumeMode defines what type of volume is required by the claim. Value of Filesystem is implied when not included in claim spec. This is an alpha feature and may change in the future.</TD></TR>
<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>VolumeName is the binding reference to the PersistentVolume backing this claim.</TD></TR>
</TBODY>
</TABLE>
<H3 id="persistentvolumeclaimstatus-v1-core">PersistentVolumeClaimStatus v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>accessModes</CODE><BR /><I>string array</I></TD><TD>AccessModes contains the actual access modes the volume backing the PVC has. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes-1</TD></TR>
<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>Represents the actual resources of the underlying volume.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#persistentvolumeclaimcondition-v1-core">PersistentVolumeClaimCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Current Condition of persistent volume claim. If underlying persistent volume is being resized then the Condition will be set to &#39;ResizeStarted&#39;.</TD></TR>
<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>Phase represents the current phase of PersistentVolumeClaim.</TD></TR>
</TBODY>
</TABLE>
<H3 id="persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a> array</I></TD><TD>A list of persistent volume claims. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-persistentvolumeclaim-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-persistentvolumeclaim-v1-core">Create</H2>
<P>create a PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/persistentvolumeclaims</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-persistentvolumeclaim-v1-core">Patch</H2>
<P>partially update the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-persistentvolumeclaim-v1-core">Replace</H2>
<P>replace the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-persistentvolumeclaim-v1-core">Delete</H2>
<P>delete a PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-persistentvolumeclaim-v1-core">Delete Collection</H2>
<P>delete collection of PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/persistentvolumeclaims</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-persistentvolumeclaim-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-persistentvolumeclaim-v1-core">Read</H2>
<P>read the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-persistentvolumeclaim-v1-core">List</H2>
<P>list or watch objects of kind PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/persistentvolumeclaims</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-persistentvolumeclaim-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/persistentvolumeclaims</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-persistentvolumeclaim-v1-core">Watch</H2>
<P>watch changes to an object of kind PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/persistentvolumeclaims/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-persistentvolumeclaim-v1-core">Watch List</H2>
<P>watch individual changes to a list of PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/persistentvolumeclaims</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-persistentvolumeclaim-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/persistentvolumeclaims</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-persistentvolumeclaim-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-persistentvolumeclaim-v1-core">Patch Status</H2>
<P>partially update status of the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-persistentvolumeclaim-v1-core">Read Status</H2>
<P>read status of the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-persistentvolumeclaim-v1-core">Replace Status</H2>
<P>replace status of the specified PersistentVolumeClaim</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolumeClaim</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="storageclass-v1-storage-k8s-io">StorageClass v1 storage.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StorageClass</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#storageclass-v1beta1-storage-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageclasslist-v1-storage-k8s-io">StorageClassList [storage/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowVolumeExpansion</CODE><BR /><I>boolean</I></TD><TD>AllowVolumeExpansion shows whether the storage class allow volume expand</TD></TR>
<TR><TD><CODE>allowedTopologies</CODE><BR /><I><a href="#topologyselectorterm-v1-core">TopologySelectorTerm</a> array</I></TD><TD>Restrict the node topologies where volumes can be dynamically provisioned. Each volume plugin defines its own supported topology specifications. An empty TopologySelectorTerm list means there is no topology restriction. This field is alpha-level and is only honored by servers that enable the DynamicProvisioningScheduling feature.</TD></TR>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>mountOptions</CODE><BR /><I>string array</I></TD><TD>Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. [&#34;ro&#34;, &#34;soft&#34;]. Not validated - mount of the PVs will simply fail if one is invalid.</TD></TR>
<TR><TD><CODE>parameters</CODE><BR /><I>object</I></TD><TD>Parameters holds the parameters for the provisioner that should create volumes of this storage class.</TD></TR>
<TR><TD><CODE>provisioner</CODE><BR /><I>string</I></TD><TD>Provisioner indicates the type of the provisioner.</TD></TR>
<TR><TD><CODE>reclaimPolicy</CODE><BR /><I>string</I></TD><TD>Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.</TD></TR>
<TR><TD><CODE>volumeBindingMode</CODE><BR /><I>string</I></TD><TD>VolumeBindingMode indicates how PersistentVolumeClaims should be provisioned and bound. When unset, VolumeBindingImmediate is used. This field is alpha-level and is only honored by servers that enable the VolumeScheduling feature.</TD></TR>
</TBODY>
</TABLE>
<H3 id="storageclasslist-v1-storage-k8s-io">StorageClassList v1 storage</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a> array</I></TD><TD>Items is the list of StorageClasses</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-storageclass-v1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-storageclass-v1-storage-k8s-io">Create</H2>
<P>create a StorageClass</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/storage.k8s.io/v1/storageclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-storageclass-v1-storage-k8s-io">Patch</H2>
<P>partially update the specified StorageClass</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/storage.k8s.io/v1/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-storageclass-v1-storage-k8s-io">Replace</H2>
<P>replace the specified StorageClass</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/storage.k8s.io/v1/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-storageclass-v1-storage-k8s-io">Delete</H2>
<P>delete a StorageClass</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/storage.k8s.io/v1/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-storageclass-v1-storage-k8s-io">Delete Collection</H2>
<P>delete collection of StorageClass</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/storage.k8s.io/v1/storageclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-storageclass-v1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-storageclass-v1-storage-k8s-io">Read</H2>
<P>read the specified StorageClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageclass-v1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-storageclass-v1-storage-k8s-io">List</H2>
<P>list or watch objects of kind StorageClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1/storageclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageclasslist-v1-storage-k8s-io">StorageClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-storageclass-v1-storage-k8s-io">Watch</H2>
<P>watch changes to an object of kind StorageClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1/watch/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-storageclass-v1-storage-k8s-io">Watch List</H2>
<P>watch individual changes to a list of StorageClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1/watch/storageclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="volume-v1-core">Volume v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Volume</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podpresetspec-v1alpha1-settings-k8s-io">PodPresetSpec [settings/v1alpha1]</a></LI>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>awsElasticBlockStore</CODE><BR /><I><a href="#awselasticblockstorevolumesource-v1-core">AWSElasticBlockStoreVolumeSource</a></I></TD><TD>AWSElasticBlockStore represents an AWS Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
<TR><TD><CODE>azureDisk</CODE><BR /><I><a href="#azurediskvolumesource-v1-core">AzureDiskVolumeSource</a></I></TD><TD>AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.</TD></TR>
<TR><TD><CODE>azureFile</CODE><BR /><I><a href="#azurefilevolumesource-v1-core">AzureFileVolumeSource</a></I></TD><TD>AzureFile represents an Azure File Service mount on the host and bind mount to the pod.</TD></TR>
<TR><TD><CODE>cephfs</CODE><BR /><I><a href="#cephfsvolumesource-v1-core">CephFSVolumeSource</a></I></TD><TD>CephFS represents a Ceph FS mount on the host that shares a pod&#39;s lifetime</TD></TR>
<TR><TD><CODE>cinder</CODE><BR /><I><a href="#cindervolumesource-v1-core">CinderVolumeSource</a></I></TD><TD>Cinder represents a cinder volume attached and mounted on kubelets host machine More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>configMap</CODE><BR /><I><a href="#configmapvolumesource-v1-core">ConfigMapVolumeSource</a></I></TD><TD>ConfigMap represents a configMap that should populate this volume</TD></TR>
<TR><TD><CODE>downwardAPI</CODE><BR /><I><a href="#downwardapivolumesource-v1-core">DownwardAPIVolumeSource</a></I></TD><TD>DownwardAPI represents downward API about the pod that should populate this volume</TD></TR>
<TR><TD><CODE>emptyDir</CODE><BR /><I><a href="#emptydirvolumesource-v1-core">EmptyDirVolumeSource</a></I></TD><TD>EmptyDir represents a temporary directory that shares a pod&#39;s lifetime. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir</TD></TR>
<TR><TD><CODE>fc</CODE><BR /><I><a href="#fcvolumesource-v1-core">FCVolumeSource</a></I></TD><TD>FC represents a Fibre Channel resource that is attached to a kubelet&#39;s host machine and then exposed to the pod.</TD></TR>
<TR><TD><CODE>flexVolume</CODE><BR /><I><a href="#flexvolumesource-v1-core">FlexVolumeSource</a></I></TD><TD>FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.</TD></TR>
<TR><TD><CODE>flocker</CODE><BR /><I><a href="#flockervolumesource-v1-core">FlockerVolumeSource</a></I></TD><TD>Flocker represents a Flocker volume attached to a kubelet&#39;s host machine. This depends on the Flocker control service being running</TD></TR>
<TR><TD><CODE>gcePersistentDisk</CODE><BR /><I><a href="#gcepersistentdiskvolumesource-v1-core">GCEPersistentDiskVolumeSource</a></I></TD><TD>GCEPersistentDisk represents a GCE Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
<TR><TD><CODE>gitRepo</CODE><BR /><I><a href="#gitrepovolumesource-v1-core">GitRepoVolumeSource</a></I></TD><TD>GitRepo represents a git repository at a particular revision. DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod&#39;s container.</TD></TR>
<TR><TD><CODE>glusterfs</CODE><BR /><I><a href="#glusterfsvolumesource-v1-core">GlusterfsVolumeSource</a></I></TD><TD>Glusterfs represents a Glusterfs mount on the host that shares a pod&#39;s lifetime. More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md</TD></TR>
<TR><TD><CODE>hostPath</CODE><BR /><I><a href="#hostpathvolumesource-v1-core">HostPathVolumeSource</a></I></TD><TD>HostPath represents a pre-existing file or directory on the host machine that is directly exposed to the container. This is generally used for system agents or other privileged things that are allowed to see the host machine. Most containers will NOT need this. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath</TD></TR>
<TR><TD><CODE>iscsi</CODE><BR /><I><a href="#iscsivolumesource-v1-core">ISCSIVolumeSource</a></I></TD><TD>ISCSI represents an ISCSI Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://releases.k8s.io/HEAD/examples/volumes/iscsi/README.md</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Volume&#39;s name. Must be a DNS_LABEL and unique within the pod. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
<TR><TD><CODE>nfs</CODE><BR /><I><a href="#nfsvolumesource-v1-core">NFSVolumeSource</a></I></TD><TD>NFS represents an NFS mount on the host that shares a pod&#39;s lifetime More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
<TR><TD><CODE>persistentVolumeClaim</CODE><BR /><I><a href="#persistentvolumeclaimvolumesource-v1-core">PersistentVolumeClaimVolumeSource</a></I></TD><TD>PersistentVolumeClaimVolumeSource represents a reference to a PersistentVolumeClaim in the same namespace. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
<TR><TD><CODE>photonPersistentDisk</CODE><BR /><I><a href="#photonpersistentdiskvolumesource-v1-core">PhotonPersistentDiskVolumeSource</a></I></TD><TD>PhotonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine</TD></TR>
<TR><TD><CODE>portworxVolume</CODE><BR /><I><a href="#portworxvolumesource-v1-core">PortworxVolumeSource</a></I></TD><TD>PortworxVolume represents a portworx volume attached and mounted on kubelets host machine</TD></TR>
<TR><TD><CODE>projected</CODE><BR /><I><a href="#projectedvolumesource-v1-core">ProjectedVolumeSource</a></I></TD><TD>Items for all in one resources secrets, configmaps, and downward API</TD></TR>
<TR><TD><CODE>quobyte</CODE><BR /><I><a href="#quobytevolumesource-v1-core">QuobyteVolumeSource</a></I></TD><TD>Quobyte represents a Quobyte mount on the host that shares a pod&#39;s lifetime</TD></TR>
<TR><TD><CODE>rbd</CODE><BR /><I><a href="#rbdvolumesource-v1-core">RBDVolumeSource</a></I></TD><TD>RBD represents a Rados Block Device mount on the host that shares a pod&#39;s lifetime. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md</TD></TR>
<TR><TD><CODE>scaleIO</CODE><BR /><I><a href="#scaleiovolumesource-v1-core">ScaleIOVolumeSource</a></I></TD><TD>ScaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.</TD></TR>
<TR><TD><CODE>secret</CODE><BR /><I><a href="#secretvolumesource-v1-core">SecretVolumeSource</a></I></TD><TD>Secret represents a secret that should populate this volume. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret</TD></TR>
<TR><TD><CODE>storageos</CODE><BR /><I><a href="#storageosvolumesource-v1-core">StorageOSVolumeSource</a></I></TD><TD>StorageOS represents a StorageOS volume attached and mounted on Kubernetes nodes.</TD></TR>
<TR><TD><CODE>vsphereVolume</CODE><BR /><I><a href="#vspherevirtualdiskvolumesource-v1-core">VsphereVirtualDiskVolumeSource</a></I></TD><TD>VsphereVolume represents a vSphere volume attached and mounted on kubelets host machine</TD></TR>
</TBODY>
</TABLE>
<H1 id="volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment v1beta1 storage.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>VolumeAttachment</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#volumeattachment-v1alpha1-storage-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachmentlist-v1beta1-storage-k8s-io">VolumeAttachmentList [storage/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#volumeattachmentspec-v1beta1-storage-k8s-io">VolumeAttachmentSpec</a></I></TD><TD>Specification of the desired attach/detach volume behavior. Populated by the Kubernetes system.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#volumeattachmentstatus-v1beta1-storage-k8s-io">VolumeAttachmentStatus</a></I></TD><TD>Status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher.</TD></TR>
</TBODY>
</TABLE>
<H3 id="volumeattachmentspec-v1beta1-storage-k8s-io">VolumeAttachmentSpec v1beta1 storage</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment [storage/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>attacher</CODE><BR /><I>string</I></TD><TD>Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().</TD></TR>
<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>The node that the volume should be attached to.</TD></TR>
<TR><TD><CODE>source</CODE><BR /><I><a href="#volumeattachmentsource-v1beta1-storage-k8s-io">VolumeAttachmentSource</a></I></TD><TD>Source represents the volume that should be attached.</TD></TR>
</TBODY>
</TABLE>
<H3 id="volumeattachmentstatus-v1beta1-storage-k8s-io">VolumeAttachmentStatus v1beta1 storage</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment [storage/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>attachError</CODE><BR /><I><a href="#volumeerror-v1beta1-storage-k8s-io">VolumeError</a></I></TD><TD>The last error encountered during attach operation, if any. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.</TD></TR>
<TR><TD><CODE>attached</CODE><BR /><I>boolean</I></TD><TD>Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.</TD></TR>
<TR><TD><CODE>attachmentMetadata</CODE><BR /><I>object</I></TD><TD>Upon successful attach, this field is populated with any information returned by the attach operation that must be passed into subsequent WaitForAttach or Mount calls. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.</TD></TR>
<TR><TD><CODE>detachError</CODE><BR /><I><a href="#volumeerror-v1beta1-storage-k8s-io">VolumeError</a></I></TD><TD>The last error encountered during detach operation, if any. This field must only be set by the entity completing the detach operation, i.e. the external-attacher.</TD></TR>
</TBODY>
</TABLE>
<H3 id="volumeattachmentlist-v1beta1-storage-k8s-io">VolumeAttachmentList v1beta1 storage</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a> array</I></TD><TD>Items is the list of VolumeAttachments</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-volumeattachment-v1beta1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-volumeattachment-v1beta1-storage-k8s-io">Create</H2>
<P>create a VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/storage.k8s.io/v1beta1/volumeattachments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-volumeattachment-v1beta1-storage-k8s-io">Patch</H2>
<P>partially update the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/storage.k8s.io/v1beta1/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-volumeattachment-v1beta1-storage-k8s-io">Replace</H2>
<P>replace the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/storage.k8s.io/v1beta1/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-volumeattachment-v1beta1-storage-k8s-io">Delete</H2>
<P>delete a VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/storage.k8s.io/v1beta1/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-volumeattachment-v1beta1-storage-k8s-io">Delete Collection</H2>
<P>delete collection of VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/storage.k8s.io/v1beta1/volumeattachments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-volumeattachment-v1beta1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-volumeattachment-v1beta1-storage-k8s-io">Read</H2>
<P>read the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1beta1/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-volumeattachment-v1beta1-storage-k8s-io">List</H2>
<P>list or watch objects of kind VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1beta1/volumeattachments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachmentlist-v1beta1-storage-k8s-io">VolumeAttachmentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-volumeattachment-v1beta1-storage-k8s-io">Watch</H2>
<P>watch changes to an object of kind VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1beta1/watch/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-volumeattachment-v1beta1-storage-k8s-io">Watch List</H2>
<P>watch individual changes to a list of VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1beta1/watch/volumeattachments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="-strong-metadata-apis-strong-"><STRONG>Metadata APIs</STRONG></H1>
<H1 id="controllerrevision-v1-apps">ControllerRevision v1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ControllerRevision</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#controllerrevision-v1beta2-apps">v1beta2</a>
<a href="#controllerrevision-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#controllerrevisionlist-v1-apps">ControllerRevisionList [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>data</CODE></TD><TD>Data is the serialized representation of the state.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>revision</CODE><BR /><I>integer</I></TD><TD>Revision indicates the revision of the state represented by Data.</TD></TR>
</TBODY>
</TABLE>
<H3 id="controllerrevisionlist-v1-apps">ControllerRevisionList v1 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a> array</I></TD><TD>Items is the list of ControllerRevisions</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-controllerrevision-v1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-controllerrevision-v1-apps">Create</H2>
<P>create a ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-controllerrevision-v1-apps">Patch</H2>
<P>partially update the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-controllerrevision-v1-apps">Replace</H2>
<P>replace the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-controllerrevision-v1-apps">Delete</H2>
<P>delete a ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-controllerrevision-v1-apps">Delete Collection</H2>
<P>delete collection of ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-controllerrevision-v1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-controllerrevision-v1-apps">Read</H2>
<P>read the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-controllerrevision-v1-apps">List</H2>
<P>list or watch objects of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevisionlist-v1-apps">ControllerRevisionList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-controllerrevision-v1-apps">List All Namespaces</H2>
<P>list or watch objects of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/controllerrevisions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevisionlist-v1-apps">ControllerRevisionList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-controllerrevision-v1-apps">Watch</H2>
<P>watch changes to an object of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-controllerrevision-v1-apps">Watch List</H2>
<P>watch individual changes to a list of ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-controllerrevision-v1-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1/watch/controllerrevisions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition v1beta1 apiextensions.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CustomResourceDefinition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionlist-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionList [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#customresourcedefinitionspec-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionSpec</a></I></TD><TD>Spec describes how the user wants the resources to appear</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#customresourcedefinitionstatus-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionStatus</a></I></TD><TD>Status indicates the actual state of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<H3 id="customresourcedefinitionspec-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionSpec v1beta1 apiextensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>additionalPrinterColumns</CODE><BR /><I><a href="#customresourcecolumndefinition-v1beta1-apiextensions-k8s-io">CustomResourceColumnDefinition</a> array</I></TD><TD>AdditionalPrinterColumns are additional columns shown e.g. in kubectl next to the name. Defaults to a created-at column.</TD></TR>
<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>Group is the group this resource belongs in</TD></TR>
<TR><TD><CODE>names</CODE><BR /><I><a href="#customresourcedefinitionnames-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionNames</a></I></TD><TD>Names are the names used to describe this custom resource</TD></TR>
<TR><TD><CODE>scope</CODE><BR /><I>string</I></TD><TD>Scope indicates whether this resource is cluster or namespace scoped. Default is namespaced</TD></TR>
<TR><TD><CODE>subresources</CODE><BR /><I><a href="#customresourcesubresources-v1beta1-apiextensions-k8s-io">CustomResourceSubresources</a></I></TD><TD>Subresources describes the subresources for CustomResources</TD></TR>
<TR><TD><CODE>validation</CODE><BR /><I><a href="#customresourcevalidation-v1beta1-apiextensions-k8s-io">CustomResourceValidation</a></I></TD><TD>Validation describes the validation methods for CustomResources</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>Version is the version this resource belongs in Should be always first item in Versions field if provided. Optional, but at least one of Version or Versions must be set. Deprecated: Please use `Versions`.</TD></TR>
<TR><TD><CODE>versions</CODE><BR /><I><a href="#customresourcedefinitionversion-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionVersion</a> array</I></TD><TD>Versions is the list of all supported versions for this resource. If Version field is provided, this field is optional. Validation: All versions must use the same validation schema for now. i.e., top level Validation field is applied to all of these versions. Order: The version name will be used to compute the order. If the version string is &#34;kube-like&#34;, it will sort above non &#34;kube-like&#34; version strings, which are ordered lexicographically. &#34;Kube-like&#34; versions start with a &#34;v&#34;, then are followed by a number (the major version), then optionally the string &#34;alpha&#34; or &#34;beta&#34; and another number (the minor version). These are sorted first by GA &gt; beta &gt; alpha (where GA is a version with no suffix such as beta or alpha), and then by comparing major version, then minor version. An example sorted list of versions: v10, v2, v1, v11beta2, v10beta3, v3beta1, v12alpha1, v11alpha2, foo1, foo10.</TD></TR>
</TBODY>
</TABLE>
<H3 id="customresourcedefinitionstatus-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionStatus v1beta1 apiextensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>acceptedNames</CODE><BR /><I><a href="#customresourcedefinitionnames-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionNames</a></I></TD><TD>AcceptedNames are the names that are actually being used to serve discovery They may be different than the names in spec.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#customresourcedefinitioncondition-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionCondition</a> array</I></TD><TD>Conditions indicate state for particular aspects of a CustomResourceDefinition</TD></TR>
<TR><TD><CODE>storedVersions</CODE><BR /><I>string array</I></TD><TD>StoredVersions are all versions of CustomResources that were ever persisted. Tracking these versions allows a migration path for stored versions in etcd. The field is mutable so the migration controller can first finish a migration to another version (i.e. that no old objects are left in the storage), and then remove the rest of the versions from this list. None of the versions in this list can be removed from the spec.Versions field.</TD></TR>
</TBODY>
</TABLE>
<H3 id="customresourcedefinitionlist-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionList v1beta1 apiextensions</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a> array</I></TD><TD>Items individual CustomResourceDefinitions</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-customresourcedefinition-v1beta1-apiextensions-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-customresourcedefinition-v1beta1-apiextensions-k8s-io">Create</H2>
<P>create a CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-customresourcedefinition-v1beta1-apiextensions-k8s-io">Patch</H2>
<P>partially update the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-customresourcedefinition-v1beta1-apiextensions-k8s-io">Replace</H2>
<P>replace the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-customresourcedefinition-v1beta1-apiextensions-k8s-io">Delete</H2>
<P>delete a CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-customresourcedefinition-v1beta1-apiextensions-k8s-io">Delete Collection</H2>
<P>delete collection of CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-customresourcedefinition-v1beta1-apiextensions-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-customresourcedefinition-v1beta1-apiextensions-k8s-io">Read</H2>
<P>read the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-customresourcedefinition-v1beta1-apiextensions-k8s-io">List</H2>
<P>list or watch objects of kind CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#customresourcedefinitionlist-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-customresourcedefinition-v1beta1-apiextensions-k8s-io">Watch</H2>
<P>watch changes to an object of kind CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiextensions.k8s.io/v1beta1/watch/customresourcedefinitions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-customresourcedefinition-v1beta1-apiextensions-k8s-io">Watch List</H2>
<P>watch individual changes to a list of CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiextensions.k8s.io/v1beta1/watch/customresourcedefinitions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-customresourcedefinition-v1beta1-apiextensions-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-customresourcedefinition-v1beta1-apiextensions-k8s-io">Patch Status</H2>
<P>partially update status of the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-customresourcedefinition-v1beta1-apiextensions-k8s-io">Read Status</H2>
<P>read status of the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-customresourcedefinition-v1beta1-apiextensions-k8s-io">Replace Status</H2>
<P>replace status of the specified CustomResourceDefinition</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CustomResourceDefinition</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="event-v1-core">Event v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Event</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#event-v1beta1-events-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#eventlist-v1-core">EventList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>action</CODE><BR /><I>string</I></TD><TD>What action was taken/failed regarding to the Regarding object.</TD></TR>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>The number of times this event has occurred.</TD></TR>
<TR><TD><CODE>eventTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>Time when this Event was first observed.</TD></TR>
<TR><TD><CODE>firstTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The time at which the event was first recorded. (Time of server receipt is in TypeMeta.)</TD></TR>
<TR><TD><CODE>involvedObject</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>The object that this event is about.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>lastTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The time at which the most recent occurrence of this event was recorded.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human-readable description of the status of this operation.</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>This should be a short, machine understandable string that gives the reason for the transition into the object&#39;s current status.</TD></TR>
<TR><TD><CODE>related</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>Optional secondary object for more complex actions.</TD></TR>
<TR><TD><CODE>reportingComponent</CODE><BR /><I>string</I></TD><TD>Name of the controller that emitted this Event, e.g. `kubernetes.io/kubelet`.</TD></TR>
<TR><TD><CODE>reportingInstance</CODE><BR /><I>string</I></TD><TD>ID of the controller instance, e.g. `kubelet-xyzf`.</TD></TR>
<TR><TD><CODE>series</CODE><BR /><I><a href="#eventseries-v1-core">EventSeries</a></I></TD><TD>Data about the Event series this event represents or nil if it&#39;s a singleton Event.</TD></TR>
<TR><TD><CODE>source</CODE><BR /><I><a href="#eventsource-v1-core">EventSource</a></I></TD><TD>The component reporting this event. Should be a short machine understandable string.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of this event (Normal, Warning), new types could be added in the future</TD></TR>
</TBODY>
</TABLE>
<H3 id="eventlist-v1-core">EventList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#event-v1-core">Event</a> array</I></TD><TD>List of events</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-event-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-event-v1-core">Create</H2>
<P>create an Event</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/events</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1-core">Event</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-event-v1-core">Patch</H2>
<P>partially update the specified Event</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-event-v1-core">Replace</H2>
<P>replace the specified Event</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1-core">Event</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-event-v1-core">Delete</H2>
<P>delete an Event</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-event-v1-core">Delete Collection</H2>
<P>delete collection of Event</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/events</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-event-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-event-v1-core">Read</H2>
<P>read the specified Event</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#event-v1-core">Event</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-event-v1-core">List</H2>
<P>list or watch objects of kind Event</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/events</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#eventlist-v1-core">EventList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-event-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind Event</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/events</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#eventlist-v1-core">EventList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-event-v1-core">Watch</H2>
<P>watch changes to an object of kind Event</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-event-v1-core">Watch List</H2>
<P>watch individual changes to a list of Event</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/events</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-event-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Event</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/events</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="limitrange-v1-core">LimitRange v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LimitRange</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#limitrangelist-v1-core">LimitRangeList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#limitrangespec-v1-core">LimitRangeSpec</a></I></TD><TD>Spec defines the limits enforced. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="limitrangespec-v1-core">LimitRangeSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#limitrange-v1-core">LimitRange [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>limits</CODE><BR /><I><a href="#limitrangeitem-v1-core">LimitRangeItem</a> array</I></TD><TD>Limits is the list of LimitRangeItem objects that are enforced.</TD></TR>
</TBODY>
</TABLE>
<H3 id="limitrangelist-v1-core">LimitRangeList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#limitrange-v1-core">LimitRange</a> array</I></TD><TD>Items is a list of LimitRange objects. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-limitrange-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-limitrange-v1-core">Create</H2>
<P>create a LimitRange</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/limitranges</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-limitrange-v1-core">Patch</H2>
<P>partially update the specified LimitRange</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/limitranges/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-limitrange-v1-core">Replace</H2>
<P>replace the specified LimitRange</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/limitranges/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-limitrange-v1-core">Delete</H2>
<P>delete a LimitRange</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/limitranges/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-limitrange-v1-core">Delete Collection</H2>
<P>delete collection of LimitRange</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/limitranges</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-limitrange-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-limitrange-v1-core">Read</H2>
<P>read the specified LimitRange</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/limitranges/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#limitrange-v1-core">LimitRange</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-limitrange-v1-core">List</H2>
<P>list or watch objects of kind LimitRange</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/limitranges</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#limitrangelist-v1-core">LimitRangeList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-limitrange-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind LimitRange</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/limitranges</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#limitrangelist-v1-core">LimitRangeList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-limitrange-v1-core">Watch</H2>
<P>watch changes to an object of kind LimitRange</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/limitranges/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the LimitRange</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-limitrange-v1-core">Watch List</H2>
<P>watch individual changes to a list of LimitRange</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/limitranges</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-limitrange-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of LimitRange</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/limitranges</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler v1 autoscaling</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HorizontalPodAutoscaler</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#horizontalpodautoscaler-v2beta1-autoscaling">v2beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#horizontalpodautoscalerspec-v1-autoscaling">HorizontalPodAutoscalerSpec</a></I></TD><TD>behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus</a></I></TD><TD>current information about the autoscaler.</TD></TR>
</TBODY>
</TABLE>
<H3 id="horizontalpodautoscalerspec-v1-autoscaling">HorizontalPodAutoscalerSpec v1 autoscaling</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler [autoscaling/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxReplicas</CODE><BR /><I>integer</I></TD><TD>upper limit for the number of pods that can be set by the autoscaler; cannot be smaller than MinReplicas.</TD></TR>
<TR><TD><CODE>minReplicas</CODE><BR /><I>integer</I></TD><TD>lower limit for the number of pods that can be set by the autoscaler, default 1.</TD></TR>
<TR><TD><CODE>scaleTargetRef</CODE><BR /><I><a href="#crossversionobjectreference-v1-autoscaling">CrossVersionObjectReference</a></I></TD><TD>reference to scaled resource; horizontal pod autoscaler will learn the current resource consumption and will set the desired number of pods by using its Scale subresource.</TD></TR>
<TR><TD><CODE>targetCPUUtilizationPercentage</CODE><BR /><I>integer</I></TD><TD>target average CPU utilization (represented as a percentage of requested CPU) over all the pods; if not specified the default autoscaling policy will be used.</TD></TR>
</TBODY>
</TABLE>
<H3 id="horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus v1 autoscaling</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler [autoscaling/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>currentCPUUtilizationPercentage</CODE><BR /><I>integer</I></TD><TD>current average CPU utilization over all pods, represented as a percentage of requested CPU, e.g. 70 means that an average pod is using now 70% of its requested CPU.</TD></TR>
<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>current number of replicas of pods managed by this autoscaler.</TD></TR>
<TR><TD><CODE>desiredReplicas</CODE><BR /><I>integer</I></TD><TD>desired number of replicas of pods managed by this autoscaler.</TD></TR>
<TR><TD><CODE>lastScaleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>last time the HorizontalPodAutoscaler scaled the number of pods; used by the autoscaler to control how often the number of pods is changed.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>most recent generation observed by this autoscaler.</TD></TR>
</TBODY>
</TABLE>
<H3 id="horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList v1 autoscaling</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a> array</I></TD><TD>list of horizontal pod autoscaler objects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-horizontalpodautoscaler-v1-autoscaling-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-horizontalpodautoscaler-v1-autoscaling">Create</H2>
<P>create a HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-horizontalpodautoscaler-v1-autoscaling">Patch</H2>
<P>partially update the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-horizontalpodautoscaler-v1-autoscaling">Replace</H2>
<P>replace the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-horizontalpodautoscaler-v1-autoscaling">Delete</H2>
<P>delete a HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-horizontalpodautoscaler-v1-autoscaling">Delete Collection</H2>
<P>delete collection of HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-horizontalpodautoscaler-v1-autoscaling-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-horizontalpodautoscaler-v1-autoscaling">Read</H2>
<P>read the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-horizontalpodautoscaler-v1-autoscaling">List</H2>
<P>list or watch objects of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-horizontalpodautoscaler-v1-autoscaling">List All Namespaces</H2>
<P>list or watch objects of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v1/horizontalpodautoscalers</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-horizontalpodautoscaler-v1-autoscaling">Watch</H2>
<P>watch changes to an object of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v1/watch/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-horizontalpodautoscaler-v1-autoscaling">Watch List</H2>
<P>watch individual changes to a list of HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v1/watch/namespaces/{namespace}/horizontalpodautoscalers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-horizontalpodautoscaler-v1-autoscaling">Watch List All Namespaces</H2>
<P>watch individual changes to a list of HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v1/watch/horizontalpodautoscalers</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-horizontalpodautoscaler-v1-autoscaling-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-horizontalpodautoscaler-v1-autoscaling">Patch Status</H2>
<P>partially update status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-horizontalpodautoscaler-v1-autoscaling">Read Status</H2>
<P>read status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-horizontalpodautoscaler-v1-autoscaling">Replace Status</H2>
<P>replace status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration v1alpha1 admissionregistration.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>InitializerConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#initializerconfigurationlist-v1alpha1-admissionregistration-k8s-io">InitializerConfigurationList [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>initializers</CODE><BR /><I><a href="#initializer-v1alpha1-admissionregistration-k8s-io">Initializer</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Initializers is a list of resources and their default initializers Order-sensitive. When merging multiple InitializerConfigurations, we sort the initializers from different InitializerConfigurations by the name of the InitializerConfigurations; the order of the initializers from the same InitializerConfiguration is preserved.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata.</TD></TR>
</TBODY>
</TABLE>
<H3 id="initializerconfigurationlist-v1alpha1-admissionregistration-k8s-io">InitializerConfigurationList v1alpha1 admissionregistration</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a> array</I></TD><TD>List of InitializerConfiguration.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-initializerconfiguration-v1alpha1-admissionregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-initializerconfiguration-v1alpha1-admissionregistration-k8s-io">Create</H2>
<P>create an InitializerConfiguration</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-initializerconfiguration-v1alpha1-admissionregistration-k8s-io">Patch</H2>
<P>partially update the specified InitializerConfiguration</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the InitializerConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-initializerconfiguration-v1alpha1-admissionregistration-k8s-io">Replace</H2>
<P>replace the specified InitializerConfiguration</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the InitializerConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-initializerconfiguration-v1alpha1-admissionregistration-k8s-io">Delete</H2>
<P>delete an InitializerConfiguration</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the InitializerConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-initializerconfiguration-v1alpha1-admissionregistration-k8s-io">Delete Collection</H2>
<P>delete collection of InitializerConfiguration</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-initializerconfiguration-v1alpha1-admissionregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-initializerconfiguration-v1alpha1-admissionregistration-k8s-io">Read</H2>
<P>read the specified InitializerConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the InitializerConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-initializerconfiguration-v1alpha1-admissionregistration-k8s-io">List</H2>
<P>list or watch objects of kind InitializerConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/initializerconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#initializerconfigurationlist-v1alpha1-admissionregistration-k8s-io">InitializerConfigurationList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-initializerconfiguration-v1alpha1-admissionregistration-k8s-io">Watch</H2>
<P>watch changes to an object of kind InitializerConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/watch/initializerconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the InitializerConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-initializerconfiguration-v1alpha1-admissionregistration-k8s-io">Watch List</H2>
<P>watch individual changes to a list of InitializerConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1alpha1/watch/initializerconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration v1beta1 admissionregistration.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>MutatingWebhookConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#mutatingwebhookconfigurationlist-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfigurationList [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>webhooks</CODE><BR /><I><a href="#webhook-v1beta1-admissionregistration-k8s-io">Webhook</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Webhooks is a list of webhooks and the affected resources and operations.</TD></TR>
</TBODY>
</TABLE>
<H3 id="mutatingwebhookconfigurationlist-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfigurationList v1beta1 admissionregistration</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a> array</I></TD><TD>List of MutatingWebhookConfiguration.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Create</H2>
<P>create a MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/admissionregistration.k8s.io/v1beta1/mutatingwebhookconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Patch</H2>
<P>partially update the specified MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/admissionregistration.k8s.io/v1beta1/mutatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Replace</H2>
<P>replace the specified MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/admissionregistration.k8s.io/v1beta1/mutatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Delete</H2>
<P>delete a MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/admissionregistration.k8s.io/v1beta1/mutatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Delete Collection</H2>
<P>delete collection of MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/admissionregistration.k8s.io/v1beta1/mutatingwebhookconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Read</H2>
<P>read the specified MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1beta1/mutatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">List</H2>
<P>list or watch objects of kind MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1beta1/mutatingwebhookconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#mutatingwebhookconfigurationlist-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfigurationList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Watch</H2>
<P>watch changes to an object of kind MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1beta1/watch/mutatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the MutatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Watch List</H2>
<P>watch individual changes to a list of MutatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1beta1/watch/mutatingwebhookconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration v1beta1 admissionregistration.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ValidatingWebhookConfiguration</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#validatingwebhookconfigurationlist-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>webhooks</CODE><BR /><I><a href="#webhook-v1beta1-admissionregistration-k8s-io">Webhook</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Webhooks is a list of webhooks and the affected resources and operations.</TD></TR>
</TBODY>
</TABLE>
<H3 id="validatingwebhookconfigurationlist-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList v1beta1 admissionregistration</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a> array</I></TD><TD>List of ValidatingWebhookConfiguration.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Create</H2>
<P>create a ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/admissionregistration.k8s.io/v1beta1/validatingwebhookconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Patch</H2>
<P>partially update the specified ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/admissionregistration.k8s.io/v1beta1/validatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Replace</H2>
<P>replace the specified ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/admissionregistration.k8s.io/v1beta1/validatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Delete</H2>
<P>delete a ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/admissionregistration.k8s.io/v1beta1/validatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Delete Collection</H2>
<P>delete collection of ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/admissionregistration.k8s.io/v1beta1/validatingwebhookconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Read</H2>
<P>read the specified ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1beta1/validatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">List</H2>
<P>list or watch objects of kind ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1beta1/validatingwebhookconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#validatingwebhookconfigurationlist-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Watch</H2>
<P>watch changes to an object of kind ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1beta1/watch/validatingwebhookconfigurations/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ValidatingWebhookConfiguration</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">Watch List</H2>
<P>watch individual changes to a list of ValidatingWebhookConfiguration</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/admissionregistration.k8s.io/v1beta1/watch/validatingwebhookconfigurations</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="podtemplate-v1-core">PodTemplate v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodTemplate</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podtemplatelist-v1-core">PodTemplateList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template defines the pods that will be created from this pod template. https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="podtemplatespec-v1-core">PodTemplateSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetspec-v1-apps">DaemonSetSpec [apps/v1]</a></LI>
<LI><a href="#daemonsetspec-v1beta2-apps">DaemonSetSpec [apps/v1beta2]</a></LI>
<LI><a href="#daemonsetspec-v1beta1-extensions">DaemonSetSpec [extensions/v1beta1]</a></LI>
<LI><a href="#deploymentspec-v1-apps">DeploymentSpec [apps/v1]</a></LI>
<LI><a href="#deploymentspec-v1beta2-apps">DeploymentSpec [apps/v1beta2]</a></LI>
<LI><a href="#deploymentspec-v1beta1-apps">DeploymentSpec [apps/v1beta1]</a></LI>
<LI><a href="#deploymentspec-v1beta1-extensions">DeploymentSpec [extensions/v1beta1]</a></LI>
<LI><a href="#jobspec-v1-batch">JobSpec [batch/v1]</a></LI>
<LI><a href="#podtemplate-v1-core">PodTemplate [core/v1]</a></LI>
<LI><a href="#replicasetspec-v1-apps">ReplicaSetSpec [apps/v1]</a></LI>
<LI><a href="#replicasetspec-v1beta2-apps">ReplicaSetSpec [apps/v1beta2]</a></LI>
<LI><a href="#replicasetspec-v1beta1-extensions">ReplicaSetSpec [extensions/v1beta1]</a></LI>
<LI><a href="#replicationcontrollerspec-v1-core">ReplicationControllerSpec [core/v1]</a></LI>
<LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
<LI><a href="#statefulsetspec-v1beta2-apps">StatefulSetSpec [apps/v1beta2]</a></LI>
<LI><a href="#statefulsetspec-v1beta1-apps">StatefulSetSpec [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#podspec-v1-core">PodSpec</a></I></TD><TD>Specification of the desired behavior of the pod. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="podtemplatelist-v1-core">PodTemplateList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#podtemplate-v1-core">PodTemplate</a> array</I></TD><TD>List of pod templates</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-podtemplate-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-podtemplate-v1-core">Create</H2>
<P>create a PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/podtemplates</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-podtemplate-v1-core">Patch</H2>
<P>partially update the specified PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-podtemplate-v1-core">Replace</H2>
<P>replace the specified PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-podtemplate-v1-core">Delete</H2>
<P>delete a PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-podtemplate-v1-core">Delete Collection</H2>
<P>delete collection of PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/podtemplates</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-podtemplate-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-podtemplate-v1-core">Read</H2>
<P>read the specified PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/podtemplates/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podtemplate-v1-core">PodTemplate</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-podtemplate-v1-core">List</H2>
<P>list or watch objects of kind PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/podtemplates</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podtemplatelist-v1-core">PodTemplateList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-podtemplate-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/podtemplates</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podtemplatelist-v1-core">PodTemplateList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-podtemplate-v1-core">Watch</H2>
<P>watch changes to an object of kind PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/podtemplates/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodTemplate</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-podtemplate-v1-core">Watch List</H2>
<P>watch individual changes to a list of PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/podtemplates</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-podtemplate-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of PodTemplate</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/podtemplates</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="poddisruptionbudget-v1beta1-policy">PodDisruptionBudget v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PodDisruptionBudget</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#poddisruptionbudgetspec-v1beta1-policy">PodDisruptionBudgetSpec</a></I></TD><TD>Specification of the desired behavior of the PodDisruptionBudget.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#poddisruptionbudgetstatus-v1beta1-policy">PodDisruptionBudgetStatus</a></I></TD><TD>Most recently observed status of the PodDisruptionBudget.</TD></TR>
</TBODY>
</TABLE>
<H3 id="poddisruptionbudgetspec-v1beta1-policy">PodDisruptionBudgetSpec v1beta1 policy</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxUnavailable</CODE></TD><TD>An eviction is allowed if at most &#34;maxUnavailable&#34; pods selected by &#34;selector&#34; are unavailable after the eviction, i.e. even in absence of the evicted pod. For example, one can prevent all voluntary evictions by specifying 0. This is a mutually exclusive setting with &#34;minAvailable&#34;.</TD></TR>
<TR><TD><CODE>minAvailable</CODE></TD><TD>An eviction is allowed if at least &#34;minAvailable&#34; pods selected by &#34;selector&#34; will still be available after the eviction, i.e. even in the absence of the evicted pod. So for example you can prevent all voluntary evictions by specifying &#34;100%&#34;.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Label query over pods whose evictions are managed by the disruption budget.</TD></TR>
</TBODY>
</TABLE>
<H3 id="poddisruptionbudgetstatus-v1beta1-policy">PodDisruptionBudgetStatus v1beta1 policy</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>currentHealthy</CODE><BR /><I>integer</I></TD><TD>current number of healthy pods</TD></TR>
<TR><TD><CODE>desiredHealthy</CODE><BR /><I>integer</I></TD><TD>minimum desired number of healthy pods</TD></TR>
<TR><TD><CODE>disruptedPods</CODE><BR /><I>object</I></TD><TD>DisruptedPods contains information about pods whose eviction was processed by the API server eviction subresource handler but has not yet been observed by the PodDisruptionBudget controller. A pod will be in this map from the time when the API server processed the eviction request to the time when the pod is seen by PDB controller as having been marked for deletion (or after a timeout). The key in the map is the name of the pod and the value is the time when the API server processed the eviction request. If the deletion didn&#39;t occur and a pod is still there it will be removed from the list automatically by PodDisruptionBudget controller after some time. If everything goes smooth this map should be empty for the most of the time. Large number of entries in the map may indicate problems with pod deletions.</TD></TR>
<TR><TD><CODE>disruptionsAllowed</CODE><BR /><I>integer</I></TD><TD>Number of pod disruptions that are currently allowed.</TD></TR>
<TR><TD><CODE>expectedPods</CODE><BR /><I>integer</I></TD><TD>total number of pods counted by this disruption budget</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>Most recent generation observed when updating this PDB status. PodDisruptionsAllowed and other status informatio is valid only if observedGeneration equals to PDB&#39;s object generation.</TD></TR>
</TBODY>
</TABLE>
<H3 id="poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList v1beta1 policy</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-poddisruptionbudget-v1beta1-policy-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-poddisruptionbudget-v1beta1-policy">Create</H2>
<P>create a PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-poddisruptionbudget-v1beta1-policy">Patch</H2>
<P>partially update the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-poddisruptionbudget-v1beta1-policy">Replace</H2>
<P>replace the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-poddisruptionbudget-v1beta1-policy">Delete</H2>
<P>delete a PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-poddisruptionbudget-v1beta1-policy">Delete Collection</H2>
<P>delete collection of PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-poddisruptionbudget-v1beta1-policy-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-poddisruptionbudget-v1beta1-policy">Read</H2>
<P>read the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-poddisruptionbudget-v1beta1-policy">List</H2>
<P>list or watch objects of kind PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-poddisruptionbudget-v1beta1-policy">List All Namespaces</H2>
<P>list or watch objects of kind PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/poddisruptionbudgets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-poddisruptionbudget-v1beta1-policy">Watch</H2>
<P>watch changes to an object of kind PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/watch/namespaces/{namespace}/poddisruptionbudgets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-poddisruptionbudget-v1beta1-policy">Watch List</H2>
<P>watch individual changes to a list of PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/watch/namespaces/{namespace}/poddisruptionbudgets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-poddisruptionbudget-v1beta1-policy">Watch List All Namespaces</H2>
<P>watch individual changes to a list of PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/watch/poddisruptionbudgets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-poddisruptionbudget-v1beta1-policy-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-poddisruptionbudget-v1beta1-policy">Patch Status</H2>
<P>partially update status of the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-poddisruptionbudget-v1beta1-policy">Read Status</H2>
<P>read status of the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-poddisruptionbudget-v1beta1-policy">Replace Status</H2>
<P>replace status of the specified PodDisruptionBudget</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/policy/v1beta1/namespaces/{namespace}/poddisruptionbudgets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodDisruptionBudget</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="priorityclass-v1beta1-scheduling-k8s-io">PriorityClass v1beta1 scheduling.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>scheduling.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PriorityClass</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#priorityclass-v1alpha1-scheduling-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#priorityclasslist-v1beta1-scheduling-k8s-io">PriorityClassList [scheduling/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>description</CODE><BR /><I>string</I></TD><TD>description is an arbitrary string that usually provides guidelines on when this priority class should be used.</TD></TR>
<TR><TD><CODE>globalDefault</CODE><BR /><I>boolean</I></TD><TD>globalDefault specifies whether this PriorityClass should be considered as the default priority for pods that do not have any priority class. Only one PriorityClass can be marked as `globalDefault`. However, if more than one PriorityClasses exists with their `globalDefault` field set to true, the smallest value of such global default PriorityClasses will be used as the default priority.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>integer</I></TD><TD>The value of this priority class. This is the actual priority that pods receive when they have the name of this class in their pod spec.</TD></TR>
</TBODY>
</TABLE>
<H3 id="priorityclasslist-v1beta1-scheduling-k8s-io">PriorityClassList v1beta1 scheduling</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a> array</I></TD><TD>items is the list of PriorityClasses</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-priorityclass-v1beta1-scheduling-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-priorityclass-v1beta1-scheduling-k8s-io">Create</H2>
<P>create a PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/scheduling.k8s.io/v1beta1/priorityclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-priorityclass-v1beta1-scheduling-k8s-io">Patch</H2>
<P>partially update the specified PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/scheduling.k8s.io/v1beta1/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-priorityclass-v1beta1-scheduling-k8s-io">Replace</H2>
<P>replace the specified PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/scheduling.k8s.io/v1beta1/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-priorityclass-v1beta1-scheduling-k8s-io">Delete</H2>
<P>delete a PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/scheduling.k8s.io/v1beta1/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-priorityclass-v1beta1-scheduling-k8s-io">Delete Collection</H2>
<P>delete collection of PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/scheduling.k8s.io/v1beta1/priorityclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-priorityclass-v1beta1-scheduling-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-priorityclass-v1beta1-scheduling-k8s-io">Read</H2>
<P>read the specified PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/scheduling.k8s.io/v1beta1/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-priorityclass-v1beta1-scheduling-k8s-io">List</H2>
<P>list or watch objects of kind PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/scheduling.k8s.io/v1beta1/priorityclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#priorityclasslist-v1beta1-scheduling-k8s-io">PriorityClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-priorityclass-v1beta1-scheduling-k8s-io">Watch</H2>
<P>watch changes to an object of kind PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/scheduling.k8s.io/v1beta1/watch/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-priorityclass-v1beta1-scheduling-k8s-io">Watch List</H2>
<P>watch individual changes to a list of PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/scheduling.k8s.io/v1beta1/watch/priorityclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="podpreset-v1alpha1-settings-k8s-io">PodPreset v1alpha1 settings.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>settings.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>PodPreset</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-warning col-md-8"><P><I class="fa fa-warning"></I> <B>Warning:</B></P><P>Alpha objects should not be used in production and may not be compatible with future versions of the resource type.</P></DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podpresetlist-v1alpha1-settings-k8s-io">PodPresetList [settings/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#podpresetspec-v1alpha1-settings-k8s-io">PodPresetSpec</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3 id="podpresetspec-v1alpha1-settings-k8s-io">PodPresetSpec v1alpha1 settings</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset [settings/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>env</CODE><BR /><I><a href="#envvar-v1-core">EnvVar</a> array</I></TD><TD>Env defines the collection of EnvVar to inject into containers.</TD></TR>
<TR><TD><CODE>envFrom</CODE><BR /><I><a href="#envfromsource-v1-core">EnvFromSource</a> array</I></TD><TD>EnvFrom defines the collection of EnvFromSource to inject into containers.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selector is a label query over a set of resources, in this case pods. Required.</TD></TR>
<TR><TD><CODE>volumeMounts</CODE><BR /><I><a href="#volumemount-v1-core">VolumeMount</a> array</I></TD><TD>VolumeMounts defines the collection of VolumeMount to inject into containers.</TD></TR>
<TR><TD><CODE>volumes</CODE><BR /><I><a href="#volume-v1-core">Volume</a> array</I></TD><TD>Volumes defines the collection of Volume to inject into the pod.</TD></TR>
</TBODY>
</TABLE>
<H3 id="podpresetlist-v1alpha1-settings-k8s-io">PodPresetList v1alpha1 settings</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a> array</I></TD><TD>Items is a list of schema objects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-podpreset-v1alpha1-settings-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-podpreset-v1alpha1-settings-k8s-io">Create</H2>
<P>create a PodPreset</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/settings.k8s.io/v1alpha1/namespaces/{namespace}/podpresets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-podpreset-v1alpha1-settings-k8s-io">Patch</H2>
<P>partially update the specified PodPreset</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/settings.k8s.io/v1alpha1/namespaces/{namespace}/podpresets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodPreset</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-podpreset-v1alpha1-settings-k8s-io">Replace</H2>
<P>replace the specified PodPreset</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/settings.k8s.io/v1alpha1/namespaces/{namespace}/podpresets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodPreset</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-podpreset-v1alpha1-settings-k8s-io">Delete</H2>
<P>delete a PodPreset</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/settings.k8s.io/v1alpha1/namespaces/{namespace}/podpresets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodPreset</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-podpreset-v1alpha1-settings-k8s-io">Delete Collection</H2>
<P>delete collection of PodPreset</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/settings.k8s.io/v1alpha1/namespaces/{namespace}/podpresets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-podpreset-v1alpha1-settings-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-podpreset-v1alpha1-settings-k8s-io">Read</H2>
<P>read the specified PodPreset</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/settings.k8s.io/v1alpha1/namespaces/{namespace}/podpresets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodPreset</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-podpreset-v1alpha1-settings-k8s-io">List</H2>
<P>list or watch objects of kind PodPreset</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/settings.k8s.io/v1alpha1/namespaces/{namespace}/podpresets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podpresetlist-v1alpha1-settings-k8s-io">PodPresetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-podpreset-v1alpha1-settings-k8s-io">List All Namespaces</H2>
<P>list or watch objects of kind PodPreset</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/settings.k8s.io/v1alpha1/podpresets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podpresetlist-v1alpha1-settings-k8s-io">PodPresetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-podpreset-v1alpha1-settings-k8s-io">Watch</H2>
<P>watch changes to an object of kind PodPreset</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/settings.k8s.io/v1alpha1/watch/namespaces/{namespace}/podpresets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodPreset</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-podpreset-v1alpha1-settings-k8s-io">Watch List</H2>
<P>watch individual changes to a list of PodPreset</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/settings.k8s.io/v1alpha1/watch/namespaces/{namespace}/podpresets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-podpreset-v1alpha1-settings-k8s-io">Watch List All Namespaces</H2>
<P>watch individual changes to a list of PodPreset</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/settings.k8s.io/v1alpha1/watch/podpresets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PodSecurityPolicy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicylist-v1beta1-extensions">PodSecurityPolicyList [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#podsecuritypolicyspec-v1beta1-extensions">PodSecurityPolicySpec</a></I></TD><TD>spec defines the policy enforced.</TD></TR>
</TBODY>
</TABLE>
<H3 id="podsecuritypolicyspec-v1beta1-extensions">PodSecurityPolicySpec v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowPrivilegeEscalation</CODE><BR /><I>boolean</I></TD><TD>allowPrivilegeEscalation determines if a pod can request to allow privilege escalation. If unspecified, defaults to true.</TD></TR>
<TR><TD><CODE>allowedCapabilities</CODE><BR /><I>string array</I></TD><TD>allowedCapabilities is a list of capabilities that can be requested to add to the container. Capabilities in this field may be added at the pod author&#39;s discretion. You must not list a capability in both allowedCapabilities and requiredDropCapabilities.</TD></TR>
<TR><TD><CODE>allowedFlexVolumes</CODE><BR /><I><a href="#allowedflexvolume-v1beta1-extensions">AllowedFlexVolume</a> array</I></TD><TD>allowedFlexVolumes is a whitelist of allowed Flexvolumes. Empty or nil indicates that all Flexvolumes may be used. This parameter is effective only when the usage of the Flexvolumes is allowed in the &#34;volumes&#34; field.</TD></TR>
<TR><TD><CODE>allowedHostPaths</CODE><BR /><I><a href="#allowedhostpath-v1beta1-extensions">AllowedHostPath</a> array</I></TD><TD>allowedHostPaths is a white list of allowed host paths. Empty indicates that all host paths may be used.</TD></TR>
<TR><TD><CODE>allowedUnsafeSysctls</CODE><BR /><I>string array</I></TD><TD>allowedUnsafeSysctls is a list of explicitly allowed unsafe sysctls, defaults to none. Each entry is either a plain sysctl name or ends in &#34;*&#34; in which case it is considered as a prefix of allowed sysctls. Single * means all unsafe sysctls are allowed. Kubelet has to whitelist all allowed unsafe sysctls explicitly to avoid rejection. Examples: e.g. &#34;foo/*&#34; allows &#34;foo/bar&#34;, &#34;foo/baz&#34;, etc. e.g. &#34;foo.*&#34; allows &#34;foo.bar&#34;, &#34;foo.baz&#34;, etc.</TD></TR>
<TR><TD><CODE>defaultAddCapabilities</CODE><BR /><I>string array</I></TD><TD>defaultAddCapabilities is the default set of capabilities that will be added to the container unless the pod spec specifically drops the capability. You may not list a capability in both defaultAddCapabilities and requiredDropCapabilities. Capabilities added here are implicitly allowed, and need not be included in the allowedCapabilities list.</TD></TR>
<TR><TD><CODE>defaultAllowPrivilegeEscalation</CODE><BR /><I>boolean</I></TD><TD>defaultAllowPrivilegeEscalation controls the default setting for whether a process can gain more privileges than its parent process.</TD></TR>
<TR><TD><CODE>forbiddenSysctls</CODE><BR /><I>string array</I></TD><TD>forbiddenSysctls is a list of explicitly forbidden sysctls, defaults to none. Each entry is either a plain sysctl name or ends in &#34;*&#34; in which case it is considered as a prefix of forbidden sysctls. Single * means all sysctls are forbidden. Examples: e.g. &#34;foo/*&#34; forbids &#34;foo/bar&#34;, &#34;foo/baz&#34;, etc. e.g. &#34;foo.*&#34; forbids &#34;foo.bar&#34;, &#34;foo.baz&#34;, etc.</TD></TR>
<TR><TD><CODE>fsGroup</CODE><BR /><I><a href="#fsgroupstrategyoptions-v1beta1-extensions">FSGroupStrategyOptions</a></I></TD><TD>fsGroup is the strategy that will dictate what fs group is used by the SecurityContext.</TD></TR>
<TR><TD><CODE>hostIPC</CODE><BR /><I>boolean</I></TD><TD>hostIPC determines if the policy allows the use of HostIPC in the pod spec.</TD></TR>
<TR><TD><CODE>hostNetwork</CODE><BR /><I>boolean</I></TD><TD>hostNetwork determines if the policy allows the use of HostNetwork in the pod spec.</TD></TR>
<TR><TD><CODE>hostPID</CODE><BR /><I>boolean</I></TD><TD>hostPID determines if the policy allows the use of HostPID in the pod spec.</TD></TR>
<TR><TD><CODE>hostPorts</CODE><BR /><I><a href="#hostportrange-v1beta1-extensions">HostPortRange</a> array</I></TD><TD>hostPorts determines which host port ranges are allowed to be exposed.</TD></TR>
<TR><TD><CODE>privileged</CODE><BR /><I>boolean</I></TD><TD>privileged determines if a pod can request to be run as privileged.</TD></TR>
<TR><TD><CODE>readOnlyRootFilesystem</CODE><BR /><I>boolean</I></TD><TD>readOnlyRootFilesystem when set to true will force containers to run with a read only root file system. If the container specifically requests to run with a non-read only root file system the PSP should deny the pod. If set to false the container may run with a read only root file system if it wishes but it will not be forced to.</TD></TR>
<TR><TD><CODE>requiredDropCapabilities</CODE><BR /><I>string array</I></TD><TD>requiredDropCapabilities are the capabilities that will be dropped from the container. These are required to be dropped and cannot be added.</TD></TR>
<TR><TD><CODE>runAsUser</CODE><BR /><I><a href="#runasuserstrategyoptions-v1beta1-extensions">RunAsUserStrategyOptions</a></I></TD><TD>runAsUser is the strategy that will dictate the allowable RunAsUser values that may be set.</TD></TR>
<TR><TD><CODE>seLinux</CODE><BR /><I><a href="#selinuxstrategyoptions-v1beta1-extensions">SELinuxStrategyOptions</a></I></TD><TD>seLinux is the strategy that will dictate the allowable labels that may be set.</TD></TR>
<TR><TD><CODE>supplementalGroups</CODE><BR /><I><a href="#supplementalgroupsstrategyoptions-v1beta1-extensions">SupplementalGroupsStrategyOptions</a></I></TD><TD>supplementalGroups is the strategy that will dictate what supplemental groups are used by the SecurityContext.</TD></TR>
<TR><TD><CODE>volumes</CODE><BR /><I>string array</I></TD><TD>volumes is a white list of allowed volume plugins. Empty indicates that no volumes may be used. To allow all volumes you may use &#39;\*&#39;.</TD></TR>
</TBODY>
</TABLE>
<H3 id="podsecuritypolicylist-v1beta1-extensions">PodSecurityPolicyList v1beta1 extensions</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a> array</I></TD><TD>items is a list of schema objects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-podsecuritypolicy-v1beta1-extensions-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-podsecuritypolicy-v1beta1-extensions">Create</H2>
<P>create a PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/extensions/v1beta1/podsecuritypolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-podsecuritypolicy-v1beta1-extensions">Patch</H2>
<P>partially update the specified PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-podsecuritypolicy-v1beta1-extensions">Replace</H2>
<P>replace the specified PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-podsecuritypolicy-v1beta1-extensions">Delete</H2>
<P>delete a PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-podsecuritypolicy-v1beta1-extensions">Delete Collection</H2>
<P>delete collection of PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/podsecuritypolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-podsecuritypolicy-v1beta1-extensions-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-podsecuritypolicy-v1beta1-extensions">Read</H2>
<P>read the specified PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-podsecuritypolicy-v1beta1-extensions">List</H2>
<P>list or watch objects of kind PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/podsecuritypolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podsecuritypolicylist-v1beta1-extensions">PodSecurityPolicyList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-podsecuritypolicy-v1beta1-extensions">Watch</H2>
<P>watch changes to an object of kind PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-podsecuritypolicy-v1beta1-extensions">Watch List</H2>
<P>watch individual changes to a list of PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/podsecuritypolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="-strong-cluster-apis-strong-"><STRONG>Cluster APIs</STRONG></H1>
<H1 id="apiservice-v1-apiregistration-k8s-io">APIService v1 apiregistration.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIService</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#apiservice-v1beta1-apiregistration-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservicelist-v1-apiregistration-k8s-io">APIServiceList [apiregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#apiservicespec-v1-apiregistration-k8s-io">APIServiceSpec</a></I></TD><TD>Spec contains information for locating and communicating with a server</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#apiservicestatus-v1-apiregistration-k8s-io">APIServiceStatus</a></I></TD><TD>Status contains derived information about an API server</TD></TR>
</TBODY>
</TABLE>
<H3 id="apiservicespec-v1-apiregistration-k8s-io">APIServiceSpec v1 apiregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservice-v1-apiregistration-k8s-io">APIService [apiregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>caBundle</CODE><BR /><I>string</I></TD><TD>CABundle is a PEM encoded CA bundle which will be used to validate an API server&#39;s serving certificate.</TD></TR>
<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>Group is the API group name this server hosts</TD></TR>
<TR><TD><CODE>groupPriorityMinimum</CODE><BR /><I>integer</I></TD><TD>GroupPriorityMininum is the priority this group should have at least. Higher priority means that the group is preferred by clients over lower priority ones. Note that other versions of this group might specify even higher GroupPriorityMininum values such that the whole group gets a higher priority. The primary sort is based on GroupPriorityMinimum, ordered highest number to lowest (20 before 10). The secondary sort is based on the alphabetical comparison of the name of the object. (v1.bar before v1.foo) We&#39;d recommend something like: *.k8s.io (except extensions) at 18000 and PaaSes (OpenShift, Deis) are recommended to be in the 2000s</TD></TR>
<TR><TD><CODE>insecureSkipTLSVerify</CODE><BR /><I>boolean</I></TD><TD>InsecureSkipTLSVerify disables TLS certificate verification when communicating with this server. This is strongly discouraged. You should use the CABundle instead.</TD></TR>
<TR><TD><CODE>service</CODE><BR /><I><a href="#servicereference-v1-apiregistration-k8s-io">ServiceReference</a></I></TD><TD>Service is a reference to the service for this API server. It must communicate on port 443 If the Service is nil, that means the handling for the API groupversion is handled locally on this server. The call will simply delegate to the normal handler chain to be fulfilled.</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>Version is the API version this server hosts. For example, &#34;v1&#34;</TD></TR>
<TR><TD><CODE>versionPriority</CODE><BR /><I>integer</I></TD><TD>VersionPriority controls the ordering of this API version inside of its group. Must be greater than zero. The primary sort is based on VersionPriority, ordered highest to lowest (20 before 10). Since it&#39;s inside of a group, the number can be small, probably in the 10s. In case of equal version priorities, the version string will be used to compute the order inside a group. If the version string is &#34;kube-like&#34;, it will sort above non &#34;kube-like&#34; version strings, which are ordered lexicographically. &#34;Kube-like&#34; versions start with a &#34;v&#34;, then are followed by a number (the major version), then optionally the string &#34;alpha&#34; or &#34;beta&#34; and another number (the minor version). These are sorted first by GA &gt; beta &gt; alpha (where GA is a version with no suffix such as beta or alpha), and then by comparing major version, then minor version. An example sorted list of versions: v10, v2, v1, v11beta2, v10beta3, v3beta1, v12alpha1, v11alpha2, foo1, foo10.</TD></TR>
</TBODY>
</TABLE>
<H3 id="apiservicestatus-v1-apiregistration-k8s-io">APIServiceStatus v1 apiregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservice-v1-apiregistration-k8s-io">APIService [apiregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#apiservicecondition-v1-apiregistration-k8s-io">APIServiceCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Current service state of apiService.</TD></TR>
</TBODY>
</TABLE>
<H3 id="apiservicelist-v1-apiregistration-k8s-io">APIServiceList v1 apiregistration</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-apiservice-v1-apiregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-apiservice-v1-apiregistration-k8s-io">Create</H2>
<P>create an APIService</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apiregistration.k8s.io/v1/apiservices</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-apiservice-v1-apiregistration-k8s-io">Patch</H2>
<P>partially update the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-apiservice-v1-apiregistration-k8s-io">Replace</H2>
<P>replace the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-apiservice-v1-apiregistration-k8s-io">Delete</H2>
<P>delete an APIService</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-apiservice-v1-apiregistration-k8s-io">Delete Collection</H2>
<P>delete collection of APIService</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apiregistration.k8s.io/v1/apiservices</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-apiservice-v1-apiregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-apiservice-v1-apiregistration-k8s-io">Read</H2>
<P>read the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-apiservice-v1-apiregistration-k8s-io">List</H2>
<P>list or watch objects of kind APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1/apiservices</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservicelist-v1-apiregistration-k8s-io">APIServiceList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-apiservice-v1-apiregistration-k8s-io">Watch</H2>
<P>watch changes to an object of kind APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1/watch/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-apiservice-v1-apiregistration-k8s-io">Watch List</H2>
<P>watch individual changes to a list of APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1/watch/apiservices</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-apiservice-v1-apiregistration-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-apiservice-v1-apiregistration-k8s-io">Patch Status</H2>
<P>partially update status of the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apiregistration.k8s.io/v1/apiservices/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-apiservice-v1-apiregistration-k8s-io">Read Status</H2>
<P>read status of the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1/apiservices/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-apiservice-v1-apiregistration-k8s-io">Replace Status</H2>
<P>replace status of the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apiregistration.k8s.io/v1/apiservices/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#apiservice-v1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="binding-v1-core">Binding v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Binding</CODE></TD></TR>
</TBODY>
</TABLE>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>target</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>The target object that you want to bind to the standard object.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-binding-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-binding-v1-core">Create</H2>
<P>create a Binding</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/bindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#binding-v1-core">Binding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#binding-v1-core">Binding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#binding-v1-core">Binding</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#binding-v1-core">Binding</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H1 id="certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest v1beta1 certificates.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>certificates.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CertificateSigningRequest</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#certificatesigningrequestlist-v1beta1-certificates-k8s-io">CertificateSigningRequestList [certificates/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#certificatesigningrequestspec-v1beta1-certificates-k8s-io">CertificateSigningRequestSpec</a></I></TD><TD>The certificate request itself and any additional information.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#certificatesigningrequeststatus-v1beta1-certificates-k8s-io">CertificateSigningRequestStatus</a></I></TD><TD>Derived information about the request.</TD></TR>
</TBODY>
</TABLE>
<H3 id="certificatesigningrequestspec-v1beta1-certificates-k8s-io">CertificateSigningRequestSpec v1beta1 certificates</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest [certificates/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extra</CODE><BR /><I>object</I></TD><TD>Extra information about the requesting user. See user.Info interface for details.</TD></TR>
<TR><TD><CODE>groups</CODE><BR /><I>string array</I></TD><TD>Group information about the requesting user. See user.Info interface for details.</TD></TR>
<TR><TD><CODE>request</CODE><BR /><I>string</I></TD><TD>Base64-encoded PKCS#10 CSR data</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID information about the requesting user. See user.Info interface for details.</TD></TR>
<TR><TD><CODE>usages</CODE><BR /><I>string array</I></TD><TD>allowedUsages specifies a set of usage contexts the key will be valid for. See: https://tools.ietf.org/html/rfc5280#section-4.2.1.3 https://tools.ietf.org/html/rfc5280#section-4.2.1.12</TD></TR>
<TR><TD><CODE>username</CODE><BR /><I>string</I></TD><TD>Information about the requesting user. See user.Info interface for details.</TD></TR>
</TBODY>
</TABLE>
<H3 id="certificatesigningrequeststatus-v1beta1-certificates-k8s-io">CertificateSigningRequestStatus v1beta1 certificates</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest [certificates/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>certificate</CODE><BR /><I>string</I></TD><TD>If request was approved, the controller will place the issued certificate here.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#certificatesigningrequestcondition-v1beta1-certificates-k8s-io">CertificateSigningRequestCondition</a> array</I></TD><TD>Conditions applied to the request, such as approval or denial.</TD></TR>
</TBODY>
</TABLE>
<H3 id="certificatesigningrequestlist-v1beta1-certificates-k8s-io">CertificateSigningRequestList v1beta1 certificates</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-certificatesigningrequest-v1beta1-certificates-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-certificatesigningrequest-v1beta1-certificates-k8s-io">Create</H2>
<P>create a CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/certificates.k8s.io/v1beta1/certificatesigningrequests</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-certificatesigningrequest-v1beta1-certificates-k8s-io">Patch</H2>
<P>partially update the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/certificates.k8s.io/v1beta1/certificatesigningrequests/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-certificatesigningrequest-v1beta1-certificates-k8s-io">Replace</H2>
<P>replace the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/certificates.k8s.io/v1beta1/certificatesigningrequests/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-certificatesigningrequest-v1beta1-certificates-k8s-io">Delete</H2>
<P>delete a CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/certificates.k8s.io/v1beta1/certificatesigningrequests/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-certificatesigningrequest-v1beta1-certificates-k8s-io">Delete Collection</H2>
<P>delete collection of CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/certificates.k8s.io/v1beta1/certificatesigningrequests</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-certificatesigningrequest-v1beta1-certificates-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-certificatesigningrequest-v1beta1-certificates-k8s-io">Read</H2>
<P>read the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/certificates.k8s.io/v1beta1/certificatesigningrequests/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-certificatesigningrequest-v1beta1-certificates-k8s-io">List</H2>
<P>list or watch objects of kind CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/certificates.k8s.io/v1beta1/certificatesigningrequests</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#certificatesigningrequestlist-v1beta1-certificates-k8s-io">CertificateSigningRequestList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-certificatesigningrequest-v1beta1-certificates-k8s-io">Watch</H2>
<P>watch changes to an object of kind CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/certificates.k8s.io/v1beta1/watch/certificatesigningrequests/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-certificatesigningrequest-v1beta1-certificates-k8s-io">Watch List</H2>
<P>watch individual changes to a list of CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/certificates.k8s.io/v1beta1/watch/certificatesigningrequests</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-certificatesigningrequest-v1beta1-certificates-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-certificatesigningrequest-v1beta1-certificates-k8s-io">Patch Status</H2>
<P>partially update status of the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/certificates.k8s.io/v1beta1/certificatesigningrequests/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-certificatesigningrequest-v1beta1-certificates-k8s-io">Read Status</H2>
<P>read status of the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/certificates.k8s.io/v1beta1/certificatesigningrequests/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-certificatesigningrequest-v1beta1-certificates-k8s-io">Replace Status</H2>
<P>replace status of the specified CertificateSigningRequest</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/certificates.k8s.io/v1beta1/certificatesigningrequests/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CertificateSigningRequest</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="clusterrole-v1-rbac-authorization-k8s-io">ClusterRole v1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ClusterRole</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
<a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolelist-v1-rbac-authorization-k8s-io">ClusterRoleList [rbac/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>aggregationRule</CODE><BR /><I><a href="#aggregationrule-v1-rbac-authorization-k8s-io">AggregationRule</a></I></TD><TD>AggregationRule is an optional field that describes how to build the Rules for this ClusterRole. If AggregationRule is set, then the Rules are controller managed and direct changes to Rules will be stomped by the controller.</TD></TR>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyrule-v1-rbac-authorization-k8s-io">PolicyRule</a> array</I></TD><TD>Rules holds all the PolicyRules for this ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3 id="clusterrolelist-v1-rbac-authorization-k8s-io">ClusterRoleList v1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a> array</I></TD><TD>Items is a list of ClusterRoles</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-clusterrole-v1-rbac-authorization-k8s-io">Create</H2>
<P>create a ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-clusterrole-v1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-clusterrole-v1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-clusterrole-v1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-clusterrole-v1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-clusterrole-v1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-clusterrole-v1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-clusterrole-v1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolelist-v1-rbac-authorization-k8s-io">ClusterRoleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-clusterrole-v1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-clusterrole-v1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding v1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ClusterRoleBinding</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
<a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolebindinglist-v1-rbac-authorization-k8s-io">ClusterRoleBindingList [rbac/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>roleRef</CODE><BR /><I><a href="#roleref-v1-rbac-authorization-k8s-io">RoleRef</a></I></TD><TD>RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.</TD></TR>
<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1-rbac-authorization-k8s-io">Subject</a> array</I></TD><TD>Subjects holds references to the objects the role applies to.</TD></TR>
</TBODY>
</TABLE>
<H3 id="clusterrolebindinglist-v1-rbac-authorization-k8s-io">ClusterRoleBindingList v1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a> array</I></TD><TD>Items is a list of ClusterRoleBindings</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-clusterrolebinding-v1-rbac-authorization-k8s-io">Create</H2>
<P>create a ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-clusterrolebinding-v1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-clusterrolebinding-v1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-clusterrolebinding-v1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-clusterrolebinding-v1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-clusterrolebinding-v1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-clusterrolebinding-v1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-clusterrolebinding-v1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebindinglist-v1-rbac-authorization-k8s-io">ClusterRoleBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-clusterrolebinding-v1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-clusterrolebinding-v1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="componentstatus-v1-core">ComponentStatus v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ComponentStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#componentstatuslist-v1-core">ComponentStatusList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#componentcondition-v1-core">ComponentCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>List of component conditions observed</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H3 id="componentstatuslist-v1-core">ComponentStatusList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#componentstatus-v1-core">ComponentStatus</a> array</I></TD><TD>List of ComponentStatus objects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-componentstatus-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-componentstatus-v1-core">Read</H2>
<P>read the specified ComponentStatus</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/componentstatuses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ComponentStatus</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#componentstatus-v1-core">ComponentStatus</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-componentstatus-v1-core">List</H2>
<P>list objects of kind ComponentStatus</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/componentstatuses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#componentstatuslist-v1-core">ComponentStatusList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview v1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LocalSubjectAccessReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#localsubjectaccessreview-v1beta1-authorization-k8s-io">v1beta1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated. spec.namespace must be equal to the namespace you made the request against. If empty, it is defaulted.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectaccessreviewstatus-v1-authorization-k8s-io">SubjectAccessReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request is allowed or not</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-localsubjectaccessreview-v1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-localsubjectaccessreview-v1-authorization-k8s-io">Create</H2>
<P>create a LocalSubjectAccessReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authorization.k8s.io/v1/namespaces/{namespace}/localsubjectaccessreviews</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="namespace-v1-core">Namespace v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Namespace</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#namespacelist-v1-core">NamespaceList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#namespacespec-v1-core">NamespaceSpec</a></I></TD><TD>Spec defines the behavior of the Namespace. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#namespacestatus-v1-core">NamespaceStatus</a></I></TD><TD>Status describes the current status of a Namespace. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="namespacespec-v1-core">NamespaceSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#namespace-v1-core">Namespace [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>finalizers</CODE><BR /><I>string array</I></TD><TD>Finalizers is an opaque list of values that must be empty to permanently remove object from storage. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/</TD></TR>
</TBODY>
</TABLE>
<H3 id="namespacestatus-v1-core">NamespaceStatus v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#namespace-v1-core">Namespace [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>Phase is the current lifecycle phase of the namespace. More info: https://kubernetes.io/docs/tasks/administer-cluster/namespaces/</TD></TR>
</TBODY>
</TABLE>
<H3 id="namespacelist-v1-core">NamespaceList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#namespace-v1-core">Namespace</a> array</I></TD><TD>Items is the list of Namespace objects in the list. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-namespace-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-namespace-v1-core">Create</H2>
<P>create a Namespace</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-namespace-v1-core">Patch</H2>
<P>partially update the specified Namespace</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-namespace-v1-core">Replace</H2>
<P>replace the specified Namespace</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-namespace-v1-core">Delete</H2>
<P>delete a Namespace</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-namespace-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-namespace-v1-core">Read</H2>
<P>read the specified Namespace</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-namespace-v1-core">List</H2>
<P>list or watch objects of kind Namespace</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#namespacelist-v1-core">NamespaceList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-namespace-v1-core">Watch</H2>
<P>watch changes to an object of kind Namespace</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-namespace-v1-core">Watch List</H2>
<P>watch individual changes to a list of Namespace</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-namespace-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-namespace-v1-core">Patch Status</H2>
<P>partially update status of the specified Namespace</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-namespace-v1-core">Read Status</H2>
<P>read status of the specified Namespace</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-namespace-v1-core">Replace Status</H2>
<P>replace status of the specified Namespace</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Namespace</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#namespace-v1-core">Namespace</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="node-v1-core">Node v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Node</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodelist-v1-core">NodeList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#nodespec-v1-core">NodeSpec</a></I></TD><TD>Spec defines the behavior of a node. https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#nodestatus-v1-core">NodeStatus</a></I></TD><TD>Most recently observed status of the node. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="nodespec-v1-core">NodeSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#node-v1-core">Node [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>configSource</CODE><BR /><I><a href="#nodeconfigsource-v1-core">NodeConfigSource</a></I></TD><TD>If specified, the source to get node configuration from The DynamicKubeletConfig feature gate must be enabled for the Kubelet to use this field</TD></TR>
<TR><TD><CODE>externalID</CODE><BR /><I>string</I></TD><TD>Deprecated. Not all kubelets will set this field. Remove field after 1.13. see: https://issues.k8s.io/61966</TD></TR>
<TR><TD><CODE>podCIDR</CODE><BR /><I>string</I></TD><TD>PodCIDR represents the pod IP range assigned to the node.</TD></TR>
<TR><TD><CODE>providerID</CODE><BR /><I>string</I></TD><TD>ID of the node assigned by the cloud provider in the format: &lt;ProviderName&gt;://&lt;ProviderSpecificNodeID&gt;</TD></TR>
<TR><TD><CODE>taints</CODE><BR /><I><a href="#taint-v1-core">Taint</a> array</I></TD><TD>If specified, the node&#39;s taints.</TD></TR>
<TR><TD><CODE>unschedulable</CODE><BR /><I>boolean</I></TD><TD>Unschedulable controls node schedulability of new pods. By default, node is schedulable. More info: https://kubernetes.io/docs/concepts/nodes/node/#manual-node-administration</TD></TR>
</TBODY>
</TABLE>
<H3 id="nodestatus-v1-core">NodeStatus v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#node-v1-core">Node [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>addresses</CODE><BR /><I><a href="#nodeaddress-v1-core">NodeAddress</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>List of addresses reachable to the node. Queried from cloud provider, if available. More info: https://kubernetes.io/docs/concepts/nodes/node/#addresses</TD></TR>
<TR><TD><CODE>allocatable</CODE><BR /><I>object</I></TD><TD>Allocatable represents the resources of a node that are available for scheduling. Defaults to Capacity.</TD></TR>
<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>Capacity represents the total resources of a node. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#capacity</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#nodecondition-v1-core">NodeCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Conditions is an array of current observed node conditions. More info: https://kubernetes.io/docs/concepts/nodes/node/#condition</TD></TR>
<TR><TD><CODE>config</CODE><BR /><I><a href="#nodeconfigstatus-v1-core">NodeConfigStatus</a></I></TD><TD>Status of the config assigned to the node via the dynamic Kubelet config feature.</TD></TR>
<TR><TD><CODE>daemonEndpoints</CODE><BR /><I><a href="#nodedaemonendpoints-v1-core">NodeDaemonEndpoints</a></I></TD><TD>Endpoints of daemons running on the Node.</TD></TR>
<TR><TD><CODE>images</CODE><BR /><I><a href="#containerimage-v1-core">ContainerImage</a> array</I></TD><TD>List of container images on this node</TD></TR>
<TR><TD><CODE>nodeInfo</CODE><BR /><I><a href="#nodesysteminfo-v1-core">NodeSystemInfo</a></I></TD><TD>Set of ids/uuids to uniquely identify the node. More info: https://kubernetes.io/docs/concepts/nodes/node/#info</TD></TR>
<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>NodePhase is the recently observed lifecycle phase of the node. More info: https://kubernetes.io/docs/concepts/nodes/node/#phase The field is never populated, and now is deprecated.</TD></TR>
<TR><TD><CODE>volumesAttached</CODE><BR /><I><a href="#attachedvolume-v1-core">AttachedVolume</a> array</I></TD><TD>List of volumes that are attached to the node.</TD></TR>
<TR><TD><CODE>volumesInUse</CODE><BR /><I>string array</I></TD><TD>List of attachable volumes in use (mounted) by the node.</TD></TR>
</TBODY>
</TABLE>
<H3 id="nodelist-v1-core">NodeList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#node-v1-core">Node</a> array</I></TD><TD>List of nodes</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-node-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-node-v1-core">Create</H2>
<P>create a Node</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/nodes</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#node-v1-core">Node</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-node-v1-core">Patch</H2>
<P>partially update the specified Node</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/nodes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-node-v1-core">Replace</H2>
<P>replace the specified Node</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/nodes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#node-v1-core">Node</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-node-v1-core">Delete</H2>
<P>delete a Node</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/nodes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-node-v1-core">Delete Collection</H2>
<P>delete collection of Node</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/nodes</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-node-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-node-v1-core">Read</H2>
<P>read the specified Node</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/nodes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-node-v1-core">List</H2>
<P>list or watch objects of kind Node</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/nodes</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#nodelist-v1-core">NodeList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-node-v1-core">Watch</H2>
<P>watch changes to an object of kind Node</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/nodes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-node-v1-core">Watch List</H2>
<P>watch individual changes to a list of Node</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/nodes</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-node-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-node-v1-core">Patch Status</H2>
<P>partially update status of the specified Node</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/nodes/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-node-v1-core">Read Status</H2>
<P>read status of the specified Node</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/nodes/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-node-v1-core">Replace Status</H2>
<P>replace status of the specified Node</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/nodes/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#node-v1-core">Node</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#node-v1-core">Node</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-proxy-operations-node-v1-core-strong-"><STRONG>Proxy Operations</STRONG></H2>
<H2 id="create-connect-proxy-node-v1-core">Create Connect Proxy</H2>
<P>connect POST requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/nodes/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="create-connect-proxy-path-node-v1-core">Create Connect Proxy Path</H2>
<P>connect POST requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/nodes/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-connect-proxy-node-v1-core">Delete Connect Proxy</H2>
<P>connect DELETE requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/nodes/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-connect-proxy-path-node-v1-core">Delete Connect Proxy Path</H2>
<P>connect DELETE requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/nodes/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="get-connect-proxy-node-v1-core">Get Connect Proxy</H2>
<P>connect GET requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/nodes/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="get-connect-proxy-path-node-v1-core">Get Connect Proxy Path</H2>
<P>connect GET requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/nodes/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="head-connect-proxy-node-v1-core">Head Connect Proxy</H2>
<P>connect HEAD requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>HEAD /api/v1/nodes/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="head-connect-proxy-path-node-v1-core">Head Connect Proxy Path</H2>
<P>connect HEAD requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>HEAD /api/v1/nodes/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-connect-proxy-node-v1-core">Replace Connect Proxy</H2>
<P>connect PUT requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/nodes/{name}/proxy</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-connect-proxy-path-node-v1-core">Replace Connect Proxy Path</H2>
<P>connect PUT requests to proxy of Node</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/nodes/{name}/proxy/{path}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Node</TD></TR>
<TR><TD><CODE>path</CODE></TD><TD>path to the resource</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE></TD><TD>Path is the URL path to use for the current proxy request to node.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I>string</I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="persistentvolume-v1-core">PersistentVolume v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PersistentVolume</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-bullhorn"></I> These are assigned to <a href="#pod-v1-core">Pods</a> using <a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaims</a>.</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumelist-v1-core">PersistentVolumeList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec</a></I></TD><TD>Spec defines a specification of a persistent volume owned by the cluster. Provisioned by an administrator. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent-volumes</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#persistentvolumestatus-v1-core">PersistentVolumeStatus</a></I></TD><TD>Status represents the current information/status for the persistent volume. Populated by the system. Read-only. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent-volumes</TD></TR>
</TBODY>
</TABLE>
<H3 id="persistentvolumespec-v1-core">PersistentVolumeSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolume-v1-core">PersistentVolume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>accessModes</CODE><BR /><I>string array</I></TD><TD>AccessModes contains all ways the volume can be mounted. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-modes</TD></TR>
<TR><TD><CODE>awsElasticBlockStore</CODE><BR /><I><a href="#awselasticblockstorevolumesource-v1-core">AWSElasticBlockStoreVolumeSource</a></I></TD><TD>AWSElasticBlockStore represents an AWS Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
<TR><TD><CODE>azureDisk</CODE><BR /><I><a href="#azurediskvolumesource-v1-core">AzureDiskVolumeSource</a></I></TD><TD>AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.</TD></TR>
<TR><TD><CODE>azureFile</CODE><BR /><I><a href="#azurefilepersistentvolumesource-v1-core">AzureFilePersistentVolumeSource</a></I></TD><TD>AzureFile represents an Azure File Service mount on the host and bind mount to the pod.</TD></TR>
<TR><TD><CODE>capacity</CODE><BR /><I>object</I></TD><TD>A description of the persistent volume&#39;s resources and capacity. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#capacity</TD></TR>
<TR><TD><CODE>cephfs</CODE><BR /><I><a href="#cephfspersistentvolumesource-v1-core">CephFSPersistentVolumeSource</a></I></TD><TD>CephFS represents a Ceph FS mount on the host that shares a pod&#39;s lifetime</TD></TR>
<TR><TD><CODE>cinder</CODE><BR /><I><a href="#cinderpersistentvolumesource-v1-core">CinderPersistentVolumeSource</a></I></TD><TD>Cinder represents a cinder volume attached and mounted on kubelets host machine More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>claimRef</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>ClaimRef is part of a bi-directional binding between PersistentVolume and PersistentVolumeClaim. Expected to be non-nil when bound. claim.VolumeName is the authoritative bind between PV and PVC. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#binding</TD></TR>
<TR><TD><CODE>csi</CODE><BR /><I><a href="#csipersistentvolumesource-v1-core">CSIPersistentVolumeSource</a></I></TD><TD>CSI represents storage that handled by an external CSI driver (Beta feature).</TD></TR>
<TR><TD><CODE>fc</CODE><BR /><I><a href="#fcvolumesource-v1-core">FCVolumeSource</a></I></TD><TD>FC represents a Fibre Channel resource that is attached to a kubelet&#39;s host machine and then exposed to the pod.</TD></TR>
<TR><TD><CODE>flexVolume</CODE><BR /><I><a href="#flexpersistentvolumesource-v1-core">FlexPersistentVolumeSource</a></I></TD><TD>FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.</TD></TR>
<TR><TD><CODE>flocker</CODE><BR /><I><a href="#flockervolumesource-v1-core">FlockerVolumeSource</a></I></TD><TD>Flocker represents a Flocker volume attached to a kubelet&#39;s host machine and exposed to the pod for its usage. This depends on the Flocker control service being running</TD></TR>
<TR><TD><CODE>gcePersistentDisk</CODE><BR /><I><a href="#gcepersistentdiskvolumesource-v1-core">GCEPersistentDiskVolumeSource</a></I></TD><TD>GCEPersistentDisk represents a GCE Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. Provisioned by an admin. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
<TR><TD><CODE>glusterfs</CODE><BR /><I><a href="#glusterfsvolumesource-v1-core">GlusterfsVolumeSource</a></I></TD><TD>Glusterfs represents a Glusterfs volume that is attached to a host and exposed to the pod. Provisioned by an admin. More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md</TD></TR>
<TR><TD><CODE>hostPath</CODE><BR /><I><a href="#hostpathvolumesource-v1-core">HostPathVolumeSource</a></I></TD><TD>HostPath represents a directory on the host. Provisioned by a developer or tester. This is useful for single-node development and testing only! On-host storage is not supported in any way and WILL NOT WORK in a multi-node cluster. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath</TD></TR>
<TR><TD><CODE>iscsi</CODE><BR /><I><a href="#iscsipersistentvolumesource-v1-core">ISCSIPersistentVolumeSource</a></I></TD><TD>ISCSI represents an ISCSI Disk resource that is attached to a kubelet&#39;s host machine and then exposed to the pod. Provisioned by an admin.</TD></TR>
<TR><TD><CODE>local</CODE><BR /><I><a href="#localvolumesource-v1-core">LocalVolumeSource</a></I></TD><TD>Local represents directly-attached storage with node affinity</TD></TR>
<TR><TD><CODE>mountOptions</CODE><BR /><I>string array</I></TD><TD>A list of mount options, e.g. [&#34;ro&#34;, &#34;soft&#34;]. Not validated - mount will simply fail if one is invalid. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#mount-options</TD></TR>
<TR><TD><CODE>nfs</CODE><BR /><I><a href="#nfsvolumesource-v1-core">NFSVolumeSource</a></I></TD><TD>NFS represents an NFS mount on the host. Provisioned by an admin. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
<TR><TD><CODE>nodeAffinity</CODE><BR /><I><a href="#volumenodeaffinity-v1-core">VolumeNodeAffinity</a></I></TD><TD>NodeAffinity defines constraints that limit what nodes this volume can be accessed from. This field influences the scheduling of pods that use this volume.</TD></TR>
<TR><TD><CODE>persistentVolumeReclaimPolicy</CODE><BR /><I>string</I></TD><TD>What happens to a persistent volume when released from its claim. Valid options are Retain (default for manually created PersistentVolumes), Delete (default for dynamically provisioned PersistentVolumes), and Recycle (deprecated). Recycle must be supported by the volume plugin underlying this PersistentVolume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#reclaiming</TD></TR>
<TR><TD><CODE>photonPersistentDisk</CODE><BR /><I><a href="#photonpersistentdiskvolumesource-v1-core">PhotonPersistentDiskVolumeSource</a></I></TD><TD>PhotonPersistentDisk represents a PhotonController persistent disk attached and mounted on kubelets host machine</TD></TR>
<TR><TD><CODE>portworxVolume</CODE><BR /><I><a href="#portworxvolumesource-v1-core">PortworxVolumeSource</a></I></TD><TD>PortworxVolume represents a portworx volume attached and mounted on kubelets host machine</TD></TR>
<TR><TD><CODE>quobyte</CODE><BR /><I><a href="#quobytevolumesource-v1-core">QuobyteVolumeSource</a></I></TD><TD>Quobyte represents a Quobyte mount on the host that shares a pod&#39;s lifetime</TD></TR>
<TR><TD><CODE>rbd</CODE><BR /><I><a href="#rbdpersistentvolumesource-v1-core">RBDPersistentVolumeSource</a></I></TD><TD>RBD represents a Rados Block Device mount on the host that shares a pod&#39;s lifetime. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md</TD></TR>
<TR><TD><CODE>scaleIO</CODE><BR /><I><a href="#scaleiopersistentvolumesource-v1-core">ScaleIOPersistentVolumeSource</a></I></TD><TD>ScaleIO represents a ScaleIO persistent volume attached and mounted on Kubernetes nodes.</TD></TR>
<TR><TD><CODE>storageClassName</CODE><BR /><I>string</I></TD><TD>Name of StorageClass to which this persistent volume belongs. Empty value means that this volume does not belong to any StorageClass.</TD></TR>
<TR><TD><CODE>storageos</CODE><BR /><I><a href="#storageospersistentvolumesource-v1-core">StorageOSPersistentVolumeSource</a></I></TD><TD>StorageOS represents a StorageOS volume that is attached to the kubelet&#39;s host machine and mounted into the pod More info: https://releases.k8s.io/HEAD/examples/volumes/storageos/README.md</TD></TR>
<TR><TD><CODE>volumeMode</CODE><BR /><I>string</I></TD><TD>volumeMode defines if a volume is intended to be used with a formatted filesystem or to remain in raw block state. Value of Filesystem is implied when not included in spec. This is an alpha feature and may change in the future.</TD></TR>
<TR><TD><CODE>vsphereVolume</CODE><BR /><I><a href="#vspherevirtualdiskvolumesource-v1-core">VsphereVirtualDiskVolumeSource</a></I></TD><TD>VsphereVolume represents a vSphere volume attached and mounted on kubelets host machine</TD></TR>
</TBODY>
</TABLE>
<H3 id="persistentvolumestatus-v1-core">PersistentVolumeStatus v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolume-v1-core">PersistentVolume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human-readable message indicating details about why the volume is in this state.</TD></TR>
<TR><TD><CODE>phase</CODE><BR /><I>string</I></TD><TD>Phase indicates if a volume is available, bound to a claim, or released by a claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#phase</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Reason is a brief CamelCase string that describes any failure and is meant for machine parsing and tidy display in the CLI.</TD></TR>
</TBODY>
</TABLE>
<H3 id="persistentvolumelist-v1-core">PersistentVolumeList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#persistentvolume-v1-core">PersistentVolume</a> array</I></TD><TD>List of persistent volumes. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-persistentvolume-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-persistentvolume-v1-core">Create</H2>
<P>create a PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/persistentvolumes</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-persistentvolume-v1-core">Patch</H2>
<P>partially update the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/persistentvolumes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-persistentvolume-v1-core">Replace</H2>
<P>replace the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/persistentvolumes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-persistentvolume-v1-core">Delete</H2>
<P>delete a PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/persistentvolumes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-persistentvolume-v1-core">Delete Collection</H2>
<P>delete collection of PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/persistentvolumes</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-persistentvolume-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-persistentvolume-v1-core">Read</H2>
<P>read the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/persistentvolumes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-persistentvolume-v1-core">List</H2>
<P>list or watch objects of kind PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/persistentvolumes</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolumelist-v1-core">PersistentVolumeList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-persistentvolume-v1-core">Watch</H2>
<P>watch changes to an object of kind PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/persistentvolumes/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-persistentvolume-v1-core">Watch List</H2>
<P>watch individual changes to a list of PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/persistentvolumes</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-persistentvolume-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-persistentvolume-v1-core">Patch Status</H2>
<P>partially update status of the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/persistentvolumes/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-persistentvolume-v1-core">Read Status</H2>
<P>read status of the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/persistentvolumes/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-persistentvolume-v1-core">Replace Status</H2>
<P>replace status of the specified PersistentVolume</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/persistentvolumes/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PersistentVolume</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#persistentvolume-v1-core">PersistentVolume</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="resourcequota-v1-core">ResourceQuota v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceQuota</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourcequotalist-v1-core">ResourceQuotaList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#resourcequotaspec-v1-core">ResourceQuotaSpec</a></I></TD><TD>Spec defines the desired quota. https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#resourcequotastatus-v1-core">ResourceQuotaStatus</a></I></TD><TD>Status defines the actual enforced quota and its current usage. https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="resourcequotaspec-v1-core">ResourceQuotaSpec v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourcequota-v1-core">ResourceQuota [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>hard</CODE><BR /><I>object</I></TD><TD>hard is the set of desired hard limits for each named resource. More info: https://kubernetes.io/docs/concepts/policy/resource-quotas/</TD></TR>
<TR><TD><CODE>scopeSelector</CODE><BR /><I><a href="#scopeselector-v1-core">ScopeSelector</a></I></TD><TD>scopeSelector is also a collection of filters like scopes that must match each object tracked by a quota but expressed using ScopeSelectorOperator in combination with possible values. For a resource to match, both scopes AND scopeSelector (if specified in spec), must be matched.</TD></TR>
<TR><TD><CODE>scopes</CODE><BR /><I>string array</I></TD><TD>A collection of filters that must match each object tracked by a quota. If not specified, the quota matches all objects.</TD></TR>
</TBODY>
</TABLE>
<H3 id="resourcequotastatus-v1-core">ResourceQuotaStatus v1 core</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourcequota-v1-core">ResourceQuota [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>hard</CODE><BR /><I>object</I></TD><TD>Hard is the set of enforced hard limits for each named resource. More info: https://kubernetes.io/docs/concepts/policy/resource-quotas/</TD></TR>
<TR><TD><CODE>used</CODE><BR /><I>object</I></TD><TD>Used is the current observed total usage of the resource in the namespace.</TD></TR>
</TBODY>
</TABLE>
<H3 id="resourcequotalist-v1-core">ResourceQuotaList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#resourcequota-v1-core">ResourceQuota</a> array</I></TD><TD>Items is a list of ResourceQuota objects. More info: https://kubernetes.io/docs/concepts/policy/resource-quotas/</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-resourcequota-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-resourcequota-v1-core">Create</H2>
<P>create a ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/resourcequotas</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-resourcequota-v1-core">Patch</H2>
<P>partially update the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-resourcequota-v1-core">Replace</H2>
<P>replace the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-resourcequota-v1-core">Delete</H2>
<P>delete a ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-resourcequota-v1-core">Delete Collection</H2>
<P>delete collection of ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/resourcequotas</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-resourcequota-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-resourcequota-v1-core">Read</H2>
<P>read the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/resourcequotas/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-resourcequota-v1-core">List</H2>
<P>list or watch objects of kind ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/resourcequotas</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourcequotalist-v1-core">ResourceQuotaList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-resourcequota-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/resourcequotas</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourcequotalist-v1-core">ResourceQuotaList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-resourcequota-v1-core">Watch</H2>
<P>watch changes to an object of kind ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/resourcequotas/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-resourcequota-v1-core">Watch List</H2>
<P>watch individual changes to a list of ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/resourcequotas</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-resourcequota-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/resourcequotas</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-resourcequota-v1-core-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-resourcequota-v1-core">Patch Status</H2>
<P>partially update status of the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-resourcequota-v1-core">Read Status</H2>
<P>read status of the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-resourcequota-v1-core">Replace Status</H2>
<P>replace status of the specified ResourceQuota</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ResourceQuota</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#resourcequota-v1-core">ResourceQuota</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="role-v1-rbac-authorization-k8s-io">Role v1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Role</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#role-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
<a href="#role-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#rolelist-v1-rbac-authorization-k8s-io">RoleList [rbac/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyrule-v1-rbac-authorization-k8s-io">PolicyRule</a> array</I></TD><TD>Rules holds all the PolicyRules for this Role</TD></TR>
</TBODY>
</TABLE>
<H3 id="rolelist-v1-rbac-authorization-k8s-io">RoleList v1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a> array</I></TD><TD>Items is a list of Roles</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-role-v1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-role-v1-rbac-authorization-k8s-io">Create</H2>
<P>create a Role</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-role-v1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified Role</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-role-v1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified Role</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-role-v1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a Role</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-role-v1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of Role</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-role-v1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-role-v1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-role-v1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolelist-v1-rbac-authorization-k8s-io">RoleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-role-v1-rbac-authorization-k8s-io">List All Namespaces</H2>
<P>list or watch objects of kind Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/roles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolelist-v1-rbac-authorization-k8s-io">RoleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-role-v1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-role-v1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-role-v1-rbac-authorization-k8s-io">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/roles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="rolebinding-v1-rbac-authorization-k8s-io">RoleBinding v1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RoleBinding</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
<a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList [rbac/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>roleRef</CODE><BR /><I><a href="#roleref-v1-rbac-authorization-k8s-io">RoleRef</a></I></TD><TD>RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.</TD></TR>
<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1-rbac-authorization-k8s-io">Subject</a> array</I></TD><TD>Subjects holds references to the objects the role applies to.</TD></TR>
</TBODY>
</TABLE>
<H3 id="rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList v1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a> array</I></TD><TD>Items is a list of RoleBindings</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-rolebinding-v1-rbac-authorization-k8s-io">Create</H2>
<P>create a RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-rolebinding-v1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-rolebinding-v1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-rolebinding-v1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-rolebinding-v1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-rolebinding-v1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-rolebinding-v1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-rolebinding-v1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io">List All Namespaces</H2>
<P>list or watch objects of kind RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/rolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-rolebinding-v1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-rolebinding-v1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-rolebinding-v1-rbac-authorization-k8s-io">Watch List All Namespaces</H2>
<P>watch individual changes to a list of RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1/watch/rolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview v1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SelfSubjectAccessReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#selfsubjectaccessreview-v1beta1-authorization-k8s-io">v1beta1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#selfsubjectaccessreviewspec-v1-authorization-k8s-io">SelfSubjectAccessReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated. user and groups must be empty</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectaccessreviewstatus-v1-authorization-k8s-io">SubjectAccessReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request is allowed or not</TD></TR>
</TBODY>
</TABLE>
<H3 id="selfsubjectaccessreviewspec-v1-authorization-k8s-io">SelfSubjectAccessReviewSpec v1 authorization</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>nonResourceAttributes</CODE><BR /><I><a href="#nonresourceattributes-v1-authorization-k8s-io">NonResourceAttributes</a></I></TD><TD>NonResourceAttributes describes information for a non-resource access request</TD></TR>
<TR><TD><CODE>resourceAttributes</CODE><BR /><I><a href="#resourceattributes-v1-authorization-k8s-io">ResourceAttributes</a></I></TD><TD>ResourceAuthorizationAttributes describes information for a resource access request</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-selfsubjectaccessreview-v1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-selfsubjectaccessreview-v1-authorization-k8s-io">Create</H2>
<P>create a SelfSubjectAccessReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authorization.k8s.io/v1/selfsubjectaccessreviews</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H1 id="selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview v1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SelfSubjectRulesReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#selfsubjectrulesreview-v1beta1-authorization-k8s-io">v1beta1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#selfsubjectrulesreviewspec-v1-authorization-k8s-io">SelfSubjectRulesReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectrulesreviewstatus-v1-authorization-k8s-io">SubjectRulesReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates the set of actions a user can perform.</TD></TR>
</TBODY>
</TABLE>
<H3 id="selfsubjectrulesreviewspec-v1-authorization-k8s-io">SelfSubjectRulesReviewSpec v1 authorization</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace to evaluate rules for. Required.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-selfsubjectrulesreview-v1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-selfsubjectrulesreview-v1-authorization-k8s-io">Create</H2>
<P>create a SelfSubjectRulesReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authorization.k8s.io/v1/selfsubjectrulesreviews</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H1 id="serviceaccount-v1-core">ServiceAccount v1 core</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceAccount</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#serviceaccountlist-v1-core">ServiceAccountList [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>automountServiceAccountToken</CODE><BR /><I>boolean</I></TD><TD>AutomountServiceAccountToken indicates whether pods running as this service account should have an API token automatically mounted. Can be overridden at the pod level.</TD></TR>
<TR><TD><CODE>imagePullSecrets</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a> array</I></TD><TD>ImagePullSecrets is a list of references to secrets in the same namespace to use for pulling any images in pods that reference this ServiceAccount. ImagePullSecrets are distinct from Secrets because Secrets can be mounted in the pod, but ImagePullSecrets are only accessed by the kubelet. More info: https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>secrets</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Secrets is the list of secrets allowed to be used by pods running using this ServiceAccount. More info: https://kubernetes.io/docs/concepts/configuration/secret</TD></TR>
</TBODY>
</TABLE>
<H3 id="serviceaccountlist-v1-core">ServiceAccountList v1 core</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#serviceaccount-v1-core">ServiceAccount</a> array</I></TD><TD>List of ServiceAccounts. More info: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-serviceaccount-v1-core-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-serviceaccount-v1-core">Create</H2>
<P>create a ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>POST /api/v1/namespaces/{namespace}/serviceaccounts</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-serviceaccount-v1-core">Patch</H2>
<P>partially update the specified ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>PATCH /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-serviceaccount-v1-core">Replace</H2>
<P>replace the specified ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>PUT /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-serviceaccount-v1-core">Delete</H2>
<P>delete a ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-serviceaccount-v1-core">Delete Collection</H2>
<P>delete collection of ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>DELETE /api/v1/namespaces/{namespace}/serviceaccounts</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-serviceaccount-v1-core-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-serviceaccount-v1-core">Read</H2>
<P>read the specified ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/serviceaccounts/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#serviceaccount-v1-core">ServiceAccount</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-serviceaccount-v1-core">List</H2>
<P>list or watch objects of kind ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/namespaces/{namespace}/serviceaccounts</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#serviceaccountlist-v1-core">ServiceAccountList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-serviceaccount-v1-core">List All Namespaces</H2>
<P>list or watch objects of kind ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/serviceaccounts</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#serviceaccountlist-v1-core">ServiceAccountList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-serviceaccount-v1-core">Watch</H2>
<P>watch changes to an object of kind ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/serviceaccounts/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ServiceAccount</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-serviceaccount-v1-core">Watch List</H2>
<P>watch individual changes to a list of ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/namespaces/{namespace}/serviceaccounts</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-serviceaccount-v1-core">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ServiceAccount</P>
<H3>HTTP Request</H3>
<CODE>GET /api/v1/watch/serviceaccounts</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview v1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SubjectAccessReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#subjectaccessreview-v1beta1-authorization-k8s-io">v1beta1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectaccessreviewstatus-v1-authorization-k8s-io">SubjectAccessReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request is allowed or not</TD></TR>
</TBODY>
</TABLE>
<H3 id="subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec v1 authorization</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview [authorization/v1]</a></LI>
<LI><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extra</CODE><BR /><I>object</I></TD><TD>Extra corresponds to the user.Info.GetExtra() method from the authenticator. Since that is input to the authorizer it needs a reflection here.</TD></TR>
<TR><TD><CODE>groups</CODE><BR /><I>string array</I></TD><TD>Groups is the groups you&#39;re testing for.</TD></TR>
<TR><TD><CODE>nonResourceAttributes</CODE><BR /><I><a href="#nonresourceattributes-v1-authorization-k8s-io">NonResourceAttributes</a></I></TD><TD>NonResourceAttributes describes information for a non-resource access request</TD></TR>
<TR><TD><CODE>resourceAttributes</CODE><BR /><I><a href="#resourceattributes-v1-authorization-k8s-io">ResourceAttributes</a></I></TD><TD>ResourceAuthorizationAttributes describes information for a resource access request</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID information about the requesting user.</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>User is the user you&#39;re testing for. If you specify &#34;User&#34; but not &#34;Groups&#34;, then is it interpreted as &#34;What if User were not a member of any groups</TD></TR>
</TBODY>
</TABLE>
<H3 id="subjectaccessreviewstatus-v1-authorization-k8s-io">SubjectAccessReviewStatus v1 authorization</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview [authorization/v1]</a></LI>
<LI><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview [authorization/v1]</a></LI>
<LI><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowed</CODE><BR /><I>boolean</I></TD><TD>Allowed is required. True if the action would be allowed, false otherwise.</TD></TR>
<TR><TD><CODE>denied</CODE><BR /><I>boolean</I></TD><TD>Denied is optional. True if the action would be denied, otherwise false. If both allowed is false and denied is false, then the authorizer has no opinion on whether to authorize the action. Denied may not be true if Allowed is true.</TD></TR>
<TR><TD><CODE>evaluationError</CODE><BR /><I>string</I></TD><TD>EvaluationError is an indication that some error occurred during the authorization check. It is entirely possible to get an error and be able to continue determine authorization status in spite of it. For instance, RBAC can be missing a role, but enough roles are still present and bound to reason about the request.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Reason is optional. It indicates why a request was allowed or denied.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-subjectaccessreview-v1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-subjectaccessreview-v1-authorization-k8s-io">Create</H2>
<P>create a SubjectAccessReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authorization.k8s.io/v1/subjectaccessreviews</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="tokenreview-v1-authentication-k8s-io">TokenReview v1 authentication.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TokenReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#tokenreview-v1beta1-authentication-k8s-io">v1beta1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#tokenreviewspec-v1-authentication-k8s-io">TokenReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#tokenreviewstatus-v1-authentication-k8s-io">TokenReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request can be authenticated.</TD></TR>
</TBODY>
</TABLE>
<H3 id="tokenreviewspec-v1-authentication-k8s-io">TokenReviewSpec v1 authentication</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#tokenreview-v1-authentication-k8s-io">TokenReview [authentication/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>token</CODE><BR /><I>string</I></TD><TD>Token is the opaque bearer token.</TD></TR>
</TBODY>
</TABLE>
<H3 id="tokenreviewstatus-v1-authentication-k8s-io">TokenReviewStatus v1 authentication</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#tokenreview-v1-authentication-k8s-io">TokenReview [authentication/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authenticated</CODE><BR /><I>boolean</I></TD><TD>Authenticated indicates that the token was associated with a known user.</TD></TR>
<TR><TD><CODE>error</CODE><BR /><I>string</I></TD><TD>Error indicates that the token couldn&#39;t be checked</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I><a href="#userinfo-v1-authentication-k8s-io">UserInfo</a></I></TD><TD>User is the UserInfo associated with the provided token.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-tokenreview-v1-authentication-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-tokenreview-v1-authentication-k8s-io">Create</H2>
<P>create a TokenReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authentication.k8s.io/v1/tokenreviews</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#tokenreview-v1-authentication-k8s-io">TokenReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#tokenreview-v1-authentication-k8s-io">TokenReview</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#tokenreview-v1-authentication-k8s-io">TokenReview</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#tokenreview-v1-authentication-k8s-io">TokenReview</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="networkpolicy-v1-networking-k8s-io">NetworkPolicy v1 networking.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicy-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicylist-v1-networking-k8s-io">NetworkPolicyList [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec</a></I></TD><TD>Specification of the desired behavior for this NetworkPolicy.</TD></TR>
</TBODY>
</TABLE>
<H3 id="networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec v1 networking</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>egress</CODE><BR /><I><a href="#networkpolicyegressrule-v1-networking-k8s-io">NetworkPolicyEgressRule</a> array</I></TD><TD>List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8</TD></TR>
<TR><TD><CODE>ingress</CODE><BR /><I><a href="#networkpolicyingressrule-v1-networking-k8s-io">NetworkPolicyIngressRule</a> array</I></TD><TD>List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic source is the pod&#39;s local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default)</TD></TR>
<TR><TD><CODE>podSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.</TD></TR>
<TR><TD><CODE>policyTypes</CODE><BR /><I>string array</I></TD><TD>List of rule types that the NetworkPolicy relates to. Valid options are Ingress, Egress, or Ingress,Egress. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ &#34;Egress&#34; ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include &#34;Egress&#34; (since such a policy would not include an Egress section and would otherwise default to just [ &#34;Ingress&#34; ]). This field is beta-level in 1.8</TD></TR>
</TBODY>
</TABLE>
<H3 id="networkpolicylist-v1-networking-k8s-io">NetworkPolicyList v1 networking</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a> array</I></TD><TD>Items is a list of schema objects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-networkpolicy-v1-networking-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-networkpolicy-v1-networking-k8s-io">Create</H2>
<P>create a NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-networkpolicy-v1-networking-k8s-io">Patch</H2>
<P>partially update the specified NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-networkpolicy-v1-networking-k8s-io">Replace</H2>
<P>replace the specified NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-networkpolicy-v1-networking-k8s-io">Delete</H2>
<P>delete a NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-networkpolicy-v1-networking-k8s-io">Delete Collection</H2>
<P>delete collection of NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-networkpolicy-v1-networking-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-networkpolicy-v1-networking-k8s-io">Read</H2>
<P>read the specified NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-networkpolicy-v1-networking-k8s-io">List</H2>
<P>list or watch objects of kind NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicylist-v1-networking-k8s-io">NetworkPolicyList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-networkpolicy-v1-networking-k8s-io">List All Namespaces</H2>
<P>list or watch objects of kind NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/networking.k8s.io/v1/networkpolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicylist-v1-networking-k8s-io">NetworkPolicyList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-networkpolicy-v1-networking-k8s-io">Watch</H2>
<P>watch changes to an object of kind NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-networkpolicy-v1-networking-k8s-io">Watch List</H2>
<P>watch individual changes to a list of NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/networking.k8s.io/v1/watch/namespaces/{namespace}/networkpolicies</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-networkpolicy-v1-networking-k8s-io">Watch List All Namespaces</H2>
<P>watch individual changes to a list of NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/networking.k8s.io/v1/watch/networkpolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="-strong-definitions-strong-"><STRONG>DEFINITIONS</STRONG></H1>
<P>This section contains definitions for objects used in the Kubernetes APIs.</P>
<H2 id="apigroup-v1-meta">APIGroup v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIGroup</CODE></TD></TR>
</TBODY>
</TABLE>
<P>APIGroup contains the name, the supported versions, and the preferred version of a group.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apigrouplist-v1-meta">APIGroupList [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the group.</TD></TR>
<TR><TD><CODE>preferredVersion</CODE><BR /><I><a href="#groupversionfordiscovery-v1-meta">GroupVersionForDiscovery</a></I></TD><TD>preferredVersion is the version preferred by the API server, which probably is the storage version.</TD></TR>
<TR><TD><CODE>serverAddressByClientCIDRs</CODE><BR /><I><a href="#serveraddressbyclientcidr-v1-meta">ServerAddressByClientCIDR</a> array</I></TD><TD>a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.</TD></TR>
<TR><TD><CODE>versions</CODE><BR /><I><a href="#groupversionfordiscovery-v1-meta">GroupVersionForDiscovery</a> array</I></TD><TD>versions are the versions supported in this group.</TD></TR>
</TBODY>
</TABLE>
<H2 id="apiresource-v1-meta">APIResource v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIResource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>APIResource specifies the name of a resource and whether it is namespaced.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiresourcelist-v1-meta">APIResourceList [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>categories</CODE><BR /><I>string array</I></TD><TD>categories is a list of the grouped resources this resource belongs to (e.g. &#39;all&#39;)</TD></TR>
<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>group is the preferred group of the resource. Empty implies the group of the containing resource list. For subresources, this may have a different value, for example: Scale&#34;.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>kind is the kind for the resource (e.g. &#39;Foo&#39; is the kind for a resource &#39;foo&#39;)</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the plural name of the resource.</TD></TR>
<TR><TD><CODE>namespaced</CODE><BR /><I>boolean</I></TD><TD>namespaced indicates if a resource is namespaced or not.</TD></TR>
<TR><TD><CODE>shortNames</CODE><BR /><I>string array</I></TD><TD>shortNames is a list of suggested short names of the resource.</TD></TR>
<TR><TD><CODE>singularName</CODE><BR /><I>string</I></TD><TD>singularName is the singular name of the resource. This allows clients to handle plural and singular opaquely. The singularName is more correct for reporting status on a single item and both singular and plural are allowed from the kubectl CLI interface.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>verbs is a list of supported kube verbs (this includes get, list, watch, create, update, patch, delete, deletecollection, and proxy)</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>version is the preferred version of the resource. Empty implies the version of the containing resource list For subresources, this may have a different value, for example: v1 (while inside a v1beta1 version of the core resource&#39;s group)&#34;.</TD></TR>
</TBODY>
</TABLE>
<H2 id="apiservicecondition-v1-apiregistration-k8s-io">APIServiceCondition v1 apiregistration.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIServiceCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P></P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#apiservicecondition-v1beta1-apiregistration-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservicestatus-v1-apiregistration-k8s-io">APIServiceStatus [apiregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human-readable message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status is the status of the condition. Can be True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is the type of the condition.</TD></TR>
</TBODY>
</TABLE>
<H2 id="apiversions-v1-meta">APIVersions v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>APIVersions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>APIVersions lists the versions that are available, to allow clients to discover the API at /api, which is the root path of the legacy v1 API.</P>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>serverAddressByClientCIDRs</CODE><BR /><I><a href="#serveraddressbyclientcidr-v1-meta">ServerAddressByClientCIDR</a> array</I></TD><TD>a map of client CIDR to server address that is serving this group. This is to help clients reach servers in the most network-efficient way possible. Clients can use the appropriate server address as per the CIDR that they match. In case of multiple matches, clients should use the longest matching CIDR. The server returns only those CIDRs that it thinks that the client can match. For example: the master will return an internal IP CIDR only, if the client reaches the server using an internal IP. Server looks at X-Forwarded-For header or X-Real-Ip header or request.RemoteAddr (in that order) to get the client IP.</TD></TR>
<TR><TD><CODE>versions</CODE><BR /><I>string array</I></TD><TD>versions are the api versions that are available.</TD></TR>
</TBODY>
</TABLE>
<H2 id="awselasticblockstorevolumesource-v1-core">AWSElasticBlockStoreVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AWSElasticBlockStoreVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Persistent Disk resource in AWS.
An AWS EBS disk must exist before mounting to a container. The disk must also be in the same AWS zone as the kubelet. An AWS EBS disk can only be mounted as read/write once. AWS EBS volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as &#34;1&#34;. Similarly, the volume partition for /dev/sda is &#34;0&#34; (or you can leave the property empty).</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Specify &#34;true&#34; to force and set the ReadOnly property in VolumeMounts to &#34;true&#34;. If omitted, the default is &#34;false&#34;. More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>Unique ID of the persistent disk resource in AWS (Amazon EBS volume). More info: https://kubernetes.io/docs/concepts/storage/volumes#awselasticblockstore</TD></TR>
</TBODY>
</TABLE>
<H2 id="affinity-v1-core">Affinity v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Affinity</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Affinity is a group of affinity scheduling rules.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>nodeAffinity</CODE><BR /><I><a href="#nodeaffinity-v1-core">NodeAffinity</a></I></TD><TD>Describes node affinity scheduling rules for the pod.</TD></TR>
<TR><TD><CODE>podAffinity</CODE><BR /><I><a href="#podaffinity-v1-core">PodAffinity</a></I></TD><TD>Describes pod affinity scheduling rules (e.g. co-locate this pod in the same node, zone, etc. as some other pod(s)).</TD></TR>
<TR><TD><CODE>podAntiAffinity</CODE><BR /><I><a href="#podantiaffinity-v1-core">PodAntiAffinity</a></I></TD><TD>Describes pod anti-affinity scheduling rules (e.g. avoid putting this pod in the same node, zone, etc. as some other pod(s)).</TD></TR>
</TBODY>
</TABLE>
<H2 id="aggregationrule-v1-rbac-authorization-k8s-io">AggregationRule v1 rbac.authorization.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AggregationRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AggregationRule describes how to locate ClusterRoles to aggregate into the ClusterRole</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#aggregationrule-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
<a href="#aggregationrule-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole [rbac/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>clusterRoleSelectors</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a> array</I></TD><TD>ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole&#39;s permissions will be added</TD></TR>
</TBODY>
</TABLE>
<H2 id="allowedflexvolume-v1beta1-extensions">AllowedFlexVolume v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AllowedFlexVolume</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AllowedFlexVolume represents a single Flexvolume that is allowed to be used. Deprecated: use AllowedFlexVolume from policy API Group instead.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-extensions">PodSecurityPolicySpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>driver is the name of the Flexvolume driver.</TD></TR>
</TBODY>
</TABLE>
<H2 id="allowedhostpath-v1beta1-extensions">AllowedHostPath v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AllowedHostPath</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AllowedHostPath defines the host volume conditions that will be enabled by a policy for pods to use. It requires the path prefix to be defined. Deprecated: use AllowedHostPath from policy API Group instead.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-extensions">PodSecurityPolicySpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pathPrefix</CODE><BR /><I>string</I></TD><TD>pathPrefix is the path prefix that the host volume must match. It does not support `*`. Trailing slashes are trimmed when validating the path prefix with a host path. Examples: `/foo` would allow `/foo`, `/foo/` and `/foo/bar` `/foo` would not allow `/food` or `/etc/foo`</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>when set to true, will allow host volumes matching the pathPrefix only if all volume mounts are readOnly.</TD></TR>
</TBODY>
</TABLE>
<H2 id="attachedvolume-v1-core">AttachedVolume v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AttachedVolume</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AttachedVolume describes a volume attached to a node</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>devicePath</CODE><BR /><I>string</I></TD><TD>DevicePath represents the device path where the volume should be available</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the attached volume</TD></TR>
</TBODY>
</TABLE>
<H2 id="azurediskvolumesource-v1-core">AzureDiskVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AzureDiskVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AzureDisk represents an Azure Data Disk mount on the host and bind mount to the pod.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>cachingMode</CODE><BR /><I>string</I></TD><TD>Host Caching mode: None, Read Only, Read Write.</TD></TR>
<TR><TD><CODE>diskName</CODE><BR /><I>string</I></TD><TD>The Name of the data disk in the blob storage</TD></TR>
<TR><TD><CODE>diskURI</CODE><BR /><I>string</I></TD><TD>The URI the data disk in the blob storage</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Expected values Shared: multiple blob disks per storage account Dedicated: single blob disk per storage account Managed: azure managed data disk (only in managed availability set). defaults to shared</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
</TBODY>
</TABLE>
<H2 id="azurefilepersistentvolumesource-v1-core">AzureFilePersistentVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AzureFilePersistentVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AzureFile represents an Azure File Service mount on the host and bind mount to the pod.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>the name of secret that contains Azure Storage Account Name and Key</TD></TR>
<TR><TD><CODE>secretNamespace</CODE><BR /><I>string</I></TD><TD>the namespace of the secret that contains Azure Storage Account Name and Key default is the same as the Pod</TD></TR>
<TR><TD><CODE>shareName</CODE><BR /><I>string</I></TD><TD>Share Name</TD></TR>
</TBODY>
</TABLE>
<H2 id="azurefilevolumesource-v1-core">AzureFileVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>AzureFileVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>AzureFile represents an Azure File Service mount on the host and bind mount to the pod.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>the name of secret that contains Azure Storage Account Name and Key</TD></TR>
<TR><TD><CODE>shareName</CODE><BR /><I>string</I></TD><TD>Share Name</TD></TR>
</TBODY>
</TABLE>
<H2 id="csipersistentvolumesource-v1-core">CSIPersistentVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CSIPersistentVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents storage that is managed by an external CSI volume driver (Beta feature)</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>controllerPublishSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>ControllerPublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI ControllerPublishVolume and ControllerUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.</TD></TR>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver is the name of the driver to use for this volume. Required.</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>nodePublishSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>NodePublishSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodePublishVolume and NodeUnpublishVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.</TD></TR>
<TR><TD><CODE>nodeStageSecretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>NodeStageSecretRef is a reference to the secret object containing sensitive information to pass to the CSI driver to complete the CSI NodeStageVolume and NodeStageVolume and NodeUnstageVolume calls. This field is optional, and may be empty if no secret is required. If the secret object contains more than one secret, all secrets are passed.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: The value to pass to ControllerPublishVolumeRequest. Defaults to false (read/write).</TD></TR>
<TR><TD><CODE>volumeAttributes</CODE><BR /><I>object</I></TD><TD>Attributes of the volume to publish.</TD></TR>
<TR><TD><CODE>volumeHandle</CODE><BR /><I>string</I></TD><TD>VolumeHandle is the unique volume name returned by the CSI volume plugin’s CreateVolume to refer to the volume on all subsequent calls. Required.</TD></TR>
</TBODY>
</TABLE>
<H2 id="capabilities-v1-core">Capabilities v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Capabilities</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Adds and removes POSIX capabilities from running containers.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#securitycontext-v1-core">SecurityContext [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>add</CODE><BR /><I>string array</I></TD><TD>Added capabilities</TD></TR>
<TR><TD><CODE>drop</CODE><BR /><I>string array</I></TD><TD>Removed capabilities</TD></TR>
</TBODY>
</TABLE>
<H2 id="cephfspersistentvolumesource-v1-core">CephFSPersistentVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CephFSPersistentVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>Required: Monitors is a collection of Ceph monitors More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Optional: Used as the mounted root, rather than the full Ceph tree, default is /</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>secretFile</CODE><BR /><I>string</I></TD><TD>Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>Optional: User is the rados user name, default is admin More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
</TBODY>
</TABLE>
<H2 id="cephfsvolumesource-v1-core">CephFSVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CephFSVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Ceph Filesystem mount that lasts the lifetime of a pod Cephfs volumes do not support ownership management or SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>Required: Monitors is a collection of Ceph monitors More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Optional: Used as the mounted root, rather than the full Ceph tree, default is /</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>secretFile</CODE><BR /><I>string</I></TD><TD>Optional: SecretFile is the path to key ring for User, default is /etc/ceph/user.secret More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>Optional: SecretRef is reference to the authentication secret for User, default is empty. More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>Optional: User is the rados user name, default is admin More info: https://releases.k8s.io/HEAD/examples/volumes/cephfs/README.md#how-to-use-it</TD></TR>
</TBODY>
</TABLE>
<H2 id="certificatesigningrequestcondition-v1beta1-certificates-k8s-io">CertificateSigningRequestCondition v1beta1 certificates.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>certificates.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CertificateSigningRequestCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P></P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#certificatesigningrequeststatus-v1beta1-certificates-k8s-io">CertificateSigningRequestStatus [certificates/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastUpdateTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>timestamp for the last update to this condition</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>human readable message with details about the request state</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>brief reason for the request state</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>request approval state, currently Approved or Denied.</TD></TR>
</TBODY>
</TABLE>
<H2 id="cinderpersistentvolumesource-v1-core">CinderPersistentVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CinderPersistentVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>Optional: points to a secret object containing parameters used to connect to OpenStack.</TD></TR>
<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>volume id used to identify the volume in cinder More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md</TD></TR>
</TBODY>
</TABLE>
<H2 id="cindervolumesource-v1-core">CinderVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CinderVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a cinder volume resource in Openstack. A Cinder volume must exist before mounting to a container. The volume must also be in the same region as the kubelet. Cinder volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>Optional: points to a secret object containing parameters used to connect to OpenStack.</TD></TR>
<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>volume id used to identify the volume in cinder More info: https://releases.k8s.io/HEAD/examples/mysql-cinder-pd/README.md</TD></TR>
</TBODY>
</TABLE>
<H2 id="clientipconfig-v1-core">ClientIPConfig v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ClientIPConfig</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ClientIPConfig represents the configurations of Client IP based session affinity.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#sessionaffinityconfig-v1-core">SessionAffinityConfig [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>timeoutSeconds</CODE><BR /><I>integer</I></TD><TD>timeoutSeconds specifies the seconds of ClientIP type session sticky time. The value must be &gt;0 &amp;&amp; &lt;=86400(for 1 day) if ServiceAffinity == &#34;ClientIP&#34;. Default value is 10800(for 3 hours).</TD></TR>
</TBODY>
</TABLE>
<H2 id="componentcondition-v1-core">ComponentCondition v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ComponentCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Information about the condition of a component.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#componentstatus-v1-core">ComponentStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>error</CODE><BR /><I>string</I></TD><TD>Condition error code for a component. For example, a health check error code.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message about the condition for a component. For example, information about a health check.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition for a component. Valid values for &#34;Healthy&#34;: &#34;True&#34;, &#34;False&#34;, or &#34;Unknown&#34;.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of condition for a component. Valid value: &#34;Healthy&#34;</TD></TR>
</TBODY>
</TABLE>
<H2 id="configmapenvsource-v1-core">ConfigMapEnvSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapEnvSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ConfigMapEnvSource selects a ConfigMap to populate the environment variables with.
The contents of the target ConfigMap&#39;s Data field will represent the key-value pairs as environment variables.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#envfromsource-v1-core">EnvFromSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the ConfigMap must be defined</TD></TR>
</TBODY>
</TABLE>
<H2 id="configmapkeyselector-v1-core">ConfigMapKeySelector v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapKeySelector</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Selects a key from a ConfigMap.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#envvarsource-v1-core">EnvVarSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The key to select.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the ConfigMap or it&#39;s key must be defined</TD></TR>
</TBODY>
</TABLE>
<H2 id="configmapnodeconfigsource-v1-core">ConfigMapNodeConfigSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapNodeConfigSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ConfigMapNodeConfigSource contains the information to reference a ConfigMap as a config source for the Node.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodeconfigsource-v1-core">NodeConfigSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>kubeletConfigKey</CODE><BR /><I>string</I></TD><TD>KubeletConfigKey declares which key of the referenced ConfigMap corresponds to the KubeletConfiguration structure This field is required in all cases.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the metadata.name of the referenced ConfigMap. This field is required in all cases.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the metadata.namespace of the referenced ConfigMap. This field is required in all cases.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>ResourceVersion is the metadata.ResourceVersion of the referenced ConfigMap. This field is forbidden in Node.Spec, and required in Node.Status.</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID is the metadata.UID of the referenced ConfigMap. This field is forbidden in Node.Spec, and required in Node.Status.</TD></TR>
</TBODY>
</TABLE>
<H2 id="configmapprojection-v1-core">ConfigMapProjection v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapProjection</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Adapts a ConfigMap into a projected volume.
The contents of the target ConfigMap&#39;s Data field will be presented in a projected volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. Note that this is identical to a configmap volume source without the default mode.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeprojection-v1-core">VolumeProjection [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>items</CODE><BR /><I><a href="#keytopath-v1-core">KeyToPath</a> array</I></TD><TD>If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the ConfigMap or it&#39;s keys must be defined</TD></TR>
</TBODY>
</TABLE>
<H2 id="configmapvolumesource-v1-core">ConfigMapVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ConfigMapVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Adapts a ConfigMap into a volume.
The contents of the target ConfigMap&#39;s Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>defaultMode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#keytopath-v1-core">KeyToPath</a> array</I></TD><TD>If unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the ConfigMap or it&#39;s keys must be defined</TD></TR>
</TBODY>
</TABLE>
<H2 id="containerimage-v1-core">ContainerImage v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerImage</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Describe a container image</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>names</CODE><BR /><I>string array</I></TD><TD>Names by which this image is known. e.g. [&#34;k8s.gcr.io/hyperkube:v1.0.7&#34;, &#34;dockerhub.io/google_containers/hyperkube:v1.0.7&#34;]</TD></TR>
<TR><TD><CODE>sizeBytes</CODE><BR /><I>integer</I></TD><TD>The size of the image in bytes.</TD></TR>
</TBODY>
</TABLE>
<H2 id="containerport-v1-core">ContainerPort v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerPort</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ContainerPort represents a network port in a single container.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#container-v1-core">Container [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>containerPort</CODE><BR /><I>integer</I></TD><TD>Number of port to expose on the pod&#39;s IP address. This must be a valid port number, 0 &lt; x &lt; 65536.</TD></TR>
<TR><TD><CODE>hostIP</CODE><BR /><I>string</I></TD><TD>What host IP to bind the external port to.</TD></TR>
<TR><TD><CODE>hostPort</CODE><BR /><I>integer</I></TD><TD>Number of port to expose on the host. If specified, this must be a valid port number, 0 &lt; x &lt; 65536. If HostNetwork is specified, this must match ContainerPort. Most containers do not need this.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>If specified, this must be an IANA_SVC_NAME and unique within the pod. Each named port in a pod must have a unique name. Name for the port that can be referred to by services.</TD></TR>
<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>Protocol for port. Must be UDP or TCP. Defaults to &#34;TCP&#34;.</TD></TR>
</TBODY>
</TABLE>
<H2 id="containerstate-v1-core">ContainerState v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerState</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ContainerState holds a possible state of container. Only one of its members may be specified. If none of them is specified, the default one is ContainerStateWaiting.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#containerstatus-v1-core">ContainerStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>running</CODE><BR /><I><a href="#containerstaterunning-v1-core">ContainerStateRunning</a></I></TD><TD>Details about a running container</TD></TR>
<TR><TD><CODE>terminated</CODE><BR /><I><a href="#containerstateterminated-v1-core">ContainerStateTerminated</a></I></TD><TD>Details about a terminated container</TD></TR>
<TR><TD><CODE>waiting</CODE><BR /><I><a href="#containerstatewaiting-v1-core">ContainerStateWaiting</a></I></TD><TD>Details about a waiting container</TD></TR>
</TBODY>
</TABLE>
<H2 id="containerstaterunning-v1-core">ContainerStateRunning v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerStateRunning</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ContainerStateRunning is a running state of a container.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#containerstate-v1-core">ContainerState [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>startedAt</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time at which the container was last (re-)started</TD></TR>
</TBODY>
</TABLE>
<H2 id="containerstateterminated-v1-core">ContainerStateTerminated v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerStateTerminated</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ContainerStateTerminated is a terminated state of a container.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#containerstate-v1-core">ContainerState [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>containerID</CODE><BR /><I>string</I></TD><TD>Container&#39;s ID in the format &#39;docker://&lt;container_id&gt;&#39;</TD></TR>
<TR><TD><CODE>exitCode</CODE><BR /><I>integer</I></TD><TD>Exit status from the last termination of the container</TD></TR>
<TR><TD><CODE>finishedAt</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time at which the container last terminated</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message regarding the last termination of the container</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>(brief) reason from the last termination of the container</TD></TR>
<TR><TD><CODE>signal</CODE><BR /><I>integer</I></TD><TD>Signal from the last termination of the container</TD></TR>
<TR><TD><CODE>startedAt</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time at which previous execution of the container started</TD></TR>
</TBODY>
</TABLE>
<H2 id="containerstatewaiting-v1-core">ContainerStateWaiting v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ContainerStateWaiting</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ContainerStateWaiting is a waiting state of a container.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#containerstate-v1-core">ContainerState [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Message regarding why the container is not yet running.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>(brief) reason the container is not yet running.</TD></TR>
</TBODY>
</TABLE>
<H2 id="crossversionobjectreference-v1-autoscaling">CrossVersionObjectReference v1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>CrossVersionObjectReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CrossVersionObjectReference contains enough information to let you identify the referred resource.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#crossversionobjectreference-v2beta1-autoscaling">v2beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscalerspec-v1-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds&#34;</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
</TBODY>
</TABLE>
<H2 id="customresourcecolumndefinition-v1beta1-apiextensions-k8s-io">CustomResourceColumnDefinition v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CustomResourceColumnDefinition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CustomResourceColumnDefinition specifies a column for server side printing.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionspec-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>JSONPath</CODE><BR /><I>string</I></TD><TD>JSONPath is a simple JSON path, i.e. with array notation.</TD></TR>
<TR><TD><CODE>description</CODE><BR /><I>string</I></TD><TD>description is a human readable description of this column.</TD></TR>
<TR><TD><CODE>format</CODE><BR /><I>string</I></TD><TD>format is an optional OpenAPI type definition for this column. The &#39;name&#39; format is applied to the primary identifier column to assist in clients identifying column is the resource name. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for more.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is a human readable name for the column.</TD></TR>
<TR><TD><CODE>priority</CODE><BR /><I>integer</I></TD><TD>priority is an integer defining the relative importance of this column compared to others. Lower numbers are considered higher priority. Columns that may be omitted in limited space scenarios should be given a higher priority.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is an OpenAPI type definition for this column. See https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types for more.</TD></TR>
</TBODY>
</TABLE>
<H2 id="customresourcedefinitioncondition-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionCondition v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CustomResourceDefinitionCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CustomResourceDefinitionCondition contains details for the current condition of this pod.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionstatus-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionStatus [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human-readable message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status is the status of the condition. Can be True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is the type of the condition.</TD></TR>
</TBODY>
</TABLE>
<H2 id="customresourcedefinitionnames-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionNames v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CustomResourceDefinitionNames</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CustomResourceDefinitionNames indicates the names to serve this CustomResourceDefinition</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionspec-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1beta1]</a></LI>
<LI><a href="#customresourcedefinitionstatus-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionStatus [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>categories</CODE><BR /><I>string array</I></TD><TD>Categories is a list of grouped resources custom resources belong to (e.g. &#39;all&#39;)</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the serialized kind of the resource. It is normally CamelCase and singular.</TD></TR>
<TR><TD><CODE>listKind</CODE><BR /><I>string</I></TD><TD>ListKind is the serialized kind of the list for this resource. Defaults to &lt;kind&gt;List.</TD></TR>
<TR><TD><CODE>plural</CODE><BR /><I>string</I></TD><TD>Plural is the plural name of the resource to serve. It must match the name of the CustomResourceDefinition-registration too: plural.group and it must be all lowercase.</TD></TR>
<TR><TD><CODE>shortNames</CODE><BR /><I>string array</I></TD><TD>ShortNames are short names for the resource. It must be all lowercase.</TD></TR>
<TR><TD><CODE>singular</CODE><BR /><I>string</I></TD><TD>Singular is the singular name of the resource. It must be all lowercase Defaults to lowercased &lt;kind&gt;</TD></TR>
</TBODY>
</TABLE>
<H2 id="customresourcedefinitionversion-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionVersion v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CustomResourceDefinitionVersion</CODE></TD></TR>
</TBODY>
</TABLE>
<P></P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionspec-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the version name, e.g. “v1”, “v2beta1”, etc.</TD></TR>
<TR><TD><CODE>served</CODE><BR /><I>boolean</I></TD><TD>Served is a flag enabling/disabling this version from being served via REST APIs</TD></TR>
<TR><TD><CODE>storage</CODE><BR /><I>boolean</I></TD><TD>Storage flags the version as storage version. There must be exactly one flagged as storage version.</TD></TR>
</TBODY>
</TABLE>
<H2 id="customresourcesubresourcescale-v1beta1-apiextensions-k8s-io">CustomResourceSubresourceScale v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CustomResourceSubresourceScale</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CustomResourceSubresourceScale defines how to serve the scale subresource for CustomResources.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcesubresources-v1beta1-apiextensions-k8s-io">CustomResourceSubresources [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>labelSelectorPath</CODE><BR /><I>string</I></TD><TD>LabelSelectorPath defines the JSON path inside of a CustomResource that corresponds to Scale.Status.Selector. Only JSON paths without the array notation are allowed. Must be a JSON Path under .status. Must be set to work with HPA. If there is no value under the given path in the CustomResource, the status label selector value in the /scale subresource will default to the empty string.</TD></TR>
<TR><TD><CODE>specReplicasPath</CODE><BR /><I>string</I></TD><TD>SpecReplicasPath defines the JSON path inside of a CustomResource that corresponds to Scale.Spec.Replicas. Only JSON paths without the array notation are allowed. Must be a JSON Path under .spec. If there is no value under the given path in the CustomResource, the /scale subresource will return an error on GET.</TD></TR>
<TR><TD><CODE>statusReplicasPath</CODE><BR /><I>string</I></TD><TD>StatusReplicasPath defines the JSON path inside of a CustomResource that corresponds to Scale.Status.Replicas. Only JSON paths without the array notation are allowed. Must be a JSON Path under .status. If there is no value under the given path in the CustomResource, the status replica value in the /scale subresource will default to 0.</TD></TR>
</TBODY>
</TABLE>
<H2 id="customresourcesubresourcestatus-v1beta1-apiextensions-k8s-io">CustomResourceSubresourceStatus v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CustomResourceSubresourceStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CustomResourceSubresourceStatus defines how to serve the status subresource for CustomResources. Status is represented by the `.status` JSON path inside of a CustomResource. When set, * exposes a /status subresource for the custom resource * PUT requests to the /status subresource take a custom resource object, and ignore changes to anything except the status stanza * PUT/POST/PATCH requests to the custom resource ignore changes to the status stanza</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcesubresources-v1beta1-apiextensions-k8s-io">CustomResourceSubresources [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
<H2 id="customresourcesubresources-v1beta1-apiextensions-k8s-io">CustomResourceSubresources v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CustomResourceSubresources</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CustomResourceSubresources defines the status and scale subresources for CustomResources.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionspec-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>scale</CODE><BR /><I><a href="#customresourcesubresourcescale-v1beta1-apiextensions-k8s-io">CustomResourceSubresourceScale</a></I></TD><TD>Scale denotes the scale subresource for CustomResources</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#customresourcesubresourcestatus-v1beta1-apiextensions-k8s-io">CustomResourceSubresourceStatus</a></I></TD><TD>Status denotes the status subresource for CustomResources</TD></TR>
</TBODY>
</TABLE>
<H2 id="customresourcevalidation-v1beta1-apiextensions-k8s-io">CustomResourceValidation v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>CustomResourceValidation</CODE></TD></TR>
</TBODY>
</TABLE>
<P>CustomResourceValidation is a list of validation methods for CustomResources.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcedefinitionspec-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionSpec [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>openAPIV3Schema</CODE><BR /><I><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps</a></I></TD><TD>OpenAPIV3Schema is the OpenAPI v3 schema to be validated against.</TD></TR>
</TBODY>
</TABLE>
<H2 id="daemonendpoint-v1-core">DaemonEndpoint v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DaemonEndpoint</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DaemonEndpoint contains information about a single Daemon endpoint.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodedaemonendpoints-v1-core">NodeDaemonEndpoints [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>Port</CODE><BR /><I>integer</I></TD><TD>Port number of the given endpoint.</TD></TR>
</TBODY>
</TABLE>
<H2 id="daemonsetcondition-v1-apps">DaemonSetCondition v1 apps</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DaemonSetCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DaemonSetCondition describes the state of a DaemonSet at a certain point.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#daemonsetcondition-v1beta2-apps">v1beta2</a>
<a href="#daemonsetcondition-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetstatus-v1-apps">DaemonSetStatus [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of DaemonSet condition.</TD></TR>
</TBODY>
</TABLE>
<H2 id="daemonsetupdatestrategy-v1-apps">DaemonSetUpdateStrategy v1 apps</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DaemonSetUpdateStrategy</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DaemonSetUpdateStrategy is a struct used to control the update strategy for a DaemonSet.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#daemonsetupdatestrategy-v1beta2-apps">v1beta2</a>
<a href="#daemonsetupdatestrategy-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetspec-v1-apps">DaemonSetSpec [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatedaemonset-v1-apps">RollingUpdateDaemonSet</a></I></TD><TD>Rolling update config params. Present only if type = &#34;RollingUpdate&#34;.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of daemon set update. Can be &#34;RollingUpdate&#34; or &#34;OnDelete&#34;. Default is RollingUpdate.</TD></TR>
</TBODY>
</TABLE>
<H2 id="deleteoptions-v1-meta">DeleteOptions v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DeleteOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeleteOptions may be provided when deleting an API object.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#eviction-v1beta1-policy">Eviction [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE><BR /><I>integer</I></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>orphanDependents</CODE><BR /><I>boolean</I></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the &#34;orphan&#34; finalizer will be added to/removed from the object&#39;s finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>preconditions</CODE><BR /><I><a href="#preconditions-v1-meta">Preconditions</a></I></TD><TD>Must be fulfilled before a deletion is carried out. If not possible, a 409 Conflict status will be returned.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE><BR /><I>string</I></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: &#39;Orphan&#39; - orphan the dependents; &#39;Background&#39; - allow the garbage collector to delete the dependents in the background; &#39;Foreground&#39; - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H2 id="deploymentcondition-v1-apps">DeploymentCondition v1 apps</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DeploymentCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DeploymentCondition describes the state of a deployment at a certain point.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#deploymentcondition-v1beta2-apps">v1beta2</a>
<a href="#deploymentcondition-v1beta1-apps">v1beta1</a>
<a href="#deploymentcondition-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentstatus-v1-apps">DeploymentStatus [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>lastUpdateTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time this condition was updated.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment condition.</TD></TR>
</TBODY>
</TABLE>
<H2 id="downwardapiprojection-v1-core">DownwardAPIProjection v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DownwardAPIProjection</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents downward API info for projecting into a projected volume. Note that this is identical to a downwardAPI volume source without the default mode.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeprojection-v1-core">VolumeProjection [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>items</CODE><BR /><I><a href="#downwardapivolumefile-v1-core">DownwardAPIVolumeFile</a> array</I></TD><TD>Items is a list of DownwardAPIVolume file</TD></TR>
</TBODY>
</TABLE>
<H2 id="downwardapivolumefile-v1-core">DownwardAPIVolumeFile v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DownwardAPIVolumeFile</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DownwardAPIVolumeFile represents information to create the file containing the pod field</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#downwardapiprojection-v1-core">DownwardAPIProjection [core/v1]</a></LI>
<LI><a href="#downwardapivolumesource-v1-core">DownwardAPIVolumeSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fieldRef</CODE><BR /><I><a href="#objectfieldselector-v1-core">ObjectFieldSelector</a></I></TD><TD>Required: Selects a field of the pod: only annotations, labels, name and namespace are supported.</TD></TR>
<TR><TD><CODE>mode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Required: Path is the relative path name of the file to be created. Must not be absolute or contain the &#39;..&#39; path. Must be utf-8 encoded. The first item of the relative path must not start with &#39;..&#39;</TD></TR>
<TR><TD><CODE>resourceFieldRef</CODE><BR /><I><a href="#resourcefieldselector-v1-core">ResourceFieldSelector</a></I></TD><TD>Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, requests.cpu and requests.memory) are currently supported.</TD></TR>
</TBODY>
</TABLE>
<H2 id="downwardapivolumesource-v1-core">DownwardAPIVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>DownwardAPIVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DownwardAPIVolumeSource represents a volume containing downward API info. Downward API volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>defaultMode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#downwardapivolumefile-v1-core">DownwardAPIVolumeFile</a> array</I></TD><TD>Items is a list of downward API volume file</TD></TR>
</TBODY>
</TABLE>
<H2 id="emptydirvolumesource-v1-core">EmptyDirVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EmptyDirVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents an empty directory for a pod. Empty directory volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>medium</CODE><BR /><I>string</I></TD><TD>What type of storage medium should back this directory. The default is &#34;&#34; which means to use the node&#39;s default medium. Must be an empty string (default) or Memory. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir</TD></TR>
<TR><TD><CODE>sizeLimit</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>Total amount of local storage required for this EmptyDir volume. The size limit is also applicable for memory medium. The maximum usage on memory medium EmptyDir would be the minimum value between the SizeLimit specified here and the sum of memory limits of all containers in a pod. The default is nil which means that the limit is undefined. More info: http://kubernetes.io/docs/user-guide/volumes#emptydir</TD></TR>
</TBODY>
</TABLE>
<H2 id="endpointaddress-v1-core">EndpointAddress v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointAddress</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EndpointAddress is a tuple that describes single IP address.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#endpointsubset-v1-core">EndpointSubset [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>hostname</CODE><BR /><I>string</I></TD><TD>The Hostname of this endpoint</TD></TR>
<TR><TD><CODE>ip</CODE><BR /><I>string</I></TD><TD>The IP of this endpoint. May not be loopback (127.0.0.0/8), link-local (169.254.0.0/16), or link-local multicast ((224.0.0.0/24). IPv6 is also accepted but not fully supported on all platforms. Also, certain kubernetes components, like kube-proxy, are not IPv6 ready.</TD></TR>
<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>Optional: Node hosting this endpoint. This can be used to determine endpoints local to a node.</TD></TR>
<TR><TD><CODE>targetRef</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>Reference to object providing the endpoint.</TD></TR>
</TBODY>
</TABLE>
<H2 id="endpointport-v1-core">EndpointPort v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointPort</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EndpointPort is a tuple that describes a single port.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#endpointsubset-v1-core">EndpointSubset [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of this port (corresponds to ServicePort.Name). Must be a DNS_LABEL. Optional only if one port is defined.</TD></TR>
<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>The port number of the endpoint.</TD></TR>
<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>The IP protocol for this port. Must be UDP or TCP. Default is TCP.</TD></TR>
</TBODY>
</TABLE>
<H2 id="endpointsubset-v1-core">EndpointSubset v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EndpointSubset</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EndpointSubset is a group of addresses with a common set of ports. The expanded set of endpoints is the Cartesian product of Addresses x Ports. For example, given:
{
Addresses: [{&#34;ip&#34;: &#34;10.10.1.1&#34;}, {&#34;ip&#34;: &#34;10.10.2.2&#34;}],
Ports: [{&#34;name&#34;: &#34;a&#34;, &#34;port&#34;: 8675}, {&#34;name&#34;: &#34;b&#34;, &#34;port&#34;: 309}]
}
The resulting set of endpoints can be viewed as:
a: [ 10.10.1.1:8675, 10.10.2.2:8675 ],
b: [ 10.10.1.1:309, 10.10.2.2:309 ]</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#endpoints-v1-core">Endpoints [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>addresses</CODE><BR /><I><a href="#endpointaddress-v1-core">EndpointAddress</a> array</I></TD><TD>IP addresses which offer the related ports that are marked as ready. These endpoints should be considered safe for load balancers and clients to utilize.</TD></TR>
<TR><TD><CODE>notReadyAddresses</CODE><BR /><I><a href="#endpointaddress-v1-core">EndpointAddress</a> array</I></TD><TD>IP addresses which offer the related ports but are not currently marked as ready because they have not yet finished starting, have recently failed a readiness check, or have recently failed a liveness check.</TD></TR>
<TR><TD><CODE>ports</CODE><BR /><I><a href="#endpointport-v1-core">EndpointPort</a> array</I></TD><TD>Port numbers available on the related IP addresses.</TD></TR>
</TBODY>
</TABLE>
<H2 id="envfromsource-v1-core">EnvFromSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EnvFromSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EnvFromSource represents the source of a set of ConfigMaps</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#container-v1-core">Container [core/v1]</a></LI>
<LI><a href="#podpresetspec-v1alpha1-settings-k8s-io">PodPresetSpec [settings/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>configMapRef</CODE><BR /><I><a href="#configmapenvsource-v1-core">ConfigMapEnvSource</a></I></TD><TD>The ConfigMap to select from</TD></TR>
<TR><TD><CODE>prefix</CODE><BR /><I>string</I></TD><TD>An optional identifier to prepend to each key in the ConfigMap. Must be a C_IDENTIFIER.</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretenvsource-v1-core">SecretEnvSource</a></I></TD><TD>The Secret to select from</TD></TR>
</TBODY>
</TABLE>
<H2 id="envvar-v1-core">EnvVar v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EnvVar</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EnvVar represents an environment variable present in a Container.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#container-v1-core">Container [core/v1]</a></LI>
<LI><a href="#podpresetspec-v1alpha1-settings-k8s-io">PodPresetSpec [settings/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the environment variable. Must be a C_IDENTIFIER.</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>Variable references $(VAR_NAME) are expanded using the previous defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. The $(VAR_NAME) syntax can be escaped with a double $$, ie: $$(VAR_NAME). Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to &#34;&#34;.</TD></TR>
<TR><TD><CODE>valueFrom</CODE><BR /><I><a href="#envvarsource-v1-core">EnvVarSource</a></I></TD><TD>Source for the environment variable&#39;s value. Cannot be used if value is not empty.</TD></TR>
</TBODY>
</TABLE>
<H2 id="envvarsource-v1-core">EnvVarSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EnvVarSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EnvVarSource represents a source for the value of an EnvVar.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#envvar-v1-core">EnvVar [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>configMapKeyRef</CODE><BR /><I><a href="#configmapkeyselector-v1-core">ConfigMapKeySelector</a></I></TD><TD>Selects a key of a ConfigMap.</TD></TR>
<TR><TD><CODE>fieldRef</CODE><BR /><I><a href="#objectfieldselector-v1-core">ObjectFieldSelector</a></I></TD><TD>Selects a field of the pod: supports metadata.name, metadata.namespace, metadata.labels, metadata.annotations, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP.</TD></TR>
<TR><TD><CODE>resourceFieldRef</CODE><BR /><I><a href="#resourcefieldselector-v1-core">ResourceFieldSelector</a></I></TD><TD>Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.</TD></TR>
<TR><TD><CODE>secretKeyRef</CODE><BR /><I><a href="#secretkeyselector-v1-core">SecretKeySelector</a></I></TD><TD>Selects a key of a secret in the pod&#39;s namespace</TD></TR>
</TBODY>
</TABLE>
<H2 id="eventseries-v1-core">EventSeries v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EventSeries</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EventSeries contain information on series of events, i.e. thing that was/is happening continuously for some time.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#eventseries-v1beta1-events-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#event-v1-core">Event [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>Number of occurrences in this series up to the last heartbeat time</TD></TR>
<TR><TD><CODE>lastObservedTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>Time of the last occurrence observed</TD></TR>
<TR><TD><CODE>state</CODE><BR /><I>string</I></TD><TD>State of this Series: Ongoing or Finished</TD></TR>
</TBODY>
</TABLE>
<H2 id="eventsource-v1-core">EventSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>EventSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>EventSource contains information for an event.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#event-v1-core">Event [core/v1]</a></LI>
<LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>component</CODE><BR /><I>string</I></TD><TD>Component from which the event is generated.</TD></TR>
<TR><TD><CODE>host</CODE><BR /><I>string</I></TD><TD>Node name on which the event is generated.</TD></TR>
</TBODY>
</TABLE>
<H2 id="eviction-v1beta1-policy">Eviction v1beta1 policy</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Eviction</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Eviction evicts a pod from its node subject to certain policies and safety constraints. This is a subresource of Pod. A request to cause such an eviction is created by POSTing to .../pods/&lt;pod name&gt;/evictions.</P>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>deleteOptions</CODE><BR /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD>DeleteOptions may be provided</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>ObjectMeta describes the pod that is being evicted.</TD></TR>
</TBODY>
</TABLE>
<H2 id="execaction-v1-core">ExecAction v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ExecAction</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ExecAction describes a &#34;run in container&#34; action.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#handler-v1-core">Handler [core/v1]</a></LI>
<LI><a href="#probe-v1-core">Probe [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>command</CODE><BR /><I>string array</I></TD><TD>Command is the command line to execute inside the container, the working directory for the command is root (&#39;/&#39;) in the container&#39;s filesystem. The command is simply exec&#39;d, it is not run inside a shell, so traditional shell instructions (&#39;|&#39;, etc) won&#39;t work. To use a shell, you need to explicitly call out to that shell. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.</TD></TR>
</TBODY>
</TABLE>
<H2 id="externaldocumentation-v1beta1-apiextensions-k8s-io">ExternalDocumentation v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ExternalDocumentation</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ExternalDocumentation allows referencing an external resource for extended documentation.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>description</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>url</CODE><BR /><I>string</I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="externalmetricsource-v2beta1-autoscaling">ExternalMetricSource v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ExternalMetricSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ExternalMetricSource indicates how to scale on a metric not associated with any Kubernetes object (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster). Exactly one &#34;target&#34; type should be set.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#metricspec-v2beta1-autoscaling">MetricSpec [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question.</TD></TR>
<TR><TD><CODE>metricSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>metricSelector is used to identify a specific time series within a given metric.</TD></TR>
<TR><TD><CODE>targetAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetAverageValue is the target per-pod value of global metric (as a quantity). Mutually exclusive with TargetValue.</TD></TR>
<TR><TD><CODE>targetValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetValue is the target value of the metric (as a quantity). Mutually exclusive with TargetAverageValue.</TD></TR>
</TBODY>
</TABLE>
<H2 id="externalmetricstatus-v2beta1-autoscaling">ExternalMetricStatus v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ExternalMetricStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ExternalMetricStatus indicates the current value of a global metric not associated with any Kubernetes object.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#metricstatus-v2beta1-autoscaling">MetricStatus [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>currentAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentAverageValue is the current value of metric averaged over autoscaled pods.</TD></TR>
<TR><TD><CODE>currentValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentValue is the current value of the metric (as a quantity)</TD></TR>
<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of a metric used for autoscaling in metric system.</TD></TR>
<TR><TD><CODE>metricSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>metricSelector is used to identify a specific time series within a given metric.</TD></TR>
</TBODY>
</TABLE>
<H2 id="fcvolumesource-v1-core">FCVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FCVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Fibre Channel volume. Fibre Channel volumes can only be mounted as read/write once. Fibre Channel volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>lun</CODE><BR /><I>integer</I></TD><TD>Optional: FC target lun number</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>targetWWNs</CODE><BR /><I>string array</I></TD><TD>Optional: FC target worldwide names (WWNs)</TD></TR>
<TR><TD><CODE>wwids</CODE><BR /><I>string array</I></TD><TD>Optional: FC volume world wide identifiers (wwids) Either wwids or combination of targetWWNs and lun must be set, but not both simultaneously.</TD></TR>
</TBODY>
</TABLE>
<H2 id="fsgroupstrategyoptions-v1beta1-extensions">FSGroupStrategyOptions v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>FSGroupStrategyOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>FSGroupStrategyOptions defines the strategy type and options used to create the strategy. Deprecated: use FSGroupStrategyOptions from policy API Group instead.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-extensions">PodSecurityPolicySpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-extensions">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of fs groups. If you would like to force a single fs group then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate what FSGroup is used in the SecurityContext.</TD></TR>
</TBODY>
</TABLE>
<H2 id="flexpersistentvolumesource-v1-core">FlexPersistentVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FlexPersistentVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>FlexPersistentVolumeSource represents a generic persistent volume resource that is provisioned/attached using an exec based plugin.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver is the name of the driver to use for this volume.</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. The default filesystem depends on FlexVolume script.</TD></TR>
<TR><TD><CODE>options</CODE><BR /><I>object</I></TD><TD>Optional: Extra command options if any.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.</TD></TR>
</TBODY>
</TABLE>
<H2 id="flexvolumesource-v1-core">FlexVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FlexVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>Driver is the name of the driver to use for this volume.</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. The default filesystem depends on FlexVolume script.</TD></TR>
<TR><TD><CODE>options</CODE><BR /><I>object</I></TD><TD>Optional: Extra command options if any.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>Optional: SecretRef is reference to the secret object containing sensitive information to pass to the plugin scripts. This may be empty if no secret object is specified. If the secret object contains more than one secret, all secrets are passed to the plugin scripts.</TD></TR>
</TBODY>
</TABLE>
<H2 id="flockervolumesource-v1-core">FlockerVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>FlockerVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Flocker volume mounted by the Flocker agent. One and only one of datasetName and datasetUUID should be set. Flocker volumes do not support ownership management or SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>datasetName</CODE><BR /><I>string</I></TD><TD>Name of the dataset stored as metadata -&gt; name on the dataset for Flocker should be considered as deprecated</TD></TR>
<TR><TD><CODE>datasetUUID</CODE><BR /><I>string</I></TD><TD>UUID of the dataset. This is unique identifier of a Flocker dataset</TD></TR>
</TBODY>
</TABLE>
<H2 id="gcepersistentdiskvolumesource-v1-core">GCEPersistentDiskVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GCEPersistentDiskVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Persistent Disk resource in Google Compute Engine.
A GCE PD must exist before mounting to a container. The disk must also be in the same GCE project and zone as the kubelet. A GCE PD can only be mounted as read/write once or read-only many times. GCE PDs support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>The partition in the volume that you want to mount. If omitted, the default is to mount by volume name. Examples: For volume /dev/sda1, you specify the partition as &#34;1&#34;. Similarly, the volume partition for /dev/sda is &#34;0&#34; (or you can leave the property empty). More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
<TR><TD><CODE>pdName</CODE><BR /><I>string</I></TD><TD>Unique name of the PD resource in GCE. Used to identify the disk in GCE. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#gcepersistentdisk</TD></TR>
</TBODY>
</TABLE>
<H2 id="gitrepovolumesource-v1-core">GitRepoVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GitRepoVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a volume that is populated with the contents of a git repository. Git repo volumes do not support ownership management. Git repo volumes support SELinux relabeling.
DEPRECATED: GitRepo is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod&#39;s container.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>directory</CODE><BR /><I>string</I></TD><TD>Target directory name. Must not contain or start with &#39;..&#39;. If &#39;.&#39; is supplied, the volume directory will be the git repository. Otherwise, if specified, the volume will contain the git repository in the subdirectory with the given name.</TD></TR>
<TR><TD><CODE>repository</CODE><BR /><I>string</I></TD><TD>Repository URL</TD></TR>
<TR><TD><CODE>revision</CODE><BR /><I>string</I></TD><TD>Commit hash for the specified revision.</TD></TR>
</TBODY>
</TABLE>
<H2 id="glusterfsvolumesource-v1-core">GlusterfsVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GlusterfsVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Glusterfs mount that lasts the lifetime of a pod. Glusterfs volumes do not support ownership management or SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>endpoints</CODE><BR /><I>string</I></TD><TD>EndpointsName is the endpoint name that details Glusterfs topology. More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md#create-a-pod</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is the Glusterfs volume path. More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md#create-a-pod</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the Glusterfs volume to be mounted with read-only permissions. Defaults to false. More info: https://releases.k8s.io/HEAD/examples/volumes/glusterfs/README.md#create-a-pod</TD></TR>
</TBODY>
</TABLE>
<H2 id="groupversionfordiscovery-v1-meta">GroupVersionForDiscovery v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>GroupVersionForDiscovery</CODE></TD></TR>
</TBODY>
</TABLE>
<P>GroupVersion contains the &#34;group/version&#34; and &#34;version&#34; string of a version. It is made a struct to keep extensibility.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apigroup-v1-meta">APIGroup [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>groupVersion</CODE><BR /><I>string</I></TD><TD>groupVersion specifies the API group and version in the form &#34;group/version&#34;</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>version specifies the version in the form of &#34;version&#34;. This is to save the clients the trouble of splitting the GroupVersion.</TD></TR>
</TBODY>
</TABLE>
<H2 id="httpgetaction-v1-core">HTTPGetAction v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HTTPGetAction</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HTTPGetAction describes an action based on HTTP Get requests.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#handler-v1-core">Handler [core/v1]</a></LI>
<LI><a href="#probe-v1-core">Probe [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>host</CODE><BR /><I>string</I></TD><TD>Host name to connect to, defaults to the pod IP. You probably want to set &#34;Host&#34; in httpHeaders instead.</TD></TR>
<TR><TD><CODE>httpHeaders</CODE><BR /><I><a href="#httpheader-v1-core">HTTPHeader</a> array</I></TD><TD>Custom headers to set in the request. HTTP allows repeated headers.</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path to access on the HTTP server.</TD></TR>
<TR><TD><CODE>port</CODE></TD><TD>Name or number of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.</TD></TR>
<TR><TD><CODE>scheme</CODE><BR /><I>string</I></TD><TD>Scheme to use for connecting to the host. Defaults to HTTP.</TD></TR>
</TBODY>
</TABLE>
<H2 id="httpheader-v1-core">HTTPHeader v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HTTPHeader</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HTTPHeader describes a custom header to be used in HTTP probes</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#httpgetaction-v1-core">HTTPGetAction [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The header field name</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>The header field value</TD></TR>
</TBODY>
</TABLE>
<H2 id="httpingresspath-v1beta1-extensions">HTTPIngressPath v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>HTTPIngressPath</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HTTPIngressPath associates a path regex with a backend. Incoming urls matching the path are forwarded to the backend.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#httpingressrulevalue-v1beta1-extensions">HTTPIngressRuleValue [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>backend</CODE><BR /><I><a href="#ingressbackend-v1beta1-extensions">IngressBackend</a></I></TD><TD>Backend defines the referenced service endpoint to which the traffic will be forwarded to.</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is an extended POSIX regex as defined by IEEE Std 1003.1, (i.e this follows the egrep/unix syntax, not the perl syntax) matched against the path of an incoming request. Currently it can contain characters disallowed from the conventional &#34;path&#34; part of a URL as defined by RFC 3986. Paths must begin with a &#39;/&#39;. If unspecified, the path defaults to a catch all sending traffic to the backend.</TD></TR>
</TBODY>
</TABLE>
<H2 id="httpingressrulevalue-v1beta1-extensions">HTTPIngressRuleValue v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>HTTPIngressRuleValue</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HTTPIngressRuleValue is a list of http selectors pointing to backends. In the example: http://&lt;host&gt;/&lt;path&gt;?&lt;searchpart&gt; -&gt; backend where where parts of the url correspond to RFC 3986, this resource will be used to match against everything after the last &#39;/&#39; and before the first &#39;?&#39; or &#39;#&#39;.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressrule-v1beta1-extensions">IngressRule [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>paths</CODE><BR /><I><a href="#httpingresspath-v1beta1-extensions">HTTPIngressPath</a> array</I></TD><TD>A collection of paths that map requests to backends.</TD></TR>
</TBODY>
</TABLE>
<H2 id="handler-v1-core">Handler v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Handler</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Handler defines a specific action that should be taken</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#lifecycle-v1-core">Lifecycle [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>exec</CODE><BR /><I><a href="#execaction-v1-core">ExecAction</a></I></TD><TD>One and only one of the following should be specified. Exec specifies the action to take.</TD></TR>
<TR><TD><CODE>httpGet</CODE><BR /><I><a href="#httpgetaction-v1-core">HTTPGetAction</a></I></TD><TD>HTTPGet specifies the http request to perform.</TD></TR>
<TR><TD><CODE>tcpSocket</CODE><BR /><I><a href="#tcpsocketaction-v1-core">TCPSocketAction</a></I></TD><TD>TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported</TD></TR>
</TBODY>
</TABLE>
<H2 id="horizontalpodautoscalercondition-v2beta1-autoscaling">HorizontalPodAutoscalerCondition v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>HorizontalPodAutoscalerCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HorizontalPodAutoscalerCondition describes the state of a HorizontalPodAutoscaler at a certain point.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastTransitionTime is the last time the condition transitioned from one status to another</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>message is a human-readable explanation containing details about the transition</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>reason is the reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>status is the status of the condition (True, False, Unknown)</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type describes the current condition</TD></TR>
</TBODY>
</TABLE>
<H2 id="hostalias-v1-core">HostAlias v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HostAlias</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HostAlias holds the mapping between IP and hostnames that will be injected as an entry in the pod&#39;s hosts file.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>hostnames</CODE><BR /><I>string array</I></TD><TD>Hostnames for the above IP address.</TD></TR>
<TR><TD><CODE>ip</CODE><BR /><I>string</I></TD><TD>IP address of the host file entry.</TD></TR>
</TBODY>
</TABLE>
<H2 id="hostpathvolumesource-v1-core">HostPathVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>HostPathVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a host path mapped into a pod. Host path volumes do not support ownership management or SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path of the directory on the host. If the path is a symlink, it will follow the link to the real path. More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type for HostPath Volume Defaults to &#34;&#34; More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath</TD></TR>
</TBODY>
</TABLE>
<H2 id="hostportrange-v1beta1-extensions">HostPortRange v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>HostPortRange</CODE></TD></TR>
</TBODY>
</TABLE>
<P>HostPortRange defines a range of host ports that will be enabled by a policy for pods to use. It requires both the start and end to be defined. Deprecated: use HostPortRange from policy API Group instead.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-extensions">PodSecurityPolicySpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>max</CODE><BR /><I>integer</I></TD><TD>max is the end of the range, inclusive.</TD></TR>
<TR><TD><CODE>min</CODE><BR /><I>integer</I></TD><TD>min is the start of the range, inclusive.</TD></TR>
</TBODY>
</TABLE>
<H2 id="idrange-v1beta1-extensions">IDRange v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>IDRange</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IDRange provides a min/max of an allowed range of IDs. Deprecated: use IDRange from policy API Group instead.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#fsgroupstrategyoptions-v1beta1-extensions">FSGroupStrategyOptions [extensions/v1beta1]</a></LI>
<LI><a href="#runasuserstrategyoptions-v1beta1-extensions">RunAsUserStrategyOptions [extensions/v1beta1]</a></LI>
<LI><a href="#supplementalgroupsstrategyoptions-v1beta1-extensions">SupplementalGroupsStrategyOptions [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>max</CODE><BR /><I>integer</I></TD><TD>max is the end of the range, inclusive.</TD></TR>
<TR><TD><CODE>min</CODE><BR /><I>integer</I></TD><TD>min is the start of the range, inclusive.</TD></TR>
</TBODY>
</TABLE>
<H2 id="ipblock-v1-networking-k8s-io">IPBlock v1 networking.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>IPBlock</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IPBlock describes a particular CIDR (Ex. &#34;192.168.1.1/24&#34;) that is allowed to the pods matched by a NetworkPolicySpec&#39;s podSelector. The except entry describes CIDRs that should not be included within this rule.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#ipblock-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>cidr</CODE><BR /><I>string</I></TD><TD>CIDR is a string representing the IP Block Valid examples are &#34;192.168.1.1/24&#34;</TD></TR>
<TR><TD><CODE>except</CODE><BR /><I>string array</I></TD><TD>Except is a slice of CIDRs that should not be included within an IP Block Valid examples are &#34;192.168.1.1/24&#34; Except values will be rejected if they are outside the CIDR range</TD></TR>
</TBODY>
</TABLE>
<H2 id="iscsipersistentvolumesource-v1-core">ISCSIPersistentVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ISCSIPersistentVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ISCSIPersistentVolumeSource represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>chapAuthDiscovery</CODE><BR /><I>boolean</I></TD><TD>whether support iSCSI Discovery CHAP authentication</TD></TR>
<TR><TD><CODE>chapAuthSession</CODE><BR /><I>boolean</I></TD><TD>whether support iSCSI Session CHAP authentication</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi</TD></TR>
<TR><TD><CODE>initiatorName</CODE><BR /><I>string</I></TD><TD>Custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface &lt;target portal&gt;:&lt;volume name&gt; will be created for the connection.</TD></TR>
<TR><TD><CODE>iqn</CODE><BR /><I>string</I></TD><TD>Target iSCSI Qualified Name.</TD></TR>
<TR><TD><CODE>iscsiInterface</CODE><BR /><I>string</I></TD><TD>iSCSI Interface Name that uses an iSCSI transport. Defaults to &#39;default&#39; (tcp).</TD></TR>
<TR><TD><CODE>lun</CODE><BR /><I>integer</I></TD><TD>iSCSI Target Lun number.</TD></TR>
<TR><TD><CODE>portals</CODE><BR /><I>string array</I></TD><TD>iSCSI Target Portal List. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false.</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>CHAP Secret for iSCSI target and initiator authentication</TD></TR>
<TR><TD><CODE>targetPortal</CODE><BR /><I>string</I></TD><TD>iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).</TD></TR>
</TBODY>
</TABLE>
<H2 id="iscsivolumesource-v1-core">ISCSIVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ISCSIVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents an ISCSI disk. ISCSI volumes can only be mounted as read/write once. ISCSI volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>chapAuthDiscovery</CODE><BR /><I>boolean</I></TD><TD>whether support iSCSI Discovery CHAP authentication</TD></TR>
<TR><TD><CODE>chapAuthSession</CODE><BR /><I>boolean</I></TD><TD>whether support iSCSI Session CHAP authentication</TD></TR>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#iscsi</TD></TR>
<TR><TD><CODE>initiatorName</CODE><BR /><I>string</I></TD><TD>Custom iSCSI Initiator Name. If initiatorName is specified with iscsiInterface simultaneously, new iSCSI interface &lt;target portal&gt;:&lt;volume name&gt; will be created for the connection.</TD></TR>
<TR><TD><CODE>iqn</CODE><BR /><I>string</I></TD><TD>Target iSCSI Qualified Name.</TD></TR>
<TR><TD><CODE>iscsiInterface</CODE><BR /><I>string</I></TD><TD>iSCSI Interface Name that uses an iSCSI transport. Defaults to &#39;default&#39; (tcp).</TD></TR>
<TR><TD><CODE>lun</CODE><BR /><I>integer</I></TD><TD>iSCSI Target Lun number.</TD></TR>
<TR><TD><CODE>portals</CODE><BR /><I>string array</I></TD><TD>iSCSI Target Portal List. The portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false.</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>CHAP Secret for iSCSI target and initiator authentication</TD></TR>
<TR><TD><CODE>targetPortal</CODE><BR /><I>string</I></TD><TD>iSCSI Target Portal. The Portal is either an IP or ip_addr:port if the port is other than default (typically TCP ports 860 and 3260).</TD></TR>
</TBODY>
</TABLE>
<H2 id="ingressbackend-v1beta1-extensions">IngressBackend v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>IngressBackend</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IngressBackend describes all endpoints for a given service and port.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#httpingresspath-v1beta1-extensions">HTTPIngressPath [extensions/v1beta1]</a></LI>
<LI><a href="#ingressspec-v1beta1-extensions">IngressSpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>serviceName</CODE><BR /><I>string</I></TD><TD>Specifies the name of the referenced service.</TD></TR>
<TR><TD><CODE>servicePort</CODE></TD><TD>Specifies the port of the referenced service.</TD></TR>
</TBODY>
</TABLE>
<H2 id="ingressrule-v1beta1-extensions">IngressRule v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>IngressRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IngressRule represents the rules mapping the paths under a specified host to the related backend services. Incoming requests are first evaluated for a host match, then routed to the backend associated with the matching IngressRuleValue.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressspec-v1beta1-extensions">IngressSpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>host</CODE><BR /><I>string</I></TD><TD>Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the &#34;host&#34; part of the URI as defined in the RFC: 1. IPs are not allowed. Currently an IngressRuleValue can only apply to the IP in the Spec of the parent Ingress. 2. The `:` delimiter is not respected because ports are not allowed. Currently the port of an Ingress is implicitly :80 for http and :443 for https. Both these may change in the future. Incoming requests are matched against the host before the IngressRuleValue. If the host is unspecified, the Ingress routes all traffic based on the specified IngressRuleValue.</TD></TR>
<TR><TD><CODE>http</CODE><BR /><I><a href="#httpingressrulevalue-v1beta1-extensions">HTTPIngressRuleValue</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="ingresstls-v1beta1-extensions">IngressTLS v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>IngressTLS</CODE></TD></TR>
</TBODY>
</TABLE>
<P>IngressTLS describes the transport layer security associated with an Ingress.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressspec-v1beta1-extensions">IngressSpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>hosts</CODE><BR /><I>string array</I></TD><TD>Hosts are a list of hosts included in the TLS certificate. The values in this list must match the name/s used in the tlsSecret. Defaults to the wildcard host setting for the loadbalancer controller fulfilling this Ingress, if left unspecified.</TD></TR>
<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>SecretName is the name of the secret used to terminate SSL traffic on 443. Field is left optional to allow SSL routing based on SNI hostname alone. If the SNI host in a listener conflicts with the &#34;Host&#34; header field used by an IngressRule, the SNI host is used for termination and value of the Host header is used for routing.</TD></TR>
</TBODY>
</TABLE>
<H2 id="initializer-v1-meta">Initializer v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Initializer</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Initializer is information about an initializer that has not yet completed.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#initializer-v1alpha1-admissionregistration-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#initializers-v1-meta">Initializers [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name of the process that is responsible for initializing this object.</TD></TR>
</TBODY>
</TABLE>
<H2 id="initializers-v1-meta">Initializers v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Initializers</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Initializers tracks the progress of initialization.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#objectmeta-v1-meta">ObjectMeta [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pending</CODE><BR /><I><a href="#initializer-v1-meta">Initializer</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>Pending is a list of initializers that must execute in order before this object is visible. When the last pending initializer is removed, and no failing result is set, the initializers struct will be set to nil and the object is considered as initialized and visible to all clients.</TD></TR>
<TR><TD><CODE>result</CODE><BR /><I><a href="#status-v1-meta">Status</a></I></TD><TD>If result is set with the Failure field, the object will be persisted to storage and then deleted, ensuring that other clients can observe the deletion.</TD></TR>
</TBODY>
</TABLE>
<H2 id="json-v1beta1-apiextensions-k8s-io">JSON v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>JSON</CODE></TD></TR>
</TBODY>
</TABLE>
<P>JSON represents any valid JSON value. These types are supported: bool, int64, float64, string, []interface{}, map[string]interface{} and nil.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
<H2 id="jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>JSONSchemaProps</CODE></TD></TR>
</TBODY>
</TABLE>
<P>JSONSchemaProps is a JSON-Schema following Specification Draft 4 (http://json-schema.org/).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#customresourcevalidation-v1beta1-apiextensions-k8s-io">CustomResourceValidation [apiextensions/v1beta1]</a></LI>
<LI><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>$ref</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>$schema</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>additionalItems</CODE><BR /><I><a href="#jsonschemapropsorbool-v1beta1-apiextensions-k8s-io">JSONSchemaPropsOrBool</a></I></TD><TD></TD></TR>
<TR><TD><CODE>additionalProperties</CODE><BR /><I><a href="#jsonschemapropsorbool-v1beta1-apiextensions-k8s-io">JSONSchemaPropsOrBool</a></I></TD><TD></TD></TR>
<TR><TD><CODE>allOf</CODE><BR /><I><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>anyOf</CODE><BR /><I><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>default</CODE><BR /><I><a href="#json-v1beta1-apiextensions-k8s-io">JSON</a></I></TD><TD></TD></TR>
<TR><TD><CODE>definitions</CODE><BR /><I>object</I></TD><TD></TD></TR>
<TR><TD><CODE>dependencies</CODE><BR /><I>object</I></TD><TD></TD></TR>
<TR><TD><CODE>description</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>enum</CODE><BR /><I><a href="#json-v1beta1-apiextensions-k8s-io">JSON</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>example</CODE><BR /><I><a href="#json-v1beta1-apiextensions-k8s-io">JSON</a></I></TD><TD></TD></TR>
<TR><TD><CODE>exclusiveMaximum</CODE><BR /><I>boolean</I></TD><TD></TD></TR>
<TR><TD><CODE>exclusiveMinimum</CODE><BR /><I>boolean</I></TD><TD></TD></TR>
<TR><TD><CODE>externalDocs</CODE><BR /><I><a href="#externaldocumentation-v1beta1-apiextensions-k8s-io">ExternalDocumentation</a></I></TD><TD></TD></TR>
<TR><TD><CODE>format</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>id</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#jsonschemapropsorarray-v1beta1-apiextensions-k8s-io">JSONSchemaPropsOrArray</a></I></TD><TD></TD></TR>
<TR><TD><CODE>maxItems</CODE><BR /><I>integer</I></TD><TD></TD></TR>
<TR><TD><CODE>maxLength</CODE><BR /><I>integer</I></TD><TD></TD></TR>
<TR><TD><CODE>maxProperties</CODE><BR /><I>integer</I></TD><TD></TD></TR>
<TR><TD><CODE>maximum</CODE><BR /><I>number</I></TD><TD></TD></TR>
<TR><TD><CODE>minItems</CODE><BR /><I>integer</I></TD><TD></TD></TR>
<TR><TD><CODE>minLength</CODE><BR /><I>integer</I></TD><TD></TD></TR>
<TR><TD><CODE>minProperties</CODE><BR /><I>integer</I></TD><TD></TD></TR>
<TR><TD><CODE>minimum</CODE><BR /><I>number</I></TD><TD></TD></TR>
<TR><TD><CODE>multipleOf</CODE><BR /><I>number</I></TD><TD></TD></TR>
<TR><TD><CODE>not</CODE><BR /><I><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps</a></I></TD><TD></TD></TR>
<TR><TD><CODE>oneOf</CODE><BR /><I><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>pattern</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>patternProperties</CODE><BR /><I>object</I></TD><TD></TD></TR>
<TR><TD><CODE>properties</CODE><BR /><I>object</I></TD><TD></TD></TR>
<TR><TD><CODE>required</CODE><BR /><I>string array</I></TD><TD></TD></TR>
<TR><TD><CODE>title</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>uniqueItems</CODE><BR /><I>boolean</I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="jsonschemapropsorarray-v1beta1-apiextensions-k8s-io">JSONSchemaPropsOrArray v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>JSONSchemaPropsOrArray</CODE></TD></TR>
</TBODY>
</TABLE>
<P>JSONSchemaPropsOrArray represents a value that can either be a JSONSchemaProps or an array of JSONSchemaProps. Mainly here for serialization purposes.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
<H2 id="jsonschemapropsorbool-v1beta1-apiextensions-k8s-io">JSONSchemaPropsOrBool v1beta1 apiextensions.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiextensions.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>JSONSchemaPropsOrBool</CODE></TD></TR>
</TBODY>
</TABLE>
<P>JSONSchemaPropsOrBool represents JSONSchemaProps or a boolean value. Defaults to true for the boolean property.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#jsonschemaprops-v1beta1-apiextensions-k8s-io">JSONSchemaProps [apiextensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
<H2 id="jobcondition-v1-batch">JobCondition v1 batch</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>JobCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>JobCondition describes current state of a job.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#jobstatus-v1-batch">JobStatus [batch/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastProbeTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition was checked.</TD></TR>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transit from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human readable message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>(brief) reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of job condition, Complete or Failed.</TD></TR>
</TBODY>
</TABLE>
<H2 id="jobtemplatespec-v1beta1-batch">JobTemplateSpec v1beta1 batch</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>batch</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>JobTemplateSpec</CODE></TD></TR>
</TBODY>
</TABLE>
<P>JobTemplateSpec describes the data a Job should have when created from a template</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#jobtemplatespec-v2alpha1-batch">v2alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjobspec-v1beta1-batch">CronJobSpec [batch/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata of the jobs created from this template. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#jobspec-v1-batch">JobSpec</a></I></TD><TD>Specification of the desired behavior of the job. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H2 id="keytopath-v1-core">KeyToPath v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>KeyToPath</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Maps a string key to a path within a volume.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#configmapprojection-v1-core">ConfigMapProjection [core/v1]</a></LI>
<LI><a href="#configmapvolumesource-v1-core">ConfigMapVolumeSource [core/v1]</a></LI>
<LI><a href="#secretprojection-v1-core">SecretProjection [core/v1]</a></LI>
<LI><a href="#secretvolumesource-v1-core">SecretVolumeSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The key to project.</TD></TR>
<TR><TD><CODE>mode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits to use on this file, must be a value between 0 and 0777. If not specified, the volume defaultMode will be used. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>The relative path of the file to map the key to. May not be an absolute path. May not contain the path element &#39;..&#39;. May not start with the string &#39;..&#39;.</TD></TR>
</TBODY>
</TABLE>
<H2 id="labelselector-v1-meta">LabelSelector v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LabelSelector</CODE></TD></TR>
</TBODY>
</TABLE>
<P>A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#aggregationrule-v1-rbac-authorization-k8s-io">AggregationRule [rbac/v1]</a></LI>
<LI><a href="#aggregationrule-v1beta1-rbac-authorization-k8s-io">AggregationRule [rbac/v1beta1]</a></LI>
<LI><a href="#aggregationrule-v1alpha1-rbac-authorization-k8s-io">AggregationRule [rbac/v1alpha1]</a></LI>
<LI><a href="#daemonsetspec-v1-apps">DaemonSetSpec [apps/v1]</a></LI>
<LI><a href="#daemonsetspec-v1beta2-apps">DaemonSetSpec [apps/v1beta2]</a></LI>
<LI><a href="#daemonsetspec-v1beta1-extensions">DaemonSetSpec [extensions/v1beta1]</a></LI>
<LI><a href="#deploymentspec-v1-apps">DeploymentSpec [apps/v1]</a></LI>
<LI><a href="#deploymentspec-v1beta2-apps">DeploymentSpec [apps/v1beta2]</a></LI>
<LI><a href="#deploymentspec-v1beta1-apps">DeploymentSpec [apps/v1beta1]</a></LI>
<LI><a href="#deploymentspec-v1beta1-extensions">DeploymentSpec [extensions/v1beta1]</a></LI>
<LI><a href="#externalmetricsource-v2beta1-autoscaling">ExternalMetricSource [autoscaling/v2beta1]</a></LI>
<LI><a href="#externalmetricstatus-v2beta1-autoscaling">ExternalMetricStatus [autoscaling/v2beta1]</a></LI>
<LI><a href="#jobspec-v1-batch">JobSpec [batch/v1]</a></LI>
<LI><a href="#networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer [networking/v1]</a></LI>
<LI><a href="#networkpolicypeer-v1beta1-extensions">NetworkPolicyPeer [extensions/v1beta1]</a></LI>
<LI><a href="#networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec [networking/v1]</a></LI>
<LI><a href="#networkpolicyspec-v1beta1-extensions">NetworkPolicySpec [extensions/v1beta1]</a></LI>
<LI><a href="#persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec [core/v1]</a></LI>
<LI><a href="#podaffinityterm-v1-core">PodAffinityTerm [core/v1]</a></LI>
<LI><a href="#poddisruptionbudgetspec-v1beta1-policy">PodDisruptionBudgetSpec [policy/v1beta1]</a></LI>
<LI><a href="#podpresetspec-v1alpha1-settings-k8s-io">PodPresetSpec [settings/v1alpha1]</a></LI>
<LI><a href="#replicasetspec-v1-apps">ReplicaSetSpec [apps/v1]</a></LI>
<LI><a href="#replicasetspec-v1beta2-apps">ReplicaSetSpec [apps/v1beta2]</a></LI>
<LI><a href="#replicasetspec-v1beta1-extensions">ReplicaSetSpec [extensions/v1beta1]</a></LI>
<LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
<LI><a href="#statefulsetspec-v1beta2-apps">StatefulSetSpec [apps/v1beta2]</a></LI>
<LI><a href="#statefulsetspec-v1beta1-apps">StatefulSetSpec [apps/v1beta1]</a></LI>
<LI><a href="#webhook-v1beta1-admissionregistration-k8s-io">Webhook [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>matchExpressions</CODE><BR /><I><a href="#labelselectorrequirement-v1-meta">LabelSelectorRequirement</a> array</I></TD><TD>matchExpressions is a list of label selector requirements. The requirements are ANDed.</TD></TR>
<TR><TD><CODE>matchLabels</CODE><BR /><I>object</I></TD><TD>matchLabels is a map of {key,value} pairs. A single {key,value} in the matchLabels map is equivalent to an element of matchExpressions, whose key field is &#34;key&#34;, the operator is &#34;In&#34;, and the values array contains only &#34;value&#34;. The requirements are ANDed.</TD></TR>
</TBODY>
</TABLE>
<H2 id="labelselectorrequirement-v1-meta">LabelSelectorRequirement v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LabelSelectorRequirement</CODE></TD></TR>
</TBODY>
</TABLE>
<P>A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#labelselector-v1-meta">LabelSelector [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>key</CODE><BR /><I>string</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>key</I></TD><TD>key is the label key that the selector applies to.</TD></TR>
<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>operator represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.</TD></TR>
<TR><TD><CODE>values</CODE><BR /><I>string array</I></TD><TD>values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.</TD></TR>
</TBODY>
</TABLE>
<H2 id="lifecycle-v1-core">Lifecycle v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Lifecycle</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Lifecycle describes actions that the management system should take in response to container lifecycle events. For the PostStart and PreStop lifecycle handlers, management of the container blocks until the action is complete, unless the container process fails, in which case the handler is aborted.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#container-v1-core">Container [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>postStart</CODE><BR /><I><a href="#handler-v1-core">Handler</a></I></TD><TD>PostStart is called immediately after a container is created. If the handler fails, the container is terminated and restarted according to its restart policy. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks</TD></TR>
<TR><TD><CODE>preStop</CODE><BR /><I><a href="#handler-v1-core">Handler</a></I></TD><TD>PreStop is called immediately before a container is terminated. The container is terminated after the handler completes. The reason for termination is passed to the handler. Regardless of the outcome of the handler, the container is eventually terminated. Other management of the container blocks until the hook completes. More info: https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#container-hooks</TD></TR>
</TBODY>
</TABLE>
<H2 id="limitrangeitem-v1-core">LimitRangeItem v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LimitRangeItem</CODE></TD></TR>
</TBODY>
</TABLE>
<P>LimitRangeItem defines a min/max usage limit for any resource that matches on kind.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#limitrangespec-v1-core">LimitRangeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>default</CODE><BR /><I>object</I></TD><TD>Default resource requirement limit value by resource name if resource limit is omitted.</TD></TR>
<TR><TD><CODE>defaultRequest</CODE><BR /><I>object</I></TD><TD>DefaultRequest is the default resource requirement request value by resource name if resource request is omitted.</TD></TR>
<TR><TD><CODE>max</CODE><BR /><I>object</I></TD><TD>Max usage constraints on this kind by resource name.</TD></TR>
<TR><TD><CODE>maxLimitRequestRatio</CODE><BR /><I>object</I></TD><TD>MaxLimitRequestRatio if specified, the named resource must have a request and limit that are both non-zero where limit divided by request is less than or equal to the enumerated value; this represents the max burst for the named resource.</TD></TR>
<TR><TD><CODE>min</CODE><BR /><I>object</I></TD><TD>Min usage constraints on this kind by resource name.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of resource that this limit applies to.</TD></TR>
</TBODY>
</TABLE>
<H2 id="listmeta-v1-meta">ListMeta v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ListMeta</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservicelist-v1-apiregistration-k8s-io">APIServiceList [apiregistration/v1]</a></LI>
<LI><a href="#apiservicelist-v1beta1-apiregistration-k8s-io">APIServiceList [apiregistration/v1beta1]</a></LI>
<LI><a href="#certificatesigningrequestlist-v1beta1-certificates-k8s-io">CertificateSigningRequestList [certificates/v1beta1]</a></LI>
<LI><a href="#clusterrolebindinglist-v1-rbac-authorization-k8s-io">ClusterRoleBindingList [rbac/v1]</a></LI>
<LI><a href="#clusterrolebindinglist-v1beta1-rbac-authorization-k8s-io">ClusterRoleBindingList [rbac/v1beta1]</a></LI>
<LI><a href="#clusterrolebindinglist-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBindingList [rbac/v1alpha1]</a></LI>
<LI><a href="#clusterrolelist-v1-rbac-authorization-k8s-io">ClusterRoleList [rbac/v1]</a></LI>
<LI><a href="#clusterrolelist-v1beta1-rbac-authorization-k8s-io">ClusterRoleList [rbac/v1beta1]</a></LI>
<LI><a href="#clusterrolelist-v1alpha1-rbac-authorization-k8s-io">ClusterRoleList [rbac/v1alpha1]</a></LI>
<LI><a href="#componentstatuslist-v1-core">ComponentStatusList [core/v1]</a></LI>
<LI><a href="#configmaplist-v1-core">ConfigMapList [core/v1]</a></LI>
<LI><a href="#controllerrevisionlist-v1-apps">ControllerRevisionList [apps/v1]</a></LI>
<LI><a href="#controllerrevisionlist-v1beta2-apps">ControllerRevisionList [apps/v1beta2]</a></LI>
<LI><a href="#controllerrevisionlist-v1beta1-apps">ControllerRevisionList [apps/v1beta1]</a></LI>
<LI><a href="#cronjoblist-v1beta1-batch">CronJobList [batch/v1beta1]</a></LI>
<LI><a href="#cronjoblist-v2alpha1-batch">CronJobList [batch/v2alpha1]</a></LI>
<LI><a href="#customresourcedefinitionlist-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionList [apiextensions/v1beta1]</a></LI>
<LI><a href="#daemonsetlist-v1-apps">DaemonSetList [apps/v1]</a></LI>
<LI><a href="#daemonsetlist-v1beta2-apps">DaemonSetList [apps/v1beta2]</a></LI>
<LI><a href="#daemonsetlist-v1beta1-extensions">DaemonSetList [extensions/v1beta1]</a></LI>
<LI><a href="#deploymentlist-v1-apps">DeploymentList [apps/v1]</a></LI>
<LI><a href="#deploymentlist-v1beta2-apps">DeploymentList [apps/v1beta2]</a></LI>
<LI><a href="#deploymentlist-v1beta1-apps">DeploymentList [apps/v1beta1]</a></LI>
<LI><a href="#deploymentlist-v1beta1-extensions">DeploymentList [extensions/v1beta1]</a></LI>
<LI><a href="#endpointslist-v1-core">EndpointsList [core/v1]</a></LI>
<LI><a href="#eventlist-v1-core">EventList [core/v1]</a></LI>
<LI><a href="#eventlist-v1beta1-events-k8s-io">EventList [events/v1beta1]</a></LI>
<LI><a href="#horizontalpodautoscalerlist-v1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v1]</a></LI>
<LI><a href="#horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2beta1]</a></LI>
<LI><a href="#ingresslist-v1beta1-extensions">IngressList [extensions/v1beta1]</a></LI>
<LI><a href="#initializerconfigurationlist-v1alpha1-admissionregistration-k8s-io">InitializerConfigurationList [admissionregistration/v1alpha1]</a></LI>
<LI><a href="#joblist-v1-batch">JobList [batch/v1]</a></LI>
<LI><a href="#limitrangelist-v1-core">LimitRangeList [core/v1]</a></LI>
<LI><a href="#mutatingwebhookconfigurationlist-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfigurationList [admissionregistration/v1beta1]</a></LI>
<LI><a href="#namespacelist-v1-core">NamespaceList [core/v1]</a></LI>
<LI><a href="#networkpolicylist-v1-networking-k8s-io">NetworkPolicyList [networking/v1]</a></LI>
<LI><a href="#networkpolicylist-v1beta1-extensions">NetworkPolicyList [extensions/v1beta1]</a></LI>
<LI><a href="#nodelist-v1-core">NodeList [core/v1]</a></LI>
<LI><a href="#persistentvolumeclaimlist-v1-core">PersistentVolumeClaimList [core/v1]</a></LI>
<LI><a href="#persistentvolumelist-v1-core">PersistentVolumeList [core/v1]</a></LI>
<LI><a href="#poddisruptionbudgetlist-v1beta1-policy">PodDisruptionBudgetList [policy/v1beta1]</a></LI>
<LI><a href="#podlist-v1-core">PodList [core/v1]</a></LI>
<LI><a href="#podpresetlist-v1alpha1-settings-k8s-io">PodPresetList [settings/v1alpha1]</a></LI>
<LI><a href="#podsecuritypolicylist-v1beta1-extensions">PodSecurityPolicyList [extensions/v1beta1]</a></LI>
<LI><a href="#podsecuritypolicylist-v1beta1-policy">PodSecurityPolicyList [policy/v1beta1]</a></LI>
<LI><a href="#podtemplatelist-v1-core">PodTemplateList [core/v1]</a></LI>
<LI><a href="#priorityclasslist-v1beta1-scheduling-k8s-io">PriorityClassList [scheduling/v1beta1]</a></LI>
<LI><a href="#priorityclasslist-v1alpha1-scheduling-k8s-io">PriorityClassList [scheduling/v1alpha1]</a></LI>
<LI><a href="#replicasetlist-v1-apps">ReplicaSetList [apps/v1]</a></LI>
<LI><a href="#replicasetlist-v1beta2-apps">ReplicaSetList [apps/v1beta2]</a></LI>
<LI><a href="#replicasetlist-v1beta1-extensions">ReplicaSetList [extensions/v1beta1]</a></LI>
<LI><a href="#replicationcontrollerlist-v1-core">ReplicationControllerList [core/v1]</a></LI>
<LI><a href="#resourcequotalist-v1-core">ResourceQuotaList [core/v1]</a></LI>
<LI><a href="#rolebindinglist-v1-rbac-authorization-k8s-io">RoleBindingList [rbac/v1]</a></LI>
<LI><a href="#rolebindinglist-v1beta1-rbac-authorization-k8s-io">RoleBindingList [rbac/v1beta1]</a></LI>
<LI><a href="#rolebindinglist-v1alpha1-rbac-authorization-k8s-io">RoleBindingList [rbac/v1alpha1]</a></LI>
<LI><a href="#rolelist-v1-rbac-authorization-k8s-io">RoleList [rbac/v1]</a></LI>
<LI><a href="#rolelist-v1beta1-rbac-authorization-k8s-io">RoleList [rbac/v1beta1]</a></LI>
<LI><a href="#rolelist-v1alpha1-rbac-authorization-k8s-io">RoleList [rbac/v1alpha1]</a></LI>
<LI><a href="#secretlist-v1-core">SecretList [core/v1]</a></LI>
<LI><a href="#serviceaccountlist-v1-core">ServiceAccountList [core/v1]</a></LI>
<LI><a href="#servicelist-v1-core">ServiceList [core/v1]</a></LI>
<LI><a href="#statefulsetlist-v1-apps">StatefulSetList [apps/v1]</a></LI>
<LI><a href="#statefulsetlist-v1beta2-apps">StatefulSetList [apps/v1beta2]</a></LI>
<LI><a href="#statefulsetlist-v1beta1-apps">StatefulSetList [apps/v1beta1]</a></LI>
<LI><a href="#status-v1-meta">Status [meta/v1]</a></LI>
<LI><a href="#storageclasslist-v1-storage-k8s-io">StorageClassList [storage/v1]</a></LI>
<LI><a href="#storageclasslist-v1beta1-storage-k8s-io">StorageClassList [storage/v1beta1]</a></LI>
<LI><a href="#validatingwebhookconfigurationlist-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfigurationList [admissionregistration/v1beta1]</a></LI>
<LI><a href="#volumeattachmentlist-v1beta1-storage-k8s-io">VolumeAttachmentList [storage/v1beta1]</a></LI>
<LI><a href="#volumeattachmentlist-v1alpha1-storage-k8s-io">VolumeAttachmentList [storage/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE><BR /><I>string</I></TD><TD>continue may be set if the user set a limit on the number of items returned, and indicates that the server has more data available. The value is opaque and may be used to issue another request to the endpoint that served this list to retrieve the next set of available objects. Continuing a list may not be possible if the server configuration has changed or more than a few minutes have passed. The resourceVersion field returned when using this continue value will be identical to the value in the first response.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>String that identifies the server&#39;s internal version of this object that can be used by clients to determine when objects have changed. Value must be treated as opaque by clients and passed unmodified back to the server. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency</TD></TR>
<TR><TD><CODE>selfLink</CODE><BR /><I>string</I></TD><TD>selfLink is a URL representing this object. Populated by the system. Read-only.</TD></TR>
</TBODY>
</TABLE>
<H2 id="loadbalanceringress-v1-core">LoadBalancerIngress v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LoadBalancerIngress</CODE></TD></TR>
</TBODY>
</TABLE>
<P>LoadBalancerIngress represents the status of a load-balancer ingress point: traffic intended for the service should be sent to an ingress point.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#loadbalancerstatus-v1-core">LoadBalancerStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>hostname</CODE><BR /><I>string</I></TD><TD>Hostname is set for load-balancer ingress points that are DNS based (typically AWS load-balancers)</TD></TR>
<TR><TD><CODE>ip</CODE><BR /><I>string</I></TD><TD>IP is set for load-balancer ingress points that are IP based (typically GCE or OpenStack load-balancers)</TD></TR>
</TBODY>
</TABLE>
<H2 id="loadbalancerstatus-v1-core">LoadBalancerStatus v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LoadBalancerStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>LoadBalancerStatus represents the status of a load-balancer.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#ingressstatus-v1beta1-extensions">IngressStatus [extensions/v1beta1]</a></LI>
<LI><a href="#servicestatus-v1-core">ServiceStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ingress</CODE><BR /><I><a href="#loadbalanceringress-v1-core">LoadBalancerIngress</a> array</I></TD><TD>Ingress is a list containing ingress points for the load-balancer. Traffic intended for the service should be sent to these ingress points.</TD></TR>
</TBODY>
</TABLE>
<H2 id="localobjectreference-v1-core">LocalObjectReference v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LocalObjectReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cephfsvolumesource-v1-core">CephFSVolumeSource [core/v1]</a></LI>
<LI><a href="#cindervolumesource-v1-core">CinderVolumeSource [core/v1]</a></LI>
<LI><a href="#flexvolumesource-v1-core">FlexVolumeSource [core/v1]</a></LI>
<LI><a href="#iscsivolumesource-v1-core">ISCSIVolumeSource [core/v1]</a></LI>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
<LI><a href="#rbdvolumesource-v1-core">RBDVolumeSource [core/v1]</a></LI>
<LI><a href="#scaleiovolumesource-v1-core">ScaleIOVolumeSource [core/v1]</a></LI>
<LI><a href="#serviceaccount-v1-core">ServiceAccount [core/v1]</a></LI>
<LI><a href="#storageosvolumesource-v1-core">StorageOSVolumeSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
</TBODY>
</TABLE>
<H2 id="localvolumesource-v1-core">LocalVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>LocalVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Local represents directly-attached storage with node affinity (Beta feature)</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>The full path to the volume on the node. It can be either a directory or block device (disk, partition, ...). Directories can be represented only by PersistentVolume with VolumeMode=Filesystem. Block devices can be represented only by VolumeMode=Block, which also requires the BlockVolume alpha feature gate to be enabled.</TD></TR>
</TBODY>
</TABLE>
<H2 id="metricspec-v2beta1-autoscaling">MetricSpec v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>MetricSpec</CODE></TD></TR>
</TBODY>
</TABLE>
<P>MetricSpec specifies how to scale based on a single metric (only `type` and one other matching field should be set at once).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscalerspec-v2beta1-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>external</CODE><BR /><I><a href="#externalmetricsource-v2beta1-autoscaling">ExternalMetricSource</a></I></TD><TD>external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).</TD></TR>
<TR><TD><CODE>object</CODE><BR /><I><a href="#objectmetricsource-v2beta1-autoscaling">ObjectMetricSource</a></I></TD><TD>object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).</TD></TR>
<TR><TD><CODE>pods</CODE><BR /><I><a href="#podsmetricsource-v2beta1-autoscaling">PodsMetricSource</a></I></TD><TD>pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I><a href="#resourcemetricsource-v2beta1-autoscaling">ResourceMetricSource</a></I></TD><TD>resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of metric source. It should be one of &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each mapping to a matching field in the object.</TD></TR>
</TBODY>
</TABLE>
<H2 id="metricstatus-v2beta1-autoscaling">MetricStatus v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>MetricStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>MetricStatus describes the last-read state of a single metric.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>external</CODE><BR /><I><a href="#externalmetricstatus-v2beta1-autoscaling">ExternalMetricStatus</a></I></TD><TD>external refers to a global metric that is not associated with any Kubernetes object. It allows autoscaling based on information coming from components running outside of cluster (for example length of queue in cloud messaging service, or QPS from loadbalancer running outside of cluster).</TD></TR>
<TR><TD><CODE>object</CODE><BR /><I><a href="#objectmetricstatus-v2beta1-autoscaling">ObjectMetricStatus</a></I></TD><TD>object refers to a metric describing a single kubernetes object (for example, hits-per-second on an Ingress object).</TD></TR>
<TR><TD><CODE>pods</CODE><BR /><I><a href="#podsmetricstatus-v2beta1-autoscaling">PodsMetricStatus</a></I></TD><TD>pods refers to a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I><a href="#resourcemetricstatus-v2beta1-autoscaling">ResourceMetricStatus</a></I></TD><TD>resource refers to a resource metric (such as those specified in requests and limits) known to Kubernetes describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>type is the type of metric source. It will be one of &#34;Object&#34;, &#34;Pods&#34; or &#34;Resource&#34;, each corresponds to a matching field in the object.</TD></TR>
</TBODY>
</TABLE>
<H2 id="microtime-v1-meta">MicroTime v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>MicroTime</CODE></TD></TR>
</TBODY>
</TABLE>
<P>MicroTime is version of Time with microsecond level precision.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#event-v1-core">Event [core/v1]</a></LI>
<LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
<LI><a href="#eventseries-v1-core">EventSeries [core/v1]</a></LI>
<LI><a href="#eventseries-v1beta1-events-k8s-io">EventSeries [events/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
<H2 id="nfsvolumesource-v1-core">NFSVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NFSVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents an NFS mount that lasts the lifetime of a pod. NFS volumes do not support ownership management or SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path that is exported by the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the NFS export to be mounted with read-only permissions. Defaults to false. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
<TR><TD><CODE>server</CODE><BR /><I>string</I></TD><TD>Server is the hostname or IP address of the NFS server. More info: https://kubernetes.io/docs/concepts/storage/volumes#nfs</TD></TR>
</TBODY>
</TABLE>
<H2 id="networkpolicyegressrule-v1-networking-k8s-io">NetworkPolicyEgressRule v1 networking.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicyEgressRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NetworkPolicyEgressRule describes a particular set of traffic that is allowed out of pods matched by a NetworkPolicySpec&#39;s podSelector. The traffic must match both ports and to. This type is beta-level in 1.8</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicyegressrule-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ports</CODE><BR /><I><a href="#networkpolicyport-v1-networking-k8s-io">NetworkPolicyPort</a> array</I></TD><TD>List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.</TD></TR>
<TR><TD><CODE>to</CODE><BR /><I><a href="#networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer</a> array</I></TD><TD>List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.</TD></TR>
</TBODY>
</TABLE>
<H2 id="networkpolicyingressrule-v1-networking-k8s-io">NetworkPolicyIngressRule v1 networking.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicyIngressRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NetworkPolicyIngressRule describes a particular set of traffic that is allowed to the pods matched by a NetworkPolicySpec&#39;s podSelector. The traffic must match both ports and from.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicyingressrule-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicyspec-v1-networking-k8s-io">NetworkPolicySpec [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>from</CODE><BR /><I><a href="#networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer</a> array</I></TD><TD>List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least on item, this rule allows traffic only if the traffic matches at least one item in the from list.</TD></TR>
<TR><TD><CODE>ports</CODE><BR /><I><a href="#networkpolicyport-v1-networking-k8s-io">NetworkPolicyPort</a> array</I></TD><TD>List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.</TD></TR>
</TBODY>
</TABLE>
<H2 id="networkpolicypeer-v1-networking-k8s-io">NetworkPolicyPeer v1 networking.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicyPeer</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NetworkPolicyPeer describes a peer to allow traffic from. Only certain combinations of fields are allowed</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicypeer-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicyegressrule-v1-networking-k8s-io">NetworkPolicyEgressRule [networking/v1]</a></LI>
<LI><a href="#networkpolicyingressrule-v1-networking-k8s-io">NetworkPolicyIngressRule [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ipBlock</CODE><BR /><I><a href="#ipblock-v1-networking-k8s-io">IPBlock</a></I></TD><TD>IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.</TD></TR>
<TR><TD><CODE>namespaceSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces. If PodSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects all Pods in the Namespaces selected by NamespaceSelector.</TD></TR>
<TR><TD><CODE>podSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods. If NamespaceSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects the Pods matching PodSelector in the policy&#39;s own Namespace.</TD></TR>
</TBODY>
</TABLE>
<H2 id="networkpolicyport-v1-networking-k8s-io">NetworkPolicyPort v1 networking.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>networking.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NetworkPolicyPort</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NetworkPolicyPort describes a port to allow traffic on</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicyport-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicyegressrule-v1-networking-k8s-io">NetworkPolicyEgressRule [networking/v1]</a></LI>
<LI><a href="#networkpolicyingressrule-v1-networking-k8s-io">NetworkPolicyIngressRule [networking/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>port</CODE></TD><TD>The port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers.</TD></TR>
<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>The protocol (TCP or UDP) which traffic must match. If not specified, this field defaults to TCP.</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodeaddress-v1-core">NodeAddress v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeAddress</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NodeAddress contains information for the node&#39;s address.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>address</CODE><BR /><I>string</I></TD><TD>The node address.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Node address type, one of Hostname, ExternalIP or InternalIP.</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodeaffinity-v1-core">NodeAffinity v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeAffinity</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Node affinity is a group of node affinity scheduling rules.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#affinity-v1-core">Affinity [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>preferredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#preferredschedulingterm-v1-core">PreferredSchedulingTerm</a> array</I></TD><TD>The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding &#34;weight&#34; to the sum if the node matches the corresponding matchExpressions; the node(s) with the highest sum are the most preferred.</TD></TR>
<TR><TD><CODE>requiredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to an update), the system may or may not try to eventually evict the pod from its node.</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodecondition-v1-core">NodeCondition v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NodeCondition contains condition information for a node.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastHeartbeatTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time we got an update on a given condition.</TD></TR>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transit from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human readable message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>(brief) reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of node condition.</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodeconfigsource-v1-core">NodeConfigSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeConfigSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NodeConfigSource specifies a source of node configuration. Exactly one subfield (excluding metadata) must be non-nil.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodeconfigstatus-v1-core">NodeConfigStatus [core/v1]</a></LI>
<LI><a href="#nodespec-v1-core">NodeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>configMap</CODE><BR /><I><a href="#configmapnodeconfigsource-v1-core">ConfigMapNodeConfigSource</a></I></TD><TD>ConfigMap is a reference to a Node&#39;s ConfigMap</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodeconfigstatus-v1-core">NodeConfigStatus v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeConfigStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NodeConfigStatus describes the status of the config assigned by Node.Spec.ConfigSource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>active</CODE><BR /><I><a href="#nodeconfigsource-v1-core">NodeConfigSource</a></I></TD><TD>Active reports the checkpointed config the node is actively using. Active will represent either the current version of the Assigned config, or the current LastKnownGood config, depending on whether attempting to use the Assigned config results in an error.</TD></TR>
<TR><TD><CODE>assigned</CODE><BR /><I><a href="#nodeconfigsource-v1-core">NodeConfigSource</a></I></TD><TD>Assigned reports the checkpointed config the node will try to use. When Node.Spec.ConfigSource is updated, the node checkpoints the associated config payload to local disk, along with a record indicating intended config. The node refers to this record to choose its config checkpoint, and reports this record in Assigned. Assigned only updates in the status after the record has been checkpointed to disk. When the Kubelet is restarted, it tries to make the Assigned config the Active config by loading and validating the checkpointed payload identified by Assigned.</TD></TR>
<TR><TD><CODE>error</CODE><BR /><I>string</I></TD><TD>Error describes any problems reconciling the Spec.ConfigSource to the Active config. Errors may occur, for example, attempting to checkpoint Spec.ConfigSource to the local Assigned record, attempting to checkpoint the payload associated with Spec.ConfigSource, attempting to load or validate the Assigned config, etc. Errors may occur at different points while syncing config. Earlier errors (e.g. download or checkpointing errors) will not result in a rollback to LastKnownGood, and may resolve across Kubelet retries. Later errors (e.g. loading or validating a checkpointed config) will result in a rollback to LastKnownGood. In the latter case, it is usually possible to resolve the error by fixing the config assigned in Spec.ConfigSource. You can find additional information for debugging by searching the error message in the Kubelet log. Error is a human-readable description of the error state; machines can check whether or not Error is empty, but should not rely on the stability of the Error text across Kubelet versions.</TD></TR>
<TR><TD><CODE>lastKnownGood</CODE><BR /><I><a href="#nodeconfigsource-v1-core">NodeConfigSource</a></I></TD><TD>LastKnownGood reports the checkpointed config the node will fall back to when it encounters an error attempting to use the Assigned config. The Assigned config becomes the LastKnownGood config when the node determines that the Assigned config is stable and correct. This is currently implemented as a 10-minute soak period starting when the local record of Assigned config is updated. If the Assigned config is Active at the end of this period, it becomes the LastKnownGood. Note that if Spec.ConfigSource is reset to nil (use local defaults), the LastKnownGood is also immediately reset to nil, because the local default config is always assumed good. You should not make assumptions about the node&#39;s method of determining config stability and correctness, as this may change or become configurable in the future.</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodedaemonendpoints-v1-core">NodeDaemonEndpoints v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeDaemonEndpoints</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NodeDaemonEndpoints lists ports opened by daemons running on the Node.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>kubeletEndpoint</CODE><BR /><I><a href="#daemonendpoint-v1-core">DaemonEndpoint</a></I></TD><TD>Endpoint on which Kubelet is listening.</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodeselector-v1-core">NodeSelector v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeSelector</CODE></TD></TR>
</TBODY>
</TABLE>
<P>A node selector represents the union of the results of one or more label queries over a set of nodes; that is, it represents the OR of the selectors represented by the node selector terms.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodeaffinity-v1-core">NodeAffinity [core/v1]</a></LI>
<LI><a href="#volumenodeaffinity-v1-core">VolumeNodeAffinity [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>nodeSelectorTerms</CODE><BR /><I><a href="#nodeselectorterm-v1-core">NodeSelectorTerm</a> array</I></TD><TD>Required. A list of node selector terms. The terms are ORed.</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodeselectorrequirement-v1-core">NodeSelectorRequirement v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeSelectorRequirement</CODE></TD></TR>
</TBODY>
</TABLE>
<P>A node selector requirement is a selector that contains values, a key, and an operator that relates the key and values.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodeselectorterm-v1-core">NodeSelectorTerm [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The label key that the selector applies to.</TD></TR>
<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>Represents a key&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.</TD></TR>
<TR><TD><CODE>values</CODE><BR /><I>string array</I></TD><TD>An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodeselectorterm-v1-core">NodeSelectorTerm v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeSelectorTerm</CODE></TD></TR>
</TBODY>
</TABLE>
<P>A null or empty node selector term matches no objects. The requirements of them are ANDed. The TopologySelectorTerm type implements a subset of the NodeSelectorTerm.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodeselector-v1-core">NodeSelector [core/v1]</a></LI>
<LI><a href="#preferredschedulingterm-v1-core">PreferredSchedulingTerm [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>matchExpressions</CODE><BR /><I><a href="#nodeselectorrequirement-v1-core">NodeSelectorRequirement</a> array</I></TD><TD>A list of node selector requirements by node&#39;s labels.</TD></TR>
<TR><TD><CODE>matchFields</CODE><BR /><I><a href="#nodeselectorrequirement-v1-core">NodeSelectorRequirement</a> array</I></TD><TD>A list of node selector requirements by node&#39;s fields.</TD></TR>
</TBODY>
</TABLE>
<H2 id="nodesysteminfo-v1-core">NodeSystemInfo v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NodeSystemInfo</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NodeSystemInfo is a set of ids/uuids to uniquely identify the node.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodestatus-v1-core">NodeStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>architecture</CODE><BR /><I>string</I></TD><TD>The Architecture reported by the node</TD></TR>
<TR><TD><CODE>bootID</CODE><BR /><I>string</I></TD><TD>Boot ID reported by the node.</TD></TR>
<TR><TD><CODE>containerRuntimeVersion</CODE><BR /><I>string</I></TD><TD>ContainerRuntime Version reported by the node through runtime remote API (e.g. docker://1.5.0).</TD></TR>
<TR><TD><CODE>kernelVersion</CODE><BR /><I>string</I></TD><TD>Kernel Version reported by the node from &#39;uname -r&#39; (e.g. 3.16.0-0.bpo.4-amd64).</TD></TR>
<TR><TD><CODE>kubeProxyVersion</CODE><BR /><I>string</I></TD><TD>KubeProxy Version reported by the node.</TD></TR>
<TR><TD><CODE>kubeletVersion</CODE><BR /><I>string</I></TD><TD>Kubelet Version reported by the node.</TD></TR>
<TR><TD><CODE>machineID</CODE><BR /><I>string</I></TD><TD>MachineID reported by the node. For unique machine identification in the cluster this field is preferred. Learn more from man(5) machine-id: http://man7.org/linux/man-pages/man5/machine-id.5.html</TD></TR>
<TR><TD><CODE>operatingSystem</CODE><BR /><I>string</I></TD><TD>The Operating System reported by the node</TD></TR>
<TR><TD><CODE>osImage</CODE><BR /><I>string</I></TD><TD>OS Image reported by the node from /etc/os-release (e.g. Debian GNU/Linux 7 (wheezy)).</TD></TR>
<TR><TD><CODE>systemUUID</CODE><BR /><I>string</I></TD><TD>SystemUUID reported by the node. For unique machine identification MachineID is preferred. This field is specific to Red Hat hosts https://access.redhat.com/documentation/en-US/Red_Hat_Subscription_Management/1/html/RHSM/getting-system-uuid.html</TD></TR>
</TBODY>
</TABLE>
<H2 id="nonresourceattributes-v1-authorization-k8s-io">NonResourceAttributes v1 authorization.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NonResourceAttributes</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NonResourceAttributes includes the authorization attributes available for non-resource requests to the Authorizer interface</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#nonresourceattributes-v1beta1-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectaccessreviewspec-v1-authorization-k8s-io">SelfSubjectAccessReviewSpec [authorization/v1]</a></LI>
<LI><a href="#subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is the URL path of the request</TD></TR>
<TR><TD><CODE>verb</CODE><BR /><I>string</I></TD><TD>Verb is the standard HTTP verb</TD></TR>
</TBODY>
</TABLE>
<H2 id="nonresourcerule-v1-authorization-k8s-io">NonResourceRule v1 authorization.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>NonResourceRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>NonResourceRule holds information that describes a rule for the non-resource</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#nonresourcerule-v1beta1-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#subjectrulesreviewstatus-v1-authorization-k8s-io">SubjectRulesReviewStatus [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>nonResourceURLs</CODE><BR /><I>string array</I></TD><TD>NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verb is a list of kubernetes non-resource API verbs, like: get, post, put, delete, patch, head, options. &#34;*&#34; means all.</TD></TR>
</TBODY>
</TABLE>
<H2 id="objectfieldselector-v1-core">ObjectFieldSelector v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ObjectFieldSelector</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ObjectFieldSelector selects an APIVersioned field of an object.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#downwardapivolumefile-v1-core">DownwardAPIVolumeFile [core/v1]</a></LI>
<LI><a href="#envvarsource-v1-core">EnvVarSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>Version of the schema the FieldPath is written in terms of, defaults to &#34;v1&#34;.</TD></TR>
<TR><TD><CODE>fieldPath</CODE><BR /><I>string</I></TD><TD>Path of the field to select in the specified API version.</TD></TR>
</TBODY>
</TABLE>
<H2 id="objectmeta-v1-meta">ObjectMeta v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ObjectMeta</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservice-v1-apiregistration-k8s-io">APIService [apiregistration/v1]</a></LI>
<LI><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService [apiregistration/v1beta1]</a></LI>
<LI><a href="#binding-v1-core">Binding [core/v1]</a></LI>
<LI><a href="#certificatesigningrequest-v1beta1-certificates-k8s-io">CertificateSigningRequest [certificates/v1beta1]</a></LI>
<LI><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole [rbac/v1]</a></LI>
<LI><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole [rbac/v1beta1]</a></LI>
<LI><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole [rbac/v1alpha1]</a></LI>
<LI><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1]</a></LI>
<LI><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1beta1]</a></LI>
<LI><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1alpha1]</a></LI>
<LI><a href="#componentstatus-v1-core">ComponentStatus [core/v1]</a></LI>
<LI><a href="#configmap-v1-core">ConfigMap [core/v1]</a></LI>
<LI><a href="#controllerrevision-v1-apps">ControllerRevision [apps/v1]</a></LI>
<LI><a href="#controllerrevision-v1beta2-apps">ControllerRevision [apps/v1beta2]</a></LI>
<LI><a href="#controllerrevision-v1beta1-apps">ControllerRevision [apps/v1beta1]</a></LI>
<LI><a href="#cronjob-v1beta1-batch">CronJob [batch/v1beta1]</a></LI>
<LI><a href="#cronjob-v2alpha1-batch">CronJob [batch/v2alpha1]</a></LI>
<LI><a href="#customresourcedefinition-v1beta1-apiextensions-k8s-io">CustomResourceDefinition [apiextensions/v1beta1]</a></LI>
<LI><a href="#daemonset-v1-apps">DaemonSet [apps/v1]</a></LI>
<LI><a href="#daemonset-v1beta2-apps">DaemonSet [apps/v1beta2]</a></LI>
<LI><a href="#daemonset-v1beta1-extensions">DaemonSet [extensions/v1beta1]</a></LI>
<LI><a href="#deployment-v1-apps">Deployment [apps/v1]</a></LI>
<LI><a href="#deployment-v1beta2-apps">Deployment [apps/v1beta2]</a></LI>
<LI><a href="#deployment-v1beta1-apps">Deployment [apps/v1beta1]</a></LI>
<LI><a href="#deployment-v1beta1-extensions">Deployment [extensions/v1beta1]</a></LI>
<LI><a href="#endpoints-v1-core">Endpoints [core/v1]</a></LI>
<LI><a href="#event-v1-core">Event [core/v1]</a></LI>
<LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
<LI><a href="#eviction-v1beta1-policy">Eviction [policy/v1beta1]</a></LI>
<LI><a href="#horizontalpodautoscaler-v1-autoscaling">HorizontalPodAutoscaler [autoscaling/v1]</a></LI>
<LI><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler [autoscaling/v2beta1]</a></LI>
<LI><a href="#ingress-v1beta1-extensions">Ingress [extensions/v1beta1]</a></LI>
<LI><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration [admissionregistration/v1alpha1]</a></LI>
<LI><a href="#job-v1-batch">Job [batch/v1]</a></LI>
<LI><a href="#jobtemplatespec-v1beta1-batch">JobTemplateSpec [batch/v1beta1]</a></LI>
<LI><a href="#jobtemplatespec-v2alpha1-batch">JobTemplateSpec [batch/v2alpha1]</a></LI>
<LI><a href="#limitrange-v1-core">LimitRange [core/v1]</a></LI>
<LI><a href="#localsubjectaccessreview-v1-authorization-k8s-io">LocalSubjectAccessReview [authorization/v1]</a></LI>
<LI><a href="#localsubjectaccessreview-v1beta1-authorization-k8s-io">LocalSubjectAccessReview [authorization/v1beta1]</a></LI>
<LI><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration [admissionregistration/v1beta1]</a></LI>
<LI><a href="#namespace-v1-core">Namespace [core/v1]</a></LI>
<LI><a href="#networkpolicy-v1-networking-k8s-io">NetworkPolicy [networking/v1]</a></LI>
<LI><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy [extensions/v1beta1]</a></LI>
<LI><a href="#node-v1-core">Node [core/v1]</a></LI>
<LI><a href="#persistentvolume-v1-core">PersistentVolume [core/v1]</a></LI>
<LI><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim [core/v1]</a></LI>
<LI><a href="#pod-v1-core">Pod [core/v1]</a></LI>
<LI><a href="#poddisruptionbudget-v1beta1-policy">PodDisruptionBudget [policy/v1beta1]</a></LI>
<LI><a href="#podpreset-v1alpha1-settings-k8s-io">PodPreset [settings/v1alpha1]</a></LI>
<LI><a href="#podsecuritypolicy-v1beta1-extensions">PodSecurityPolicy [extensions/v1beta1]</a></LI>
<LI><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy [policy/v1beta1]</a></LI>
<LI><a href="#podtemplate-v1-core">PodTemplate [core/v1]</a></LI>
<LI><a href="#podtemplatespec-v1-core">PodTemplateSpec [core/v1]</a></LI>
<LI><a href="#priorityclass-v1beta1-scheduling-k8s-io">PriorityClass [scheduling/v1beta1]</a></LI>
<LI><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass [scheduling/v1alpha1]</a></LI>
<LI><a href="#replicaset-v1-apps">ReplicaSet [apps/v1]</a></LI>
<LI><a href="#replicaset-v1beta2-apps">ReplicaSet [apps/v1beta2]</a></LI>
<LI><a href="#replicaset-v1beta1-extensions">ReplicaSet [extensions/v1beta1]</a></LI>
<LI><a href="#replicationcontroller-v1-core">ReplicationController [core/v1]</a></LI>
<LI><a href="#resourcequota-v1-core">ResourceQuota [core/v1]</a></LI>
<LI><a href="#role-v1-rbac-authorization-k8s-io">Role [rbac/v1]</a></LI>
<LI><a href="#role-v1beta1-rbac-authorization-k8s-io">Role [rbac/v1beta1]</a></LI>
<LI><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role [rbac/v1alpha1]</a></LI>
<LI><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding [rbac/v1]</a></LI>
<LI><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding [rbac/v1beta1]</a></LI>
<LI><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding [rbac/v1alpha1]</a></LI>
<LI><a href="#scale-v1-autoscaling">Scale [autoscaling/v1]</a></LI>
<LI><a href="#scale-v1beta2-apps">Scale [apps/v1beta2]</a></LI>
<LI><a href="#scale-v1beta1-apps">Scale [apps/v1beta1]</a></LI>
<LI><a href="#scale-v1beta1-extensions">Scale [extensions/v1beta1]</a></LI>
<LI><a href="#secret-v1-core">Secret [core/v1]</a></LI>
<LI><a href="#selfsubjectaccessreview-v1-authorization-k8s-io">SelfSubjectAccessReview [authorization/v1]</a></LI>
<LI><a href="#selfsubjectaccessreview-v1beta1-authorization-k8s-io">SelfSubjectAccessReview [authorization/v1beta1]</a></LI>
<LI><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1]</a></LI>
<LI><a href="#selfsubjectrulesreview-v1beta1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1beta1]</a></LI>
<LI><a href="#service-v1-core">Service [core/v1]</a></LI>
<LI><a href="#serviceaccount-v1-core">ServiceAccount [core/v1]</a></LI>
<LI><a href="#statefulset-v1-apps">StatefulSet [apps/v1]</a></LI>
<LI><a href="#statefulset-v1beta2-apps">StatefulSet [apps/v1beta2]</a></LI>
<LI><a href="#statefulset-v1beta1-apps">StatefulSet [apps/v1beta1]</a></LI>
<LI><a href="#storageclass-v1-storage-k8s-io">StorageClass [storage/v1]</a></LI>
<LI><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass [storage/v1beta1]</a></LI>
<LI><a href="#subjectaccessreview-v1-authorization-k8s-io">SubjectAccessReview [authorization/v1]</a></LI>
<LI><a href="#subjectaccessreview-v1beta1-authorization-k8s-io">SubjectAccessReview [authorization/v1beta1]</a></LI>
<LI><a href="#tokenreview-v1-authentication-k8s-io">TokenReview [authentication/v1]</a></LI>
<LI><a href="#tokenreview-v1beta1-authentication-k8s-io">TokenReview [authentication/v1beta1]</a></LI>
<LI><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration [admissionregistration/v1beta1]</a></LI>
<LI><a href="#volumeattachment-v1beta1-storage-k8s-io">VolumeAttachment [storage/v1beta1]</a></LI>
<LI><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment [storage/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>annotations</CODE><BR /><I>object</I></TD><TD>Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations</TD></TR>
<TR><TD><CODE>clusterName</CODE><BR /><I>string</I></TD><TD>The name of the cluster which the object belongs to. This is used to distinguish resources with same name and namespace in different clusters. This field is not set anywhere right now and apiserver is going to ignore it if set in create or update request.</TD></TR>
<TR><TD><CODE>creationTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC. Populated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>deletionGracePeriodSeconds</CODE><BR /><I>integer</I></TD><TD>Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set. May only be shortened. Read-only.</TD></TR>
<TR><TD><CODE>deletionTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted. This field is set by the server when a graceful deletion is requested by the user, and is not directly settable by a client. The resource is expected to be deleted (no longer visible from resource lists, and not reachable by name) after the time in this field, once the finalizers list is empty. As long as the finalizers list contains items, deletion is blocked. Once the deletionTimestamp is set, this value may not be unset or be set further into the future, although it may be shortened or the resource may be deleted prior to this time. For example, a user may request that a pod is deleted in 30 seconds. The Kubelet will react by sending a graceful termination signal to the containers in the pod. After that 30 seconds, the Kubelet will send a hard termination signal (SIGKILL) to the container and after cleanup, remove the pod from the API. In the presence of network partitions, this object may still exist after this timestamp, until an administrator or automated process can determine the resource is fully terminated. If not set, graceful deletion of the object has not been requested. Populated by the system when a graceful deletion is requested. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>finalizers</CODE><BR /><I>string array</I><BR /><B>patch strategy</B>: <I>merge</I></TD><TD>Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.</TD></TR>
<TR><TD><CODE>generateName</CODE><BR /><I>string</I></TD><TD>GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server. If this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header). Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#idempotency</TD></TR>
<TR><TD><CODE>generation</CODE><BR /><I>integer</I></TD><TD>A sequence number representing a specific generation of the desired state. Populated by the system. Read-only.</TD></TR>
<TR><TD><CODE>initializers</CODE><BR /><I><a href="#initializers-v1-meta">Initializers</a></I></TD><TD>An initializer is a controller which enforces some system invariant at object creation time. This field is a list of initializers that have not yet acted on this object. If nil or empty, this object has been completely initialized. Otherwise, the object is considered uninitialized and is hidden (in list/watch and get calls) from clients that haven&#39;t explicitly asked to observe uninitialized objects. When an object is created, the system will populate this list with the current set of initializers. Only privileged users may set or modify this list. Once it is empty, it may not be modified further by any user.</TD></TR>
<TR><TD><CODE>labels</CODE><BR /><I>object</I></TD><TD>Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace defines the space within each name must be unique. An empty namespace is equivalent to the &#34;default&#34; namespace, but &#34;default&#34; is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty. Must be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces</TD></TR>
<TR><TD><CODE>ownerReferences</CODE><BR /><I><a href="#ownerreference-v1-meta">OwnerReference</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>uid</I></TD><TD>List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed. May be used for optimistic concurrency, change detection, and the watch operation on a resource or set of resources. Clients must treat these values as opaque and passed unmodified back to the server. They may only be valid for a particular resource or set of resources. Populated by the system. Read-only. Value must be treated as opaque by clients and . More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency</TD></TR>
<TR><TD><CODE>selfLink</CODE><BR /><I>string</I></TD><TD>SelfLink is a URL representing this object. Populated by the system. Read-only.</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID is the unique in time and space value for this object. It is typically generated by the server on successful creation of a resource and is not allowed to change on PUT operations. Populated by the system. Read-only. More info: http://kubernetes.io/docs/user-guide/identifiers#uids</TD></TR>
</TBODY>
</TABLE>
<H2 id="objectmetricsource-v2beta1-autoscaling">ObjectMetricSource v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ObjectMetricSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ObjectMetricSource indicates how to scale on a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#metricspec-v2beta1-autoscaling">MetricSpec [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question.</TD></TR>
<TR><TD><CODE>target</CODE><BR /><I><a href="#crossversionobjectreference-v2beta1-autoscaling">CrossVersionObjectReference</a></I></TD><TD>target is the described Kubernetes object.</TD></TR>
<TR><TD><CODE>targetValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetValue is the target value of the metric (as a quantity).</TD></TR>
</TBODY>
</TABLE>
<H2 id="objectmetricstatus-v2beta1-autoscaling">ObjectMetricStatus v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ObjectMetricStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ObjectMetricStatus indicates the current value of a metric describing a kubernetes object (for example, hits-per-second on an Ingress object).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#metricstatus-v2beta1-autoscaling">MetricStatus [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>currentValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentValue is the current value of the metric (as a quantity).</TD></TR>
<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question.</TD></TR>
<TR><TD><CODE>target</CODE><BR /><I><a href="#crossversionobjectreference-v2beta1-autoscaling">CrossVersionObjectReference</a></I></TD><TD>target is the described Kubernetes object.</TD></TR>
</TBODY>
</TABLE>
<H2 id="objectreference-v1-core">ObjectReference v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ObjectReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ObjectReference contains enough information to let you inspect or modify the referred object.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#binding-v1-core">Binding [core/v1]</a></LI>
<LI><a href="#cronjobstatus-v1beta1-batch">CronJobStatus [batch/v1beta1]</a></LI>
<LI><a href="#cronjobstatus-v2alpha1-batch">CronJobStatus [batch/v2alpha1]</a></LI>
<LI><a href="#endpointaddress-v1-core">EndpointAddress [core/v1]</a></LI>
<LI><a href="#event-v1-core">Event [core/v1]</a></LI>
<LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#serviceaccount-v1-core">ServiceAccount [core/v1]</a></LI>
<LI><a href="#storageospersistentvolumesource-v1-core">StorageOSPersistentVolumeSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent.</TD></TR>
<TR><TD><CODE>fieldPath</CODE><BR /><I>string</I></TD><TD>If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: &#34;spec.containers{name}&#34; (where &#34;name&#34; refers to the name of the container that triggered the event) or if no container name is specified &#34;spec.containers[2]&#34; (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/</TD></TR>
<TR><TD><CODE>resourceVersion</CODE><BR /><I>string</I></TD><TD>Specific resourceVersion to which this reference is made, if any. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#concurrency-control-and-consistency</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids</TD></TR>
</TBODY>
</TABLE>
<H2 id="ownerreference-v1-meta">OwnerReference v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>OwnerReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>OwnerReference contains enough information to let you identify an owning object. Currently, an owning object must be in the same namespace, so there is no namespace field.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#objectmeta-v1-meta">ObjectMeta [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent.</TD></TR>
<TR><TD><CODE>blockOwnerDeletion</CODE><BR /><I>boolean</I></TD><TD>If true, AND if the owner has the &#34;foregroundDeletion&#34; finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. Defaults to false. To set this field, a user needs &#34;delete&#34; permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.</TD></TR>
<TR><TD><CODE>controller</CODE><BR /><I>boolean</I></TD><TD>If true, this reference points to the managing controller.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID of the referent. More info: http://kubernetes.io/docs/user-guide/identifiers#uids</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-v1-meta">Patch v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Patch</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Patch is provided to give a concrete name and type to the Kubernetes PATCH request body.</P>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
<H2 id="persistentvolumeclaimcondition-v1-core">PersistentVolumeClaimCondition v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PersistentVolumeClaimCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PersistentVolumeClaimCondition contails details about state of pvc</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumeclaimstatus-v1-core">PersistentVolumeClaimStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastProbeTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time we probed the condition.</TD></TR>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human-readable message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Unique, this should be a short, machine understandable string that gives the reason for condition&#39;s last transition. If it reports &#34;ResizeStarted&#34; that means the underlying persistent volume is being resized.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD></TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="persistentvolumeclaimvolumesource-v1-core">PersistentVolumeClaimVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PersistentVolumeClaimVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PersistentVolumeClaimVolumeSource references the user&#39;s PVC in the same namespace. This volume finds the bound PV and mounts that volume for the pod. A PersistentVolumeClaimVolumeSource is, essentially, a wrapper around another type of volume that is owned by someone else (the system).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>claimName</CODE><BR /><I>string</I></TD><TD>ClaimName is the name of a PersistentVolumeClaim in the same namespace as the pod using this volume. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Will force the ReadOnly setting in VolumeMounts. Default false.</TD></TR>
</TBODY>
</TABLE>
<H2 id="photonpersistentdiskvolumesource-v1-core">PhotonPersistentDiskVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PhotonPersistentDiskVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Photon Controller persistent disk resource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>pdID</CODE><BR /><I>string</I></TD><TD>ID that identifies Photon Controller persistent disk</TD></TR>
</TBODY>
</TABLE>
<H2 id="podaffinity-v1-core">PodAffinity v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodAffinity</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Pod affinity is a group of inter pod affinity scheduling rules.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#affinity-v1-core">Affinity [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>preferredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#weightedpodaffinityterm-v1-core">WeightedPodAffinityTerm</a> array</I></TD><TD>The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding &#34;weight&#34; to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.</TD></TR>
<TR><TD><CODE>requiredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#podaffinityterm-v1-core">PodAffinityTerm</a> array</I></TD><TD>If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.</TD></TR>
</TBODY>
</TABLE>
<H2 id="podaffinityterm-v1-core">PodAffinityTerm v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodAffinityTerm</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Defines a set of pods (namely those matching the labelSelector relative to the given namespace(s)) that this pod should be co-located (affinity) or not co-located (anti-affinity) with, where co-located is defined as running on a node whose value of the label with key &lt;topologyKey&gt; matches that of any node on which a pod of the set of pods is running</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podaffinity-v1-core">PodAffinity [core/v1]</a></LI>
<LI><a href="#podantiaffinity-v1-core">PodAntiAffinity [core/v1]</a></LI>
<LI><a href="#weightedpodaffinityterm-v1-core">WeightedPodAffinityTerm [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>labelSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over a set of resources, in this case pods.</TD></TR>
<TR><TD><CODE>namespaces</CODE><BR /><I>string array</I></TD><TD>namespaces specifies which namespaces the labelSelector applies to (matches against); null or empty list means &#34;this pod&#39;s namespace&#34;</TD></TR>
<TR><TD><CODE>topologyKey</CODE><BR /><I>string</I></TD><TD>This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.</TD></TR>
</TBODY>
</TABLE>
<H2 id="podantiaffinity-v1-core">PodAntiAffinity v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodAntiAffinity</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Pod anti affinity is a group of inter pod anti affinity scheduling rules.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#affinity-v1-core">Affinity [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>preferredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#weightedpodaffinityterm-v1-core">WeightedPodAffinityTerm</a> array</I></TD><TD>The scheduler will prefer to schedule pods to nodes that satisfy the anti-affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling anti-affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding &#34;weight&#34; to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.</TD></TR>
<TR><TD><CODE>requiredDuringSchedulingIgnoredDuringExecution</CODE><BR /><I><a href="#podaffinityterm-v1-core">PodAffinityTerm</a> array</I></TD><TD>If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.</TD></TR>
</TBODY>
</TABLE>
<H2 id="podcondition-v1-core">PodCondition v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodCondition contains details for the current condition of this pod.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podstatus-v1-core">PodStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastProbeTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time we probed the condition.</TD></TR>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human-readable message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status is the status of the condition. Can be True, False, Unknown. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditions</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is the type of the condition. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#pod-conditions</TD></TR>
</TBODY>
</TABLE>
<H2 id="poddnsconfig-v1-core">PodDNSConfig v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodDNSConfig</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodDNSConfig defines the DNS parameters of a pod in addition to those generated from DNSPolicy.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>nameservers</CODE><BR /><I>string array</I></TD><TD>A list of DNS name server IP addresses. This will be appended to the base nameservers generated from DNSPolicy. Duplicated nameservers will be removed.</TD></TR>
<TR><TD><CODE>options</CODE><BR /><I><a href="#poddnsconfigoption-v1-core">PodDNSConfigOption</a> array</I></TD><TD>A list of DNS resolver options. This will be merged with the base options generated from DNSPolicy. Duplicated entries will be removed. Resolution options given in Options will override those that appear in the base DNSPolicy.</TD></TR>
<TR><TD><CODE>searches</CODE><BR /><I>string array</I></TD><TD>A list of DNS search domains for host-name lookup. This will be appended to the base search paths generated from DNSPolicy. Duplicated search paths will be removed.</TD></TR>
</TBODY>
</TABLE>
<H2 id="poddnsconfigoption-v1-core">PodDNSConfigOption v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodDNSConfigOption</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodDNSConfigOption defines DNS resolver options of a pod.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#poddnsconfig-v1-core">PodDNSConfig [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Required.</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="podreadinessgate-v1-core">PodReadinessGate v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodReadinessGate</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodReadinessGate contains the reference to a pod condition</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>conditionType</CODE><BR /><I>string</I></TD><TD>ConditionType refers to a condition in the pod&#39;s condition list with matching type.</TD></TR>
</TBODY>
</TABLE>
<H2 id="podsecuritycontext-v1-core">PodSecurityContext v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PodSecurityContext</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodSecurityContext holds pod-level security attributes and common container settings. Some fields are also present in container.securityContext. Field values of container.securityContext take precedence over field values of PodSecurityContext.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsGroup</CODE><BR /><I>integer</I></TD><TD>A special supplemental group that applies to all containers in a pod. Some volume types allow the Kubelet to change the ownership of that volume to be owned by the pod: 1. The owning GID will be the FSGroup 2. The setgid bit is set (new files created in the volume will be owned by FSGroup) 3. The permission bits are OR&#39;d with rw-rw---- If unset, the Kubelet will not modify the ownership and permissions of any volume.</TD></TR>
<TR><TD><CODE>runAsGroup</CODE><BR /><I>integer</I></TD><TD>The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.</TD></TR>
<TR><TD><CODE>runAsNonRoot</CODE><BR /><I>boolean</I></TD><TD>Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.</TD></TR>
<TR><TD><CODE>runAsUser</CODE><BR /><I>integer</I></TD><TD>The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.</TD></TR>
<TR><TD><CODE>seLinuxOptions</CODE><BR /><I><a href="#selinuxoptions-v1-core">SELinuxOptions</a></I></TD><TD>The SELinux context to be applied to all containers. If unspecified, the container runtime will allocate a random SELinux context for each container. May also be set in SecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence for that container.</TD></TR>
<TR><TD><CODE>supplementalGroups</CODE><BR /><I>integer array</I></TD><TD>A list of groups applied to the first process run in each container, in addition to the container&#39;s primary GID. If unspecified, no groups will be added to any container.</TD></TR>
<TR><TD><CODE>sysctls</CODE><BR /><I><a href="#sysctl-v1-core">Sysctl</a> array</I></TD><TD>Sysctls hold a list of namespaced sysctls used for the pod. Pods with unsupported sysctls (by the container runtime) might fail to launch.</TD></TR>
</TBODY>
</TABLE>
<H2 id="podsmetricsource-v2beta1-autoscaling">PodsMetricSource v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>PodsMetricSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodsMetricSource indicates how to scale on a metric describing each pod in the current scale target (for example, transactions-processed-per-second). The values will be averaged together before being compared to the target value.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#metricspec-v2beta1-autoscaling">MetricSpec [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question</TD></TR>
<TR><TD><CODE>targetAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetAverageValue is the target value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
</TBODY>
</TABLE>
<H2 id="podsmetricstatus-v2beta1-autoscaling">PodsMetricStatus v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>PodsMetricStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PodsMetricStatus indicates the current value of a metric describing each pod in the current scale target (for example, transactions-processed-per-second).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#metricstatus-v2beta1-autoscaling">MetricStatus [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>currentAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentAverageValue is the current value of the average of the metric across all relevant pods (as a quantity)</TD></TR>
<TR><TD><CODE>metricName</CODE><BR /><I>string</I></TD><TD>metricName is the name of the metric in question</TD></TR>
</TBODY>
</TABLE>
<H2 id="policyrule-v1-rbac-authorization-k8s-io">PolicyRule v1 rbac.authorization.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PolicyRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#policyrule-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
<a href="#policyrule-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrole-v1-rbac-authorization-k8s-io">ClusterRole [rbac/v1]</a></LI>
<LI><a href="#role-v1-rbac-authorization-k8s-io">Role [rbac/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.</TD></TR>
<TR><TD><CODE>nonResourceURLs</CODE><BR /><I>string array</I></TD><TD>NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as &#34;pods&#34; or &#34;secrets&#34;) or non-resource URL paths (such as &#34;/api&#34;), but not both.</TD></TR>
<TR><TD><CODE>resourceNames</CODE><BR /><I>string array</I></TD><TD>ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to. ResourceAll represents all resources.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verbs is a list of Verbs that apply to ALL the ResourceKinds and AttributeRestrictions contained in this rule. VerbAll represents all kinds.</TD></TR>
</TBODY>
</TABLE>
<H2 id="portworxvolumesource-v1-core">PortworxVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PortworxVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>PortworxVolumeSource represents a Portworx volume resource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>FSType represents the filesystem type to mount Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>volumeID</CODE><BR /><I>string</I></TD><TD>VolumeID uniquely identifies a Portworx volume</TD></TR>
</TBODY>
</TABLE>
<H2 id="preconditions-v1-meta">Preconditions v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Preconditions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Preconditions must be fulfilled before an operation (update, delete, etc.) is carried out.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deleteoptions-v1-meta">DeleteOptions [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>Specifies the target UID.</TD></TR>
</TBODY>
</TABLE>
<H2 id="preferredschedulingterm-v1-core">PreferredSchedulingTerm v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>PreferredSchedulingTerm</CODE></TD></TR>
</TBODY>
</TABLE>
<P>An empty preferred scheduling term matches all objects with implicit weight 0 (i.e. it&#39;s a no-op). A null preferred scheduling term matches no objects (i.e. is also a no-op).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodeaffinity-v1-core">NodeAffinity [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>preference</CODE><BR /><I><a href="#nodeselectorterm-v1-core">NodeSelectorTerm</a></I></TD><TD>A node selector term, associated with the corresponding weight.</TD></TR>
<TR><TD><CODE>weight</CODE><BR /><I>integer</I></TD><TD>Weight associated with matching the corresponding nodeSelectorTerm, in the range 1-100.</TD></TR>
</TBODY>
</TABLE>
<H2 id="probe-v1-core">Probe v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Probe</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#container-v1-core">Container [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>exec</CODE><BR /><I><a href="#execaction-v1-core">ExecAction</a></I></TD><TD>One and only one of the following should be specified. Exec specifies the action to take.</TD></TR>
<TR><TD><CODE>failureThreshold</CODE><BR /><I>integer</I></TD><TD>Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1.</TD></TR>
<TR><TD><CODE>httpGet</CODE><BR /><I><a href="#httpgetaction-v1-core">HTTPGetAction</a></I></TD><TD>HTTPGet specifies the http request to perform.</TD></TR>
<TR><TD><CODE>initialDelaySeconds</CODE><BR /><I>integer</I></TD><TD>Number of seconds after the container has started before liveness probes are initiated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</TD></TR>
<TR><TD><CODE>periodSeconds</CODE><BR /><I>integer</I></TD><TD>How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.</TD></TR>
<TR><TD><CODE>successThreshold</CODE><BR /><I>integer</I></TD><TD>Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness. Minimum value is 1.</TD></TR>
<TR><TD><CODE>tcpSocket</CODE><BR /><I><a href="#tcpsocketaction-v1-core">TCPSocketAction</a></I></TD><TD>TCPSocket specifies an action involving a TCP port. TCP hooks not yet supported</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE><BR /><I>integer</I></TD><TD>Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes</TD></TR>
</TBODY>
</TABLE>
<H2 id="projectedvolumesource-v1-core">ProjectedVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ProjectedVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a projected volume source</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>defaultMode</CODE><BR /><I>integer</I></TD><TD>Mode bits to use on created files by default. Must be a value between 0 and 0777. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.</TD></TR>
<TR><TD><CODE>sources</CODE><BR /><I><a href="#volumeprojection-v1-core">VolumeProjection</a> array</I></TD><TD>list of volume projections</TD></TR>
</TBODY>
</TABLE>
<H2 id="quantity-resource-core">Quantity resource core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>resource</CODE></TD><TD><CODE>Quantity</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and Int64() accessors.
The serialization format is:
&lt;quantity&gt; ::= &lt;signedNumber&gt;&lt;suffix&gt;
(Note that &lt;suffix&gt; may be empty, from the &#34;&#34; case in &lt;decimalSI&gt;.)
&lt;digit&gt; ::= 0 | 1 | ... | 9 &lt;digits&gt; ::= &lt;digit&gt; | &lt;digit&gt;&lt;digits&gt; &lt;number&gt; ::= &lt;digits&gt; | &lt;digits&gt;.&lt;digits&gt; | &lt;digits&gt;. | .&lt;digits&gt; &lt;sign&gt; ::= &#34;+&#34; | &#34;-&#34; &lt;signedNumber&gt; ::= &lt;number&gt; | &lt;sign&gt;&lt;number&gt; &lt;suffix&gt; ::= &lt;binarySI&gt; | &lt;decimalExponent&gt; | &lt;decimalSI&gt; &lt;binarySI&gt; ::= Ki | Mi | Gi | Ti | Pi | Ei
(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)
&lt;decimalSI&gt; ::= m | &#34;&#34; | k | M | G | T | P | E
(Note that 1024 = 1Ki but 1000 = 1k; I didn&#39;t choose the capitalization.)
&lt;decimalExponent&gt; ::= &#34;e&#34; &lt;signedNumber&gt; | &#34;E&#34; &lt;signedNumber&gt;
No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities.
When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized.
Before serializing, Quantity will be put in &#34;canonical form&#34;. This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that:
a. No precision is lost
b. No fractional digits will be emitted
c. The exponent (or suffix) is as large as possible.
The sign will be omitted unless the number is negative.
Examples:
1.5 will be serialized as &#34;1500m&#34;
1.5Gi will be serialized as &#34;1536Mi&#34;
NOTE: We reserve the right to amend this canonical format, perhaps to
allow 1.5 to be canonical.
or after March 2015.
Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.
Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don&#39;t diff.)
This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#emptydirvolumesource-v1-core">EmptyDirVolumeSource [core/v1]</a></LI>
<LI><a href="#externalmetricsource-v2beta1-autoscaling">ExternalMetricSource [autoscaling/v2beta1]</a></LI>
<LI><a href="#externalmetricstatus-v2beta1-autoscaling">ExternalMetricStatus [autoscaling/v2beta1]</a></LI>
<LI><a href="#objectmetricsource-v2beta1-autoscaling">ObjectMetricSource [autoscaling/v2beta1]</a></LI>
<LI><a href="#objectmetricstatus-v2beta1-autoscaling">ObjectMetricStatus [autoscaling/v2beta1]</a></LI>
<LI><a href="#podsmetricsource-v2beta1-autoscaling">PodsMetricSource [autoscaling/v2beta1]</a></LI>
<LI><a href="#podsmetricstatus-v2beta1-autoscaling">PodsMetricStatus [autoscaling/v2beta1]</a></LI>
<LI><a href="#resourcefieldselector-v1-core">ResourceFieldSelector [core/v1]</a></LI>
<LI><a href="#resourcemetricsource-v2beta1-autoscaling">ResourceMetricSource [autoscaling/v2beta1]</a></LI>
<LI><a href="#resourcemetricstatus-v2beta1-autoscaling">ResourceMetricStatus [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
<H2 id="quobytevolumesource-v1-core">QuobyteVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>QuobyteVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Quobyte mount that lasts the lifetime of a pod. Quobyte volumes do not support ownership management or SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>Group to map volume access to Default is no group</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the Quobyte volume to be mounted with read-only permissions. Defaults to false.</TD></TR>
<TR><TD><CODE>registry</CODE><BR /><I>string</I></TD><TD>Registry represents a single or multiple Quobyte Registry services specified as a string as host:port pair (multiple entries are separated with commas) which acts as the central registry for volumes</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>User to map volume access to Defaults to serivceaccount user</TD></TR>
<TR><TD><CODE>volume</CODE><BR /><I>string</I></TD><TD>Volume is a string that references an already created Quobyte volume by name.</TD></TR>
</TBODY>
</TABLE>
<H2 id="rbdpersistentvolumesource-v1-core">RBDPersistentVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RBDPersistentVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd</TD></TR>
<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>The rados image name. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>keyring</CODE><BR /><I>string</I></TD><TD>Keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>A collection of Ceph monitors. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>The rados pool name. Default is rbd. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>SecretRef is name of the authentication secret for RBDUser. If provided overrides keyring. Default is nil. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>The rados user name. Default is admin. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
</TBODY>
</TABLE>
<H2 id="rbdvolumesource-v1-core">RBDVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RBDVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a Rados Block Device mount that lasts the lifetime of a pod. RBD volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type of the volume that you want to mount. Tip: Ensure that the filesystem type is supported by the host operating system. Examples: &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified. More info: https://kubernetes.io/docs/concepts/storage/volumes#rbd</TD></TR>
<TR><TD><CODE>image</CODE><BR /><I>string</I></TD><TD>The rados image name. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>keyring</CODE><BR /><I>string</I></TD><TD>Keyring is the path to key ring for RBDUser. Default is /etc/ceph/keyring. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>monitors</CODE><BR /><I>string array</I></TD><TD>A collection of Ceph monitors. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>pool</CODE><BR /><I>string</I></TD><TD>The rados pool name. Default is rbd. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>ReadOnly here will force the ReadOnly setting in VolumeMounts. Defaults to false. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>SecretRef is name of the authentication secret for RBDUser. If provided overrides keyring. Default is nil. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>The rados user name. Default is admin. More info: https://releases.k8s.io/HEAD/examples/volumes/rbd/README.md#how-to-use-it</TD></TR>
</TBODY>
</TABLE>
<H2 id="replicasetcondition-v1-apps">ReplicaSetCondition v1 apps</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ReplicaSetCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ReplicaSetCondition describes the state of a replica set at a certain point.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#replicasetcondition-v1beta2-apps">v1beta2</a>
<a href="#replicasetcondition-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicasetstatus-v1-apps">ReplicaSetStatus [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of replica set condition.</TD></TR>
</TBODY>
</TABLE>
<H2 id="replicationcontrollercondition-v1-core">ReplicationControllerCondition v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ReplicationControllerCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ReplicationControllerCondition describes the state of a replication controller at a certain point.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicationcontrollerstatus-v1-core">ReplicationControllerStatus [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of replication controller condition.</TD></TR>
</TBODY>
</TABLE>
<H2 id="resourceattributes-v1-authorization-k8s-io">ResourceAttributes v1 authorization.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceAttributes</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceAttributes includes the authorization attributes available for resource requests to the Authorizer interface</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#resourceattributes-v1beta1-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectaccessreviewspec-v1-authorization-k8s-io">SelfSubjectAccessReviewSpec [authorization/v1]</a></LI>
<LI><a href="#subjectaccessreviewspec-v1-authorization-k8s-io">SubjectAccessReviewSpec [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>Group is the API Group of the Resource. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the resource being requested for a &#34;get&#34; or deleted for a &#34;delete&#34;. &#34;&#34; (empty) means all.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of the action being requested. Currently, there is no distinction between no namespace and all namespaces &#34;&#34; (empty) is defaulted for LocalSubjectAccessReviews &#34;&#34; (empty) is empty for cluster-scoped resources &#34;&#34; (empty) means &#34;all&#34; for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>Resource is one of the existing resource types. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>subresource</CODE><BR /><I>string</I></TD><TD>Subresource is one of the existing resource types. &#34;&#34; means none.</TD></TR>
<TR><TD><CODE>verb</CODE><BR /><I>string</I></TD><TD>Verb is a kubernetes resource API verb, like: get, list, watch, create, update, delete, proxy. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>Version is the API Version of the Resource. &#34;*&#34; means all.</TD></TR>
</TBODY>
</TABLE>
<H2 id="resourcefieldselector-v1-core">ResourceFieldSelector v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceFieldSelector</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceFieldSelector represents container resources (cpu, memory) and their output format</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#downwardapivolumefile-v1-core">DownwardAPIVolumeFile [core/v1]</a></LI>
<LI><a href="#envvarsource-v1-core">EnvVarSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>containerName</CODE><BR /><I>string</I></TD><TD>Container name: required for volumes, optional for env vars</TD></TR>
<TR><TD><CODE>divisor</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>Specifies the output format of the exposed resources, defaults to &#34;1&#34;</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>Required: resource to select</TD></TR>
</TBODY>
</TABLE>
<H2 id="resourcemetricsource-v2beta1-autoscaling">ResourceMetricSource v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ResourceMetricSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceMetricSource indicates how to scale on a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory). The values will be averaged together before being compared to the target. Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source. Only one &#34;target&#34; type should be set.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#metricspec-v2beta1-autoscaling">MetricSpec [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
<TR><TD><CODE>targetAverageUtilization</CODE><BR /><I>integer</I></TD><TD>targetAverageUtilization is the target value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods.</TD></TR>
<TR><TD><CODE>targetAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>targetAverageValue is the target value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the &#34;pods&#34; metric source type.</TD></TR>
</TBODY>
</TABLE>
<H2 id="resourcemetricstatus-v2beta1-autoscaling">ResourceMetricStatus v2beta1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>ResourceMetricStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceMetricStatus indicates the current value of a resource metric known to Kubernetes, as specified in requests and limits, describing each pod in the current scale target (e.g. CPU or memory). Such metrics are built in to Kubernetes, and have special scaling options on top of those available to normal per-pod metrics using the &#34;pods&#34; source.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#metricstatus-v2beta1-autoscaling">MetricStatus [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>currentAverageUtilization</CODE><BR /><I>integer</I></TD><TD>currentAverageUtilization is the current value of the average of the resource metric across all relevant pods, represented as a percentage of the requested value of the resource for the pods. It will only be present if `targetAverageValue` was set in the corresponding metric specification.</TD></TR>
<TR><TD><CODE>currentAverageValue</CODE><BR /><I><a href="#quantity-resource-core">Quantity</a></I></TD><TD>currentAverageValue is the current value of the average of the resource metric across all relevant pods, as a raw value (instead of as a percentage of the request), similar to the &#34;pods&#34; metric source type. It will always be set, regardless of the corresponding metric specification.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name is the name of the resource in question.</TD></TR>
</TBODY>
</TABLE>
<H2 id="resourcerequirements-v1-core">ResourceRequirements v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceRequirements</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceRequirements describes the compute resource requirements.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#container-v1-core">Container [core/v1]</a></LI>
<LI><a href="#persistentvolumeclaimspec-v1-core">PersistentVolumeClaimSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>limits</CODE><BR /><I>object</I></TD><TD>Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/</TD></TR>
<TR><TD><CODE>requests</CODE><BR /><I>object</I></TD><TD>Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/</TD></TR>
</TBODY>
</TABLE>
<H2 id="resourcerule-v1-authorization-k8s-io">ResourceRule v1 authorization.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ResourceRule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ResourceRule is the list of actions the subject is allowed to perform on resources. The list ordering isn&#39;t significant, may contain duplicates, and possibly be incomplete.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#resourcerule-v1beta1-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#subjectrulesreviewstatus-v1-authorization-k8s-io">SubjectRulesReviewStatus [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>resourceNames</CODE><BR /><I>string array</I></TD><TD>ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to. &#34;*&#34; means all in the specified apiGroups. &#34;*/foo&#34; represents the subresource &#39;foo&#39; for all resources in the specified apiGroups.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verb is a list of kubernetes resource API verbs, like: get, list, watch, create, update, delete, proxy. &#34;*&#34; means all.</TD></TR>
</TBODY>
</TABLE>
<H2 id="roleref-v1-rbac-authorization-k8s-io">RoleRef v1 rbac.authorization.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RoleRef</CODE></TD></TR>
</TBODY>
</TABLE>
<P>RoleRef contains information that points to the role being used</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#roleref-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
<a href="#roleref-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1]</a></LI>
<LI><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding [rbac/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup is the group for the resource being referenced</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the type of resource being referenced</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of resource being referenced</TD></TR>
</TBODY>
</TABLE>
<H2 id="rollbackconfig-v1beta1-apps">RollbackConfig v1beta1 apps</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RollbackConfig</CODE></TD></TR>
</TBODY>
</TABLE>
<P>DEPRECATED.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentrollback-v1beta1-apps">DeploymentRollback [apps/v1beta1]</a></LI>
<LI><a href="#deploymentspec-v1beta1-apps">DeploymentSpec [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>revision</CODE><BR /><I>integer</I></TD><TD>The revision to rollback to. If set to 0, rollback to the last revision.</TD></TR>
</TBODY>
</TABLE>
<H2 id="rollingupdatestatefulsetstrategy-v1-apps">RollingUpdateStatefulSetStrategy v1 apps</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>RollingUpdateStatefulSetStrategy</CODE></TD></TR>
</TBODY>
</TABLE>
<P>RollingUpdateStatefulSetStrategy is used to communicate parameter for RollingUpdateStatefulSetStrategyType.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#rollingupdatestatefulsetstrategy-v1beta2-apps">v1beta2</a>
<a href="#rollingupdatestatefulsetstrategy-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetupdatestrategy-v1-apps">StatefulSetUpdateStrategy [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>Partition indicates the ordinal at which the StatefulSet should be partitioned. Default value is 0.</TD></TR>
</TBODY>
</TABLE>
<H2 id="rule-v1alpha1-admissionregistration-k8s-io">Rule v1alpha1 admissionregistration.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>Rule</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Rule is a tuple of APIGroups, APIVersion, and Resources.It is recommended to make sure that all the tuple expansions are valid.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#initializer-v1alpha1-admissionregistration-k8s-io">Initializer [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the API groups the resources belong to. &#39;\*&#39; is all groups. If &#39;\*&#39; is present, the length of the slice must be one. Required.</TD></TR>
<TR><TD><CODE>apiVersions</CODE><BR /><I>string array</I></TD><TD>APIVersions is the API versions the resources belong to. &#39;\*&#39; is all versions. If &#39;\*&#39; is present, the length of the slice must be one. Required.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to. For example: &#39;pods&#39; means pods. &#39;pods/log&#39; means the log subresource of pods. &#39;\*&#39; means all resources, but not subresources. &#39;pods/\*&#39; means all subresources of pods. &#39;\*/scale&#39; means all scale subresources. &#39;\*/\*&#39; means all resources and their subresources. If wildcard is present, the validation rule will ensure resources do not overlap with each other. Depending on the enclosing object, subresources might not be allowed. Required.</TD></TR>
</TBODY>
</TABLE>
<H2 id="rulewithoperations-v1beta1-admissionregistration-k8s-io">RuleWithOperations v1beta1 admissionregistration.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RuleWithOperations</CODE></TD></TR>
</TBODY>
</TABLE>
<P>RuleWithOperations is a tuple of Operations and Resources. It is recommended to make sure that all the tuple expansions are valid.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#webhook-v1beta1-admissionregistration-k8s-io">Webhook [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the API groups the resources belong to. &#39;\*&#39; is all groups. If &#39;\*&#39; is present, the length of the slice must be one. Required.</TD></TR>
<TR><TD><CODE>apiVersions</CODE><BR /><I>string array</I></TD><TD>APIVersions is the API versions the resources belong to. &#39;\*&#39; is all versions. If &#39;\*&#39; is present, the length of the slice must be one. Required.</TD></TR>
<TR><TD><CODE>operations</CODE><BR /><I>string array</I></TD><TD>Operations is the operations the admission hook cares about - CREATE, UPDATE, or * for all operations. If &#39;\*&#39; is present, the length of the slice must be one. Required.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to. For example: &#39;pods&#39; means pods. &#39;pods/log&#39; means the log subresource of pods. &#39;\*&#39; means all resources, but not subresources. &#39;pods/\*&#39; means all subresources of pods. &#39;\*/scale&#39; means all scale subresources. &#39;\*/\*&#39; means all resources and their subresources. If wildcard is present, the validation rule will ensure resources do not overlap with each other. Depending on the enclosing object, subresources might not be allowed. Required.</TD></TR>
</TBODY>
</TABLE>
<H2 id="runasuserstrategyoptions-v1beta1-extensions">RunAsUserStrategyOptions v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RunAsUserStrategyOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>RunAsUserStrategyOptions defines the strategy type and any options used to create the strategy. Deprecated: use RunAsUserStrategyOptions from policy API Group instead.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-extensions">PodSecurityPolicySpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-extensions">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of uids that may be used. If you would like to force a single uid then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate the allowable RunAsUser values that may be set.</TD></TR>
</TBODY>
</TABLE>
<H2 id="selinuxoptions-v1-core">SELinuxOptions v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SELinuxOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SELinuxOptions are the labels to be applied to the container</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritycontext-v1-core">PodSecurityContext [core/v1]</a></LI>
<LI><a href="#selinuxstrategyoptions-v1beta1-extensions">SELinuxStrategyOptions [extensions/v1beta1]</a></LI>
<LI><a href="#selinuxstrategyoptions-v1beta1-policy">SELinuxStrategyOptions [policy/v1beta1]</a></LI>
<LI><a href="#securitycontext-v1-core">SecurityContext [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>level</CODE><BR /><I>string</I></TD><TD>Level is SELinux level label that applies to the container.</TD></TR>
<TR><TD><CODE>role</CODE><BR /><I>string</I></TD><TD>Role is a SELinux role label that applies to the container.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is a SELinux type label that applies to the container.</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>User is a SELinux user label that applies to the container.</TD></TR>
</TBODY>
</TABLE>
<H2 id="selinuxstrategyoptions-v1beta1-extensions">SELinuxStrategyOptions v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SELinuxStrategyOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SELinuxStrategyOptions defines the strategy type and any options used to create the strategy. Deprecated: use SELinuxStrategyOptions from policy API Group instead.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-extensions">PodSecurityPolicySpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate the allowable labels that may be set.</TD></TR>
<TR><TD><CODE>seLinuxOptions</CODE><BR /><I><a href="#selinuxoptions-v1-core">SELinuxOptions</a></I></TD><TD>seLinuxOptions required to run as; required for MustRunAs More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/</TD></TR>
</TBODY>
</TABLE>
<H2 id="scale-v1-autoscaling">Scale v1 autoscaling</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Scale</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Scale represents a scaling request for a resource.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#scale-v1beta2-apps">v1beta2</a>
<a href="#scale-v1beta1-apps">v1beta1</a>
<a href="#scale-v1beta1-extensions">v1beta1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#scalespec-v1-autoscaling">ScaleSpec</a></I></TD><TD>defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#scalestatus-v1-autoscaling">ScaleStatus</a></I></TD><TD>current status of the scale. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status. Read-only.</TD></TR>
</TBODY>
</TABLE>
<H2 id="scaleiopersistentvolumesource-v1-core">ScaleIOPersistentVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ScaleIOPersistentVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ScaleIOPersistentVolumeSource represents a persistent ScaleIO volume</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>gateway</CODE><BR /><I>string</I></TD><TD>The host address of the ScaleIO API Gateway.</TD></TR>
<TR><TD><CODE>protectionDomain</CODE><BR /><I>string</I></TD><TD>The name of the ScaleIO Protection Domain for the configured storage.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#secretreference-v1-core">SecretReference</a></I></TD><TD>SecretRef references to the secret for ScaleIO user and other sensitive information. If this is not provided, Login operation will fail.</TD></TR>
<TR><TD><CODE>sslEnabled</CODE><BR /><I>boolean</I></TD><TD>Flag to enable/disable SSL communication with Gateway, default false</TD></TR>
<TR><TD><CODE>storageMode</CODE><BR /><I>string</I></TD><TD>Indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned.</TD></TR>
<TR><TD><CODE>storagePool</CODE><BR /><I>string</I></TD><TD>The ScaleIO Storage Pool associated with the protection domain.</TD></TR>
<TR><TD><CODE>system</CODE><BR /><I>string</I></TD><TD>The name of the storage system as configured in ScaleIO.</TD></TR>
<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>The name of a volume already created in the ScaleIO system that is associated with this volume source.</TD></TR>
</TBODY>
</TABLE>
<H2 id="scaleiovolumesource-v1-core">ScaleIOVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ScaleIOVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ScaleIOVolumeSource represents a persistent ScaleIO volume</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>gateway</CODE><BR /><I>string</I></TD><TD>The host address of the ScaleIO API Gateway.</TD></TR>
<TR><TD><CODE>protectionDomain</CODE><BR /><I>string</I></TD><TD>The name of the ScaleIO Protection Domain for the configured storage.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>SecretRef references to the secret for ScaleIO user and other sensitive information. If this is not provided, Login operation will fail.</TD></TR>
<TR><TD><CODE>sslEnabled</CODE><BR /><I>boolean</I></TD><TD>Flag to enable/disable SSL communication with Gateway, default false</TD></TR>
<TR><TD><CODE>storageMode</CODE><BR /><I>string</I></TD><TD>Indicates whether the storage for a volume should be ThickProvisioned or ThinProvisioned.</TD></TR>
<TR><TD><CODE>storagePool</CODE><BR /><I>string</I></TD><TD>The ScaleIO Storage Pool associated with the protection domain.</TD></TR>
<TR><TD><CODE>system</CODE><BR /><I>string</I></TD><TD>The name of the storage system as configured in ScaleIO.</TD></TR>
<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>The name of a volume already created in the ScaleIO system that is associated with this volume source.</TD></TR>
</TBODY>
</TABLE>
<H2 id="scopeselector-v1-core">ScopeSelector v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ScopeSelector</CODE></TD></TR>
</TBODY>
</TABLE>
<P>A scope selector represents the AND of the selectors represented by the scoped-resource selector requirements.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#resourcequotaspec-v1-core">ResourceQuotaSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>matchExpressions</CODE><BR /><I><a href="#scopedresourceselectorrequirement-v1-core">ScopedResourceSelectorRequirement</a> array</I></TD><TD>A list of scope selector requirements by scope of the resources.</TD></TR>
</TBODY>
</TABLE>
<H2 id="scopedresourceselectorrequirement-v1-core">ScopedResourceSelectorRequirement v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ScopedResourceSelectorRequirement</CODE></TD></TR>
</TBODY>
</TABLE>
<P>A scoped-resource selector requirement is a selector that contains values, a scope name, and an operator that relates the scope name and values.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#scopeselector-v1-core">ScopeSelector [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>Represents a scope&#39;s relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist.</TD></TR>
<TR><TD><CODE>scopeName</CODE><BR /><I>string</I></TD><TD>The name of the scope that the selector applies to.</TD></TR>
<TR><TD><CODE>values</CODE><BR /><I>string array</I></TD><TD>An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.</TD></TR>
</TBODY>
</TABLE>
<H2 id="secretenvsource-v1-core">SecretEnvSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretEnvSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SecretEnvSource selects a Secret to populate the environment variables with.
The contents of the target Secret&#39;s Data field will represent the key-value pairs as environment variables.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#envfromsource-v1-core">EnvFromSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the Secret must be defined</TD></TR>
</TBODY>
</TABLE>
<H2 id="secretkeyselector-v1-core">SecretKeySelector v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretKeySelector</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SecretKeySelector selects a key of a Secret.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#envvarsource-v1-core">EnvVarSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The key of the secret to select from. Must be a valid secret key.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the Secret or it&#39;s key must be defined</TD></TR>
</TBODY>
</TABLE>
<H2 id="secretprojection-v1-core">SecretProjection v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretProjection</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Adapts a secret into a projected volume.
The contents of the target Secret&#39;s Data field will be presented in a projected volume as files using the keys in the Data field as the file names. Note that this is identical to a secret volume source without the default mode.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeprojection-v1-core">VolumeProjection [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>items</CODE><BR /><I><a href="#keytopath-v1-core">KeyToPath</a> array</I></TD><TD>If unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names</TD></TR>
<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the Secret or its key must be defined</TD></TR>
</TBODY>
</TABLE>
<H2 id="secretreference-v1-core">SecretReference v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#csipersistentvolumesource-v1-core">CSIPersistentVolumeSource [core/v1]</a></LI>
<LI><a href="#cephfspersistentvolumesource-v1-core">CephFSPersistentVolumeSource [core/v1]</a></LI>
<LI><a href="#cinderpersistentvolumesource-v1-core">CinderPersistentVolumeSource [core/v1]</a></LI>
<LI><a href="#flexpersistentvolumesource-v1-core">FlexPersistentVolumeSource [core/v1]</a></LI>
<LI><a href="#iscsipersistentvolumesource-v1-core">ISCSIPersistentVolumeSource [core/v1]</a></LI>
<LI><a href="#rbdpersistentvolumesource-v1-core">RBDPersistentVolumeSource [core/v1]</a></LI>
<LI><a href="#scaleiopersistentvolumesource-v1-core">ScaleIOPersistentVolumeSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is unique within a namespace to reference a secret resource.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace defines the space within which the secret name must be unique.</TD></TR>
</TBODY>
</TABLE>
<H2 id="secretvolumesource-v1-core">SecretVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecretVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Adapts a Secret into a volume.
The contents of the target Secret&#39;s Data field will be presented in a volume as files using the keys in the Data field as the file names. Secret volumes support ownership management and SELinux relabeling.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>defaultMode</CODE><BR /><I>integer</I></TD><TD>Optional: mode bits to use on created files by default. Must be a value between 0 and 0777. Defaults to 0644. Directories within the path are not affected by this setting. This might be in conflict with other options that affect the file mode, like fsGroup, and the result can be other mode bits set.</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#keytopath-v1-core">KeyToPath</a> array</I></TD><TD>If unspecified, each key-value pair in the Data field of the referenced Secret will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the Secret, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the &#39;..&#39; path or start with &#39;..&#39;.</TD></TR>
<TR><TD><CODE>optional</CODE><BR /><I>boolean</I></TD><TD>Specify whether the Secret or it&#39;s keys must be defined</TD></TR>
<TR><TD><CODE>secretName</CODE><BR /><I>string</I></TD><TD>Name of the secret in the pod&#39;s namespace to use. More info: https://kubernetes.io/docs/concepts/storage/volumes#secret</TD></TR>
</TBODY>
</TABLE>
<H2 id="securitycontext-v1-core">SecurityContext v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SecurityContext</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SecurityContext holds security configuration that will be applied to a container. Some fields are present in both SecurityContext and PodSecurityContext. When both are set, the values in SecurityContext take precedence.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#container-v1-core">Container [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowPrivilegeEscalation</CODE><BR /><I>boolean</I></TD><TD>AllowPrivilegeEscalation controls whether a process can gain more privileges than its parent process. This bool directly controls if the no_new_privs flag will be set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged 2) has CAP_SYS_ADMIN</TD></TR>
<TR><TD><CODE>capabilities</CODE><BR /><I><a href="#capabilities-v1-core">Capabilities</a></I></TD><TD>The capabilities to add/drop when running containers. Defaults to the default set of capabilities granted by the container runtime.</TD></TR>
<TR><TD><CODE>privileged</CODE><BR /><I>boolean</I></TD><TD>Run container in privileged mode. Processes in privileged containers are essentially equivalent to root on the host. Defaults to false.</TD></TR>
<TR><TD><CODE>readOnlyRootFilesystem</CODE><BR /><I>boolean</I></TD><TD>Whether this container has a read-only root filesystem. Default is false.</TD></TR>
<TR><TD><CODE>runAsGroup</CODE><BR /><I>integer</I></TD><TD>The GID to run the entrypoint of the container process. Uses runtime default if unset. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.</TD></TR>
<TR><TD><CODE>runAsNonRoot</CODE><BR /><I>boolean</I></TD><TD>Indicates that the container must run as a non-root user. If true, the Kubelet will validate the image at runtime to ensure that it does not run as UID 0 (root) and fail to start the container if it does. If unset or false, no such validation will be performed. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.</TD></TR>
<TR><TD><CODE>runAsUser</CODE><BR /><I>integer</I></TD><TD>The UID to run the entrypoint of the container process. Defaults to user specified in image metadata if unspecified. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.</TD></TR>
<TR><TD><CODE>seLinuxOptions</CODE><BR /><I><a href="#selinuxoptions-v1-core">SELinuxOptions</a></I></TD><TD>The SELinux context to be applied to the container. If unspecified, the container runtime will allocate a random SELinux context for each container. May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence.</TD></TR>
</TBODY>
</TABLE>
<H2 id="serveraddressbyclientcidr-v1-meta">ServerAddressByClientCIDR v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServerAddressByClientCIDR</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ServerAddressByClientCIDR helps the client to determine the server address that they should use, depending on the clientCIDR that they match.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apigroup-v1-meta">APIGroup [meta/v1]</a></LI>
<LI><a href="#apiversions-v1-meta">APIVersions [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>clientCIDR</CODE><BR /><I>string</I></TD><TD>The CIDR with which clients can match their IP to figure out the server address that they should use.</TD></TR>
<TR><TD><CODE>serverAddress</CODE><BR /><I>string</I></TD><TD>Address of this server, suitable for a client that matches the above CIDR. This can be a hostname, hostname:port, IP or IP:port.</TD></TR>
</TBODY>
</TABLE>
<H2 id="serviceaccounttokenprojection-v1-core">ServiceAccountTokenProjection v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceAccountTokenProjection</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ServiceAccountTokenProjection represents a projected service account token volume. This projection can be used to insert a service account token into the pods runtime filesystem for use against APIs (Kubernetes API Server or otherwise).</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeprojection-v1-core">VolumeProjection [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>audience</CODE><BR /><I>string</I></TD><TD>Audience is the intended audience of the token. A recipient of a token must identify itself with an identifier specified in the audience of the token, and otherwise should reject the token. The audience defaults to the identifier of the apiserver.</TD></TR>
<TR><TD><CODE>expirationSeconds</CODE><BR /><I>integer</I></TD><TD>ExpirationSeconds is the requested duration of validity of the service account token. As the token approaches expiration, the kubelet volume plugin will proactively rotate the service account token. The kubelet will start trying to rotate the token if the token is older than 80 percent of its time to live or if the token is older than 24 hours.Defaults to 1 hour and must be at least 10 minutes.</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is the path relative to the mount point of the file to project the token into.</TD></TR>
</TBODY>
</TABLE>
<H2 id="serviceport-v1-core">ServicePort v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServicePort</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ServicePort contains information on service&#39;s port.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#servicespec-v1-core">ServiceSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of this port within the service. This must be a DNS_LABEL. All ports within a ServiceSpec must have unique names. This maps to the &#39;Name&#39; field in EndpointPort objects. Optional if only one ServicePort is defined on this service.</TD></TR>
<TR><TD><CODE>nodePort</CODE><BR /><I>integer</I></TD><TD>The port on each node on which this service is exposed when type=NodePort or LoadBalancer. Usually assigned by the system. If specified, it will be allocated to the service if unused or else creation of the service will fail. Default is to auto-allocate a port if the ServiceType of this Service requires one. More info: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport</TD></TR>
<TR><TD><CODE>port</CODE><BR /><I>integer</I></TD><TD>The port that will be exposed by this service.</TD></TR>
<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>The IP protocol for this port. Supports &#34;TCP&#34; and &#34;UDP&#34;. Default is TCP.</TD></TR>
<TR><TD><CODE>targetPort</CODE></TD><TD>Number or name of the port to access on the pods targeted by the service. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME. If this is a string, it will be looked up as a named port in the target Pod&#39;s container ports. If this is not specified, the value of the &#39;port&#39; field is used (an identity map). This field is ignored for services with clusterIP=None, and should be omitted or set equal to the &#39;port&#39; field. More info: https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service</TD></TR>
</TBODY>
</TABLE>
<H2 id="servicereference-v1-apiregistration-k8s-io">ServiceReference v1 apiregistration.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>ServiceReference</CODE></TD></TR>
</TBODY>
</TABLE>
<P>ServiceReference holds a reference to Service.legacy.k8s.io</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#servicereference-v1beta1-admissionregistration-k8s-io">v1beta1</a>
<a href="#servicereference-v1beta1-apiregistration-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservicespec-v1-apiregistration-k8s-io">APIServiceSpec [apiregistration/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the service</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of the service</TD></TR>
</TBODY>
</TABLE>
<H2 id="sessionaffinityconfig-v1-core">SessionAffinityConfig v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SessionAffinityConfig</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SessionAffinityConfig represents the configurations of session affinity.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#servicespec-v1-core">ServiceSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>clientIP</CODE><BR /><I><a href="#clientipconfig-v1-core">ClientIPConfig</a></I></TD><TD>clientIP contains the configurations of Client IP based session affinity.</TD></TR>
</TBODY>
</TABLE>
<H2 id="statefulsetcondition-v1-apps">StatefulSetCondition v1 apps</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatefulSetCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<P>StatefulSetCondition describes the state of a statefulset at a certain point.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#statefulsetcondition-v1beta2-apps">v1beta2</a>
<a href="#statefulsetcondition-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetstatus-v1-apps">StatefulSetStatus [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of statefulset condition.</TD></TR>
</TBODY>
</TABLE>
<H2 id="statefulsetupdatestrategy-v1-apps">StatefulSetUpdateStrategy v1 apps</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatefulSetUpdateStrategy</CODE></TD></TR>
</TBODY>
</TABLE>
<P>StatefulSetUpdateStrategy indicates the strategy that the StatefulSet controller will use to perform updates. It includes any additional parameters necessary to perform the update for the indicated strategy.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#statefulsetupdatestrategy-v1beta2-apps">v1beta2</a>
<a href="#statefulsetupdatestrategy-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetspec-v1-apps">StatefulSetSpec [apps/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatestatefulsetstrategy-v1-apps">RollingUpdateStatefulSetStrategy</a></I></TD><TD>RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.</TD></TR>
</TBODY>
</TABLE>
<H2 id="status-v1-meta">Status v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Status</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Status is a return value for calls that don&#39;t return other objects.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#initializers-v1-meta">Initializers [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>code</CODE><BR /><I>integer</I></TD><TD>Suggested HTTP return code for this status, 0 if not set.</TD></TR>
<TR><TD><CODE>details</CODE><BR /><I><a href="#statusdetails-v1-meta">StatusDetails</a></I></TD><TD>Extended data associated with the reason. Each reason may define its own extended details. This field is optional and the data returned is not guaranteed to conform to any schema except that defined by the reason type.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human-readable description of the status of this operation.</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>A machine-readable description of why this operation is in the &#34;Failure&#34; status. If this value is empty there is no information available. A Reason clarifies an HTTP status code but does not override it.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the operation. One of: &#34;Success&#34; or &#34;Failure&#34;. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H2 id="statuscause-v1-meta">StatusCause v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatusCause</CODE></TD></TR>
</TBODY>
</TABLE>
<P>StatusCause provides more information about an api.Status failure, including cases when multiple errors are encountered.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statusdetails-v1-meta">StatusDetails [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>field</CODE><BR /><I>string</I></TD><TD>The field of the resource that has caused this error, as named by its JSON serialization. May include dot and postfix notation for nested attributes. Arrays are zero-indexed. Fields may appear more than once in an array of causes due to fields having multiple errors. Optional. Examples: &#34;name&#34; - the field &#34;name&#34; on the current resource &#34;items[0].name&#34; - the field &#34;name&#34; on the first array entry in &#34;items&#34;</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human-readable description of the cause of the error. This field may be presented as-is to a reader.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>A machine-readable description of the cause of the error. If this value is empty there is no information available.</TD></TR>
</TBODY>
</TABLE>
<H2 id="statusdetails-v1-meta">StatusDetails v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StatusDetails</CODE></TD></TR>
</TBODY>
</TABLE>
<P>StatusDetails is a set of additional properties that MAY be set by the server to provide additional information about a response. The Reason field of a Status object defines what attributes will be set. Clients must ignore fields that do not match the defined type of each attribute, and should assume that any attribute may be empty, invalid, or under defined.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#status-v1-meta">Status [meta/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>causes</CODE><BR /><I><a href="#statuscause-v1-meta">StatusCause</a> array</I></TD><TD>The Causes array includes more details associated with the StatusReason failure. Not all StatusReasons may provide detailed causes.</TD></TR>
<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>The group attribute of the resource associated with the status StatusReason.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>The kind attribute of the resource associated with the status StatusReason. On some operations may differ from the requested resource Kind. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name attribute of the resource associated with the status StatusReason (when there is a single name which can be described).</TD></TR>
<TR><TD><CODE>retryAfterSeconds</CODE><BR /><I>integer</I></TD><TD>If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID of the resource. (when there is a single resource which can be described). More info: http://kubernetes.io/docs/user-guide/identifiers#uids</TD></TR>
</TBODY>
</TABLE>
<H2 id="storageospersistentvolumesource-v1-core">StorageOSPersistentVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StorageOSPersistentVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a StorageOS persistent volume resource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>SecretRef specifies the secret to use for obtaining the StorageOS API credentials. If not specified, default values will be attempted.</TD></TR>
<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>VolumeName is the human-readable name of the StorageOS volume. Volume names are only unique within a namespace.</TD></TR>
<TR><TD><CODE>volumeNamespace</CODE><BR /><I>string</I></TD><TD>VolumeNamespace specifies the scope of the volume within StorageOS. If no namespace is specified then the Pod&#39;s namespace will be used. This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to &#34;default&#34; if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.</TD></TR>
</TBODY>
</TABLE>
<H2 id="storageosvolumesource-v1-core">StorageOSVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>StorageOSVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a StorageOS persistent volume resource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.</TD></TR>
<TR><TD><CODE>secretRef</CODE><BR /><I><a href="#localobjectreference-v1-core">LocalObjectReference</a></I></TD><TD>SecretRef specifies the secret to use for obtaining the StorageOS API credentials. If not specified, default values will be attempted.</TD></TR>
<TR><TD><CODE>volumeName</CODE><BR /><I>string</I></TD><TD>VolumeName is the human-readable name of the StorageOS volume. Volume names are only unique within a namespace.</TD></TR>
<TR><TD><CODE>volumeNamespace</CODE><BR /><I>string</I></TD><TD>VolumeNamespace specifies the scope of the volume within StorageOS. If no namespace is specified then the Pod&#39;s namespace will be used. This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to &#34;default&#34; if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.</TD></TR>
</TBODY>
</TABLE>
<H2 id="subject-v1-rbac-authorization-k8s-io">Subject v1 rbac.authorization.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Subject</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Subject contains a reference to the object or user identities a role binding applies to. This can either hold a direct API object reference, or a value for non-objects such as user and group names.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#subject-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
<a href="#subject-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1]</a></LI>
<LI><a href="#rolebinding-v1-rbac-authorization-k8s-io">RoleBinding [rbac/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup holds the API group of the referenced subject. Defaults to &#34;&#34; for ServiceAccount subjects. Defaults to &#34;rbac.authorization.k8s.io&#34; for User and Group subjects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of object being referenced. Values defined by this API group are &#34;User&#34;, &#34;Group&#34;, and &#34;ServiceAccount&#34;. If the Authorizer does not recognized the kind value, the Authorizer should report an error.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the object being referenced.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace of the referenced object. If the object kind is non-namespace, such as &#34;User&#34; or &#34;Group&#34;, and this value is not empty the Authorizer should report an error.</TD></TR>
</TBODY>
</TABLE>
<H2 id="subjectrulesreviewstatus-v1-authorization-k8s-io">SubjectRulesReviewStatus v1 authorization.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>SubjectRulesReviewStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SubjectRulesReviewStatus contains the result of a rules check. This check can be incomplete depending on the set of authorizers the server is configured with and any errors experienced during evaluation. Because authorization rules are additive, if a rule appears in a list it&#39;s safe to assume the subject has that permission, even if that list is incomplete.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#subjectrulesreviewstatus-v1beta1-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectrulesreview-v1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>evaluationError</CODE><BR /><I>string</I></TD><TD>EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn&#39;t support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.</TD></TR>
<TR><TD><CODE>incomplete</CODE><BR /><I>boolean</I></TD><TD>Incomplete is true when the rules returned by this call are incomplete. This is most commonly encountered when an authorizer, such as an external authorizer, doesn&#39;t support rules evaluation.</TD></TR>
<TR><TD><CODE>nonResourceRules</CODE><BR /><I><a href="#nonresourcerule-v1-authorization-k8s-io">NonResourceRule</a> array</I></TD><TD>NonResourceRules is the list of actions the subject is allowed to perform on non-resources. The list ordering isn&#39;t significant, may contain duplicates, and possibly be incomplete.</TD></TR>
<TR><TD><CODE>resourceRules</CODE><BR /><I><a href="#resourcerule-v1-authorization-k8s-io">ResourceRule</a> array</I></TD><TD>ResourceRules is the list of actions the subject is allowed to perform on resources. The list ordering isn&#39;t significant, may contain duplicates, and possibly be incomplete.</TD></TR>
</TBODY>
</TABLE>
<H2 id="supplementalgroupsstrategyoptions-v1beta1-extensions">SupplementalGroupsStrategyOptions v1beta1 extensions</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SupplementalGroupsStrategyOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<P>SupplementalGroupsStrategyOptions defines the strategy type and options used to create the strategy. Deprecated: use SupplementalGroupsStrategyOptions from policy API Group instead.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-extensions">PodSecurityPolicySpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-extensions">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of supplemental groups. If you would like to force a single supplemental group then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate what supplemental groups is used in the SecurityContext.</TD></TR>
</TBODY>
</TABLE>
<H2 id="sysctl-v1-core">Sysctl v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Sysctl</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Sysctl defines a kernel parameter to be set</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritycontext-v1-core">PodSecurityContext [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of a property to set</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>Value of a property to set</TD></TR>
</TBODY>
</TABLE>
<H2 id="tcpsocketaction-v1-core">TCPSocketAction v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TCPSocketAction</CODE></TD></TR>
</TBODY>
</TABLE>
<P>TCPSocketAction describes an action based on opening a socket</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#handler-v1-core">Handler [core/v1]</a></LI>
<LI><a href="#probe-v1-core">Probe [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>host</CODE><BR /><I>string</I></TD><TD>Optional: Host name to connect to, defaults to the pod IP.</TD></TR>
<TR><TD><CODE>port</CODE></TD><TD>Number or name of the port to access on the container. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.</TD></TR>
</TBODY>
</TABLE>
<H2 id="taint-v1-core">Taint v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Taint</CODE></TD></TR>
</TBODY>
</TABLE>
<P>The node this Taint is attached to has the &#34;effect&#34; on any pod that does not tolerate the Taint.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#nodespec-v1-core">NodeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>effect</CODE><BR /><I>string</I></TD><TD>Required. The effect of the taint on pods that do not tolerate the taint. Valid effects are NoSchedule, PreferNoSchedule and NoExecute.</TD></TR>
<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>Required. The taint key to be applied to a node.</TD></TR>
<TR><TD><CODE>timeAdded</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>TimeAdded represents the time at which the taint was added. It is only written for NoExecute taints.</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>Required. The taint value corresponding to the taint key.</TD></TR>
</TBODY>
</TABLE>
<H2 id="time-v1-meta">Time v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Time</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON. Wrappers are provided for many of the factory methods that the time package offers.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservicecondition-v1-apiregistration-k8s-io">APIServiceCondition [apiregistration/v1]</a></LI>
<LI><a href="#apiservicecondition-v1beta1-apiregistration-k8s-io">APIServiceCondition [apiregistration/v1beta1]</a></LI>
<LI><a href="#certificatesigningrequestcondition-v1beta1-certificates-k8s-io">CertificateSigningRequestCondition [certificates/v1beta1]</a></LI>
<LI><a href="#containerstaterunning-v1-core">ContainerStateRunning [core/v1]</a></LI>
<LI><a href="#containerstateterminated-v1-core">ContainerStateTerminated [core/v1]</a></LI>
<LI><a href="#cronjobstatus-v1beta1-batch">CronJobStatus [batch/v1beta1]</a></LI>
<LI><a href="#cronjobstatus-v2alpha1-batch">CronJobStatus [batch/v2alpha1]</a></LI>
<LI><a href="#customresourcedefinitioncondition-v1beta1-apiextensions-k8s-io">CustomResourceDefinitionCondition [apiextensions/v1beta1]</a></LI>
<LI><a href="#daemonsetcondition-v1-apps">DaemonSetCondition [apps/v1]</a></LI>
<LI><a href="#daemonsetcondition-v1beta2-apps">DaemonSetCondition [apps/v1beta2]</a></LI>
<LI><a href="#daemonsetcondition-v1beta1-extensions">DaemonSetCondition [extensions/v1beta1]</a></LI>
<LI><a href="#deploymentcondition-v1-apps">DeploymentCondition [apps/v1]</a></LI>
<LI><a href="#deploymentcondition-v1beta2-apps">DeploymentCondition [apps/v1beta2]</a></LI>
<LI><a href="#deploymentcondition-v1beta1-apps">DeploymentCondition [apps/v1beta1]</a></LI>
<LI><a href="#deploymentcondition-v1beta1-extensions">DeploymentCondition [extensions/v1beta1]</a></LI>
<LI><a href="#event-v1-core">Event [core/v1]</a></LI>
<LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
<LI><a href="#horizontalpodautoscalercondition-v2beta1-autoscaling">HorizontalPodAutoscalerCondition [autoscaling/v2beta1]</a></LI>
<LI><a href="#horizontalpodautoscalerstatus-v1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v1]</a></LI>
<LI><a href="#horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus [autoscaling/v2beta1]</a></LI>
<LI><a href="#jobcondition-v1-batch">JobCondition [batch/v1]</a></LI>
<LI><a href="#jobstatus-v1-batch">JobStatus [batch/v1]</a></LI>
<LI><a href="#nodecondition-v1-core">NodeCondition [core/v1]</a></LI>
<LI><a href="#objectmeta-v1-meta">ObjectMeta [meta/v1]</a></LI>
<LI><a href="#persistentvolumeclaimcondition-v1-core">PersistentVolumeClaimCondition [core/v1]</a></LI>
<LI><a href="#podcondition-v1-core">PodCondition [core/v1]</a></LI>
<LI><a href="#podstatus-v1-core">PodStatus [core/v1]</a></LI>
<LI><a href="#replicasetcondition-v1-apps">ReplicaSetCondition [apps/v1]</a></LI>
<LI><a href="#replicasetcondition-v1beta2-apps">ReplicaSetCondition [apps/v1beta2]</a></LI>
<LI><a href="#replicasetcondition-v1beta1-extensions">ReplicaSetCondition [extensions/v1beta1]</a></LI>
<LI><a href="#replicationcontrollercondition-v1-core">ReplicationControllerCondition [core/v1]</a></LI>
<LI><a href="#statefulsetcondition-v1-apps">StatefulSetCondition [apps/v1]</a></LI>
<LI><a href="#statefulsetcondition-v1beta2-apps">StatefulSetCondition [apps/v1beta2]</a></LI>
<LI><a href="#statefulsetcondition-v1beta1-apps">StatefulSetCondition [apps/v1beta1]</a></LI>
<LI><a href="#taint-v1-core">Taint [core/v1]</a></LI>
<LI><a href="#volumeerror-v1beta1-storage-k8s-io">VolumeError [storage/v1beta1]</a></LI>
<LI><a href="#volumeerror-v1alpha1-storage-k8s-io">VolumeError [storage/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
</TBODY>
</TABLE>
<H2 id="toleration-v1-core">Toleration v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>Toleration</CODE></TD></TR>
</TBODY>
</TABLE>
<P>The pod this Toleration is attached to tolerates any taint that matches the triple &lt;key,value,effect&gt; using the matching operator &lt;operator&gt;.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podspec-v1-core">PodSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>effect</CODE><BR /><I>string</I></TD><TD>Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.</TD></TR>
<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>Key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.</TD></TR>
<TR><TD><CODE>operator</CODE><BR /><I>string</I></TD><TD>Operator represents a key&#39;s relationship to the value. Valid operators are Exists and Equal. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category.</TD></TR>
<TR><TD><CODE>tolerationSeconds</CODE><BR /><I>integer</I></TD><TD>TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>string</I></TD><TD>Value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.</TD></TR>
</TBODY>
</TABLE>
<H2 id="topologyselectorlabelrequirement-v1-core">TopologySelectorLabelRequirement v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TopologySelectorLabelRequirement</CODE></TD></TR>
</TBODY>
</TABLE>
<P>A topology selector requirement is a selector that matches given label. This is an alpha feature and may change in the future.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#topologyselectorterm-v1-core">TopologySelectorTerm [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>key</CODE><BR /><I>string</I></TD><TD>The label key that the selector applies to.</TD></TR>
<TR><TD><CODE>values</CODE><BR /><I>string array</I></TD><TD>An array of string values. One value must match the label to be selected. Each entry in Values is ORed.</TD></TR>
</TBODY>
</TABLE>
<H2 id="topologyselectorterm-v1-core">TopologySelectorTerm v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>TopologySelectorTerm</CODE></TD></TR>
</TBODY>
</TABLE>
<P>A topology selector term represents the result of label queries. A null or empty topology selector term matches no objects. The requirements of them are ANDed. It provides a subset of functionality as NodeSelectorTerm. This is an alpha feature and may change in the future.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageclass-v1-storage-k8s-io">StorageClass [storage/v1]</a></LI>
<LI><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass [storage/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>matchLabelExpressions</CODE><BR /><I><a href="#topologyselectorlabelrequirement-v1-core">TopologySelectorLabelRequirement</a> array</I></TD><TD>A list of topology selector requirements by labels.</TD></TR>
</TBODY>
</TABLE>
<H2 id="userinfo-v1-authentication-k8s-io">UserInfo v1 authentication.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>UserInfo</CODE></TD></TR>
</TBODY>
</TABLE>
<P>UserInfo holds the information about the user needed to implement the user.Info interface.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#userinfo-v1beta1-authentication-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#tokenreviewstatus-v1-authentication-k8s-io">TokenReviewStatus [authentication/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extra</CODE><BR /><I>object</I></TD><TD>Any additional information provided by the authenticator.</TD></TR>
<TR><TD><CODE>groups</CODE><BR /><I>string array</I></TD><TD>The names of groups this user is a part of.</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs.</TD></TR>
<TR><TD><CODE>username</CODE><BR /><I>string</I></TD><TD>The name that uniquely identifies this user among all active users.</TD></TR>
</TBODY>
</TABLE>
<H2 id="volumeattachmentsource-v1beta1-storage-k8s-io">VolumeAttachmentSource v1beta1 storage.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>VolumeAttachmentSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>VolumeAttachmentSource represents a volume that should be attached. Right now only PersistenVolumes can be attached via external attacher, in future we may allow also inline volumes in pods. Exactly one member can be set.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#volumeattachmentsource-v1alpha1-storage-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachmentspec-v1beta1-storage-k8s-io">VolumeAttachmentSpec [storage/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>persistentVolumeName</CODE><BR /><I>string</I></TD><TD>Name of the persistent volume to attach.</TD></TR>
</TBODY>
</TABLE>
<H2 id="volumedevice-v1-core">VolumeDevice v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeDevice</CODE></TD></TR>
</TBODY>
</TABLE>
<P>volumeDevice describes a mapping of a raw block device within a container.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#container-v1-core">Container [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>devicePath</CODE><BR /><I>string</I></TD><TD>devicePath is the path inside of the container that the device will be mapped to.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>name must match the name of a persistentVolumeClaim in the pod</TD></TR>
</TBODY>
</TABLE>
<H2 id="volumeerror-v1beta1-storage-k8s-io">VolumeError v1beta1 storage.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>VolumeError</CODE></TD></TR>
</TBODY>
</TABLE>
<P>VolumeError captures an error encountered during a volume operation.</P>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#volumeerror-v1alpha1-storage-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachmentstatus-v1beta1-storage-k8s-io">VolumeAttachmentStatus [storage/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>String detailing the error encountered during Attach or Detach operation. This string maybe logged, so it should not contain sensitive information.</TD></TR>
<TR><TD><CODE>time</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time the error was encountered.</TD></TR>
</TBODY>
</TABLE>
<H2 id="volumemount-v1-core">VolumeMount v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeMount</CODE></TD></TR>
</TBODY>
</TABLE>
<P>VolumeMount describes a mounting of a Volume within a container.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#container-v1-core">Container [core/v1]</a></LI>
<LI><a href="#podpresetspec-v1alpha1-settings-k8s-io">PodPresetSpec [settings/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>mountPath</CODE><BR /><I>string</I></TD><TD>Path within the container at which the volume should be mounted. Must not contain &#39;:&#39;.</TD></TR>
<TR><TD><CODE>mountPropagation</CODE><BR /><I>string</I></TD><TD>mountPropagation determines how mounts are propagated from the host to container and the other way around. When not set, MountPropagationHostToContainer is used. This field is beta in 1.10.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>This must match the Name of a Volume.</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>Mounted read-only if true, read-write otherwise (false or unspecified). Defaults to false.</TD></TR>
<TR><TD><CODE>subPath</CODE><BR /><I>string</I></TD><TD>Path within the volume from which the container&#39;s volume should be mounted. Defaults to &#34;&#34; (volume&#39;s root).</TD></TR>
</TBODY>
</TABLE>
<H2 id="volumenodeaffinity-v1-core">VolumeNodeAffinity v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeNodeAffinity</CODE></TD></TR>
</TBODY>
</TABLE>
<P>VolumeNodeAffinity defines constraints that limit what nodes this volume can be accessed from.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>required</CODE><BR /><I><a href="#nodeselector-v1-core">NodeSelector</a></I></TD><TD>Required specifies hard node constraints that must be met.</TD></TR>
</TBODY>
</TABLE>
<H2 id="volumeprojection-v1-core">VolumeProjection v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VolumeProjection</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Projection that may be projected along with other supported volume types</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#projectedvolumesource-v1-core">ProjectedVolumeSource [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>configMap</CODE><BR /><I><a href="#configmapprojection-v1-core">ConfigMapProjection</a></I></TD><TD>information about the configMap data to project</TD></TR>
<TR><TD><CODE>downwardAPI</CODE><BR /><I><a href="#downwardapiprojection-v1-core">DownwardAPIProjection</a></I></TD><TD>information about the downwardAPI data to project</TD></TR>
<TR><TD><CODE>secret</CODE><BR /><I><a href="#secretprojection-v1-core">SecretProjection</a></I></TD><TD>information about the secret data to project</TD></TR>
<TR><TD><CODE>serviceAccountToken</CODE><BR /><I><a href="#serviceaccounttokenprojection-v1-core">ServiceAccountTokenProjection</a></I></TD><TD>information about the serviceAccountToken data to project</TD></TR>
</TBODY>
</TABLE>
<H2 id="vspherevirtualdiskvolumesource-v1-core">VsphereVirtualDiskVolumeSource v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>VsphereVirtualDiskVolumeSource</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Represents a vSphere volume resource.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#persistentvolumespec-v1-core">PersistentVolumeSpec [core/v1]</a></LI>
<LI><a href="#volume-v1-core">Volume [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>fsType</CODE><BR /><I>string</I></TD><TD>Filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. &#34;ext4&#34;, &#34;xfs&#34;, &#34;ntfs&#34;. Implicitly inferred to be &#34;ext4&#34; if unspecified.</TD></TR>
<TR><TD><CODE>storagePolicyID</CODE><BR /><I>string</I></TD><TD>Storage Policy Based Management (SPBM) profile ID associated with the StoragePolicyName.</TD></TR>
<TR><TD><CODE>storagePolicyName</CODE><BR /><I>string</I></TD><TD>Storage Policy Based Management (SPBM) profile name.</TD></TR>
<TR><TD><CODE>volumePath</CODE><BR /><I>string</I></TD><TD>Path that identifies vSphere volume vmdk</TD></TR>
</TBODY>
</TABLE>
<H2 id="watchevent-v1-meta">WatchEvent v1 meta</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>meta</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>WatchEvent</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Event represents a single event to a watched resource.</P>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>object</CODE></TD><TD>Object is: * If Type is Added or Modified: the new state of the object. * If Type is Deleted: the state of the object immediately before deletion. * If Type is Error: *Status is recommended; other types may make sense depending on context.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="webhook-v1beta1-admissionregistration-k8s-io">Webhook v1beta1 admissionregistration.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Webhook</CODE></TD></TR>
</TBODY>
</TABLE>
<P>Webhook describes an admission webhook and the resources and operations it applies to.</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#mutatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">MutatingWebhookConfiguration [admissionregistration/v1beta1]</a></LI>
<LI><a href="#validatingwebhookconfiguration-v1beta1-admissionregistration-k8s-io">ValidatingWebhookConfiguration [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>clientConfig</CODE><BR /><I><a href="#webhookclientconfig-v1beta1-admissionregistration-k8s-io">WebhookClientConfig</a></I></TD><TD>ClientConfig defines how to communicate with the hook. Required</TD></TR>
<TR><TD><CODE>failurePolicy</CODE><BR /><I>string</I></TD><TD>FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. Defaults to Ignore.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>The name of the admission webhook. Name should be fully qualified, e.g., imagepolicy.kubernetes.io, where &#34;imagepolicy&#34; is the name of the webhook, and kubernetes.io is the name of the organization. Required.</TD></TR>
<TR><TD><CODE>namespaceSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>NamespaceSelector decides whether to run the webhook on an object based on whether the namespace for that object matches the selector. If the object itself is a namespace, the matching is performed on object.metadata.labels. If the object is another cluster scoped resource, it never skips the webhook. For example, to run the webhook on any objects whose namespace is not associated with &#34;runlevel&#34; of &#34;0&#34; or &#34;1&#34;; you will set the selector as follows: &#34;namespaceSelector&#34;: { &#34;matchExpressions&#34;: [ { &#34;key&#34;: &#34;runlevel&#34;, &#34;operator&#34;: &#34;NotIn&#34;, &#34;values&#34;: [ &#34;0&#34;, &#34;1&#34; ] } ] } If instead you want to only run the webhook on any objects whose namespace is associated with the &#34;environment&#34; of &#34;prod&#34; or &#34;staging&#34;; you will set the selector as follows: &#34;namespaceSelector&#34;: { &#34;matchExpressions&#34;: [ { &#34;key&#34;: &#34;environment&#34;, &#34;operator&#34;: &#34;In&#34;, &#34;values&#34;: [ &#34;prod&#34;, &#34;staging&#34; ] } ] } See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more examples of label selectors. Default to the empty LabelSelector, which matches everything.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#rulewithoperations-v1beta1-admissionregistration-k8s-io">RuleWithOperations</a> array</I></TD><TD>Rules describes what operations on what resources/subresources the webhook cares about. The webhook cares about an operation if it matches _any_ Rule. However, in order to prevent ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks from putting the cluster in a state which cannot be recovered from without completely disabling the plugin, ValidatingAdmissionWebhooks and MutatingAdmissionWebhooks are never called on admission requests for ValidatingWebhookConfiguration and MutatingWebhookConfiguration objects.</TD></TR>
</TBODY>
</TABLE>
<H2 id="webhookclientconfig-v1beta1-admissionregistration-k8s-io">WebhookClientConfig v1beta1 admissionregistration.k8s.io</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>WebhookClientConfig</CODE></TD></TR>
</TBODY>
</TABLE>
<P>WebhookClientConfig contains the information to make a TLS connection with the webhook</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#webhook-v1beta1-admissionregistration-k8s-io">Webhook [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>caBundle</CODE><BR /><I>string</I></TD><TD>`caBundle` is a PEM encoded CA bundle which will be used to validate the webhook&#39;s server certificate. Required.</TD></TR>
<TR><TD><CODE>service</CODE><BR /><I><a href="#servicereference-v1beta1-admissionregistration-k8s-io">ServiceReference</a></I></TD><TD>`service` is a reference to the service for this webhook. Either `service` or `url` must be specified. If the webhook is running within the cluster, then you should use `service`. Port 443 will be used if it is open, otherwise it is an error.</TD></TR>
<TR><TD><CODE>url</CODE><BR /><I>string</I></TD><TD>`url` gives the location of the webhook, in standard URL form (`[scheme://]host:port/path`). Exactly one of `url` or `service` must be specified. The `host` should not refer to a service running in the cluster; use the `service` field instead. The host might be resolved via external DNS in some apiservers (e.g., `kube-apiserver` cannot resolve in-cluster DNS as that would be a layering violation). `host` may also be an IP address. Please note that using `localhost` or `127.0.0.1` as a `host` is risky unless you take great care to run this webhook on all hosts which run an apiserver which might need to make calls to this webhook. Such installs are likely to be non-portable, i.e., not easy to turn up in a new cluster. The scheme must be &#34;https&#34;; the URL must begin with &#34;https://&#34;. A path is optional, and if present may be any string permissible in a URL. You may use the path to pass an arbitrary string to the webhook, for example, a cluster identifier. Attempting to use a user or basic auth e.g. &#34;user:password@&#34; is not allowed. Fragments (&#34;#...&#34;) and query parameters (&#34;?...&#34;) are not allowed, either.</TD></TR>
</TBODY>
</TABLE>
<H2 id="weightedpodaffinityterm-v1-core">WeightedPodAffinityTerm v1 core</H2>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>core</CODE></TD><TD><CODE>v1</CODE></TD><TD><CODE>WeightedPodAffinityTerm</CODE></TD></TR>
</TBODY>
</TABLE>
<P>The weights of all of the matched WeightedPodAffinityTerm fields are added per-node to find the most preferred node(s)</P>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podaffinity-v1-core">PodAffinity [core/v1]</a></LI>
<LI><a href="#podantiaffinity-v1-core">PodAntiAffinity [core/v1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>podAffinityTerm</CODE><BR /><I><a href="#podaffinityterm-v1-core">PodAffinityTerm</a></I></TD><TD>Required. A pod affinity term, associated with the corresponding weight.</TD></TR>
<TR><TD><CODE>weight</CODE><BR /><I>integer</I></TD><TD>weight associated with matching the corresponding podAffinityTerm, in the range 1-100.</TD></TR>
</TBODY>
</TABLE>
<H1 id="-strong-old-api-versions-strong-"><STRONG>OLD API VERSIONS</STRONG></H1>
<P>This section contains older versions of resources shown above.</P>
<H1 id="apiservice-v1beta1-apiregistration-k8s-io">APIService v1beta1 apiregistration.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>APIService</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#apiservice-v1-apiregistration-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservicelist-v1beta1-apiregistration-k8s-io">APIServiceList [apiregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#apiservicespec-v1beta1-apiregistration-k8s-io">APIServiceSpec</a></I></TD><TD>Spec contains information for locating and communicating with a server</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#apiservicestatus-v1beta1-apiregistration-k8s-io">APIServiceStatus</a></I></TD><TD>Status contains derived information about an API server</TD></TR>
</TBODY>
</TABLE>
<H3 id="apiservicespec-v1beta1-apiregistration-k8s-io">APIServiceSpec v1beta1 apiregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService [apiregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>caBundle</CODE><BR /><I>string</I></TD><TD>CABundle is a PEM encoded CA bundle which will be used to validate an API server&#39;s serving certificate.</TD></TR>
<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>Group is the API group name this server hosts</TD></TR>
<TR><TD><CODE>groupPriorityMinimum</CODE><BR /><I>integer</I></TD><TD>GroupPriorityMininum is the priority this group should have at least. Higher priority means that the group is preferred by clients over lower priority ones. Note that other versions of this group might specify even higher GroupPriorityMininum values such that the whole group gets a higher priority. The primary sort is based on GroupPriorityMinimum, ordered highest number to lowest (20 before 10). The secondary sort is based on the alphabetical comparison of the name of the object. (v1.bar before v1.foo) We&#39;d recommend something like: *.k8s.io (except extensions) at 18000 and PaaSes (OpenShift, Deis) are recommended to be in the 2000s</TD></TR>
<TR><TD><CODE>insecureSkipTLSVerify</CODE><BR /><I>boolean</I></TD><TD>InsecureSkipTLSVerify disables TLS certificate verification when communicating with this server. This is strongly discouraged. You should use the CABundle instead.</TD></TR>
<TR><TD><CODE>service</CODE><BR /><I><a href="#servicereference-v1beta1-apiregistration-k8s-io">ServiceReference</a></I></TD><TD>Service is a reference to the service for this API server. It must communicate on port 443 If the Service is nil, that means the handling for the API groupversion is handled locally on this server. The call will simply delegate to the normal handler chain to be fulfilled.</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>Version is the API version this server hosts. For example, &#34;v1&#34;</TD></TR>
<TR><TD><CODE>versionPriority</CODE><BR /><I>integer</I></TD><TD>VersionPriority controls the ordering of this API version inside of its group. Must be greater than zero. The primary sort is based on VersionPriority, ordered highest to lowest (20 before 10). Since it&#39;s inside of a group, the number can be small, probably in the 10s. In case of equal version priorities, the version string will be used to compute the order inside a group. If the version string is &#34;kube-like&#34;, it will sort above non &#34;kube-like&#34; version strings, which are ordered lexicographically. &#34;Kube-like&#34; versions start with a &#34;v&#34;, then are followed by a number (the major version), then optionally the string &#34;alpha&#34; or &#34;beta&#34; and another number (the minor version). These are sorted first by GA &gt; beta &gt; alpha (where GA is a version with no suffix such as beta or alpha), and then by comparing major version, then minor version. An example sorted list of versions: v10, v2, v1, v11beta2, v10beta3, v3beta1, v12alpha1, v11alpha2, foo1, foo10.</TD></TR>
</TBODY>
</TABLE>
<H3 id="apiservicestatus-v1beta1-apiregistration-k8s-io">APIServiceStatus v1beta1 apiregistration</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService [apiregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#apiservicecondition-v1beta1-apiregistration-k8s-io">APIServiceCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Current service state of apiService.</TD></TR>
</TBODY>
</TABLE>
<H3 id="apiservicelist-v1beta1-apiregistration-k8s-io">APIServiceList v1beta1 apiregistration</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-apiservice-v1beta1-apiregistration-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-apiservice-v1beta1-apiregistration-k8s-io">Create</H2>
<P>create an APIService</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apiregistration.k8s.io/v1beta1/apiservices</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-apiservice-v1beta1-apiregistration-k8s-io">Patch</H2>
<P>partially update the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-apiservice-v1beta1-apiregistration-k8s-io">Replace</H2>
<P>replace the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-apiservice-v1beta1-apiregistration-k8s-io">Delete</H2>
<P>delete an APIService</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-apiservice-v1beta1-apiregistration-k8s-io">Delete Collection</H2>
<P>delete collection of APIService</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apiregistration.k8s.io/v1beta1/apiservices</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-apiservice-v1beta1-apiregistration-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-apiservice-v1beta1-apiregistration-k8s-io">Read</H2>
<P>read the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-apiservice-v1beta1-apiregistration-k8s-io">List</H2>
<P>list or watch objects of kind APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1beta1/apiservices</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservicelist-v1beta1-apiregistration-k8s-io">APIServiceList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-apiservice-v1beta1-apiregistration-k8s-io">Watch</H2>
<P>watch changes to an object of kind APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1beta1/watch/apiservices/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-apiservice-v1beta1-apiregistration-k8s-io">Watch List</H2>
<P>watch individual changes to a list of APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1beta1/watch/apiservices</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-apiservice-v1beta1-apiregistration-k8s-io-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-apiservice-v1beta1-apiregistration-k8s-io">Patch Status</H2>
<P>partially update status of the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-apiservice-v1beta1-apiregistration-k8s-io">Read Status</H2>
<P>read status of the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-apiservice-v1beta1-apiregistration-k8s-io">Replace Status</H2>
<P>replace status of the specified APIService</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apiregistration.k8s.io/v1beta1/apiservices/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the APIService</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#apiservice-v1beta1-apiregistration-k8s-io">APIService</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="apiservicecondition-v1beta1-apiregistration-k8s-io">APIServiceCondition v1beta1 apiregistration.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>APIServiceCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#apiservicecondition-v1-apiregistration-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservicestatus-v1beta1-apiregistration-k8s-io">APIServiceStatus [apiregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>Human-readable message indicating details about last transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Unique, one-word, CamelCase reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status is the status of the condition. Can be True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type is the type of the condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="aggregationrule-v1beta1-rbac-authorization-k8s-io">AggregationRule v1beta1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AggregationRule</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#aggregationrule-v1-rbac-authorization-k8s-io">v1</a>
<a href="#aggregationrule-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole [rbac/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>clusterRoleSelectors</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a> array</I></TD><TD>ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole&#39;s permissions will be added</TD></TR>
</TBODY>
</TABLE>
<H1 id="aggregationrule-v1alpha1-rbac-authorization-k8s-io">AggregationRule v1alpha1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>AggregationRule</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#aggregationrule-v1-rbac-authorization-k8s-io">v1</a>
<a href="#aggregationrule-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole [rbac/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>clusterRoleSelectors</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a> array</I></TD><TD>ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole&#39;s permissions will be added</TD></TR>
</TBODY>
</TABLE>
<H1 id="allowedflexvolume-v1beta1-policy">AllowedFlexVolume v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AllowedFlexVolume</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>driver</CODE><BR /><I>string</I></TD><TD>driver is the name of the Flexvolume driver.</TD></TR>
</TBODY>
</TABLE>
<H1 id="allowedhostpath-v1beta1-policy">AllowedHostPath v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>AllowedHostPath</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pathPrefix</CODE><BR /><I>string</I></TD><TD>pathPrefix is the path prefix that the host volume must match. It does not support `*`. Trailing slashes are trimmed when validating the path prefix with a host path. Examples: `/foo` would allow `/foo`, `/foo/` and `/foo/bar` `/foo` would not allow `/food` or `/etc/foo`</TD></TR>
<TR><TD><CODE>readOnly</CODE><BR /><I>boolean</I></TD><TD>when set to true, will allow host volumes matching the pathPrefix only if all volume mounts are readOnly.</TD></TR>
</TBODY>
</TABLE>
<H1 id="clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole v1beta1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ClusterRole</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#clusterrole-v1-rbac-authorization-k8s-io">v1</a>
<a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolelist-v1beta1-rbac-authorization-k8s-io">ClusterRoleList [rbac/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>aggregationRule</CODE><BR /><I><a href="#aggregationrule-v1beta1-rbac-authorization-k8s-io">AggregationRule</a></I></TD><TD>AggregationRule is an optional field that describes how to build the Rules for this ClusterRole. If AggregationRule is set, then the Rules are controller managed and direct changes to Rules will be stomped by the controller.</TD></TR>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyrule-v1beta1-rbac-authorization-k8s-io">PolicyRule</a> array</I></TD><TD>Rules holds all the PolicyRules for this ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3 id="clusterrolelist-v1beta1-rbac-authorization-k8s-io">ClusterRoleList v1beta1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a> array</I></TD><TD>Items is a list of ClusterRoles</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-clusterrole-v1beta1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-clusterrole-v1beta1-rbac-authorization-k8s-io">Create</H2>
<P>create a ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1beta1/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-clusterrole-v1beta1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1beta1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-clusterrole-v1beta1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1beta1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-clusterrole-v1beta1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1beta1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-clusterrole-v1beta1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1beta1/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-clusterrole-v1beta1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-clusterrole-v1beta1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-clusterrole-v1beta1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolelist-v1beta1-rbac-authorization-k8s-io">ClusterRoleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-clusterrole-v1beta1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-clusterrole-v1beta1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole v1alpha1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>ClusterRole</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#clusterrole-v1-rbac-authorization-k8s-io">v1</a>
<a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolelist-v1alpha1-rbac-authorization-k8s-io">ClusterRoleList [rbac/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>aggregationRule</CODE><BR /><I><a href="#aggregationrule-v1alpha1-rbac-authorization-k8s-io">AggregationRule</a></I></TD><TD>AggregationRule is an optional field that describes how to build the Rules for this ClusterRole. If AggregationRule is set, then the Rules are controller managed and direct changes to Rules will be stomped by the controller.</TD></TR>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyrule-v1alpha1-rbac-authorization-k8s-io">PolicyRule</a> array</I></TD><TD>Rules holds all the PolicyRules for this ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3 id="clusterrolelist-v1alpha1-rbac-authorization-k8s-io">ClusterRoleList v1alpha1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a> array</I></TD><TD>Items is a list of ClusterRoles</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-clusterrole-v1alpha1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-clusterrole-v1alpha1-rbac-authorization-k8s-io">Create</H2>
<P>create a ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-clusterrole-v1alpha1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-clusterrole-v1alpha1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-clusterrole-v1alpha1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-clusterrole-v1alpha1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-clusterrole-v1alpha1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-clusterrole-v1alpha1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-clusterrole-v1alpha1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolelist-v1alpha1-rbac-authorization-k8s-io">ClusterRoleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-clusterrole-v1alpha1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterroles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRole</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-clusterrole-v1alpha1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of ClusterRole</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterroles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding v1beta1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ClusterRoleBinding</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">v1</a>
<a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolebindinglist-v1beta1-rbac-authorization-k8s-io">ClusterRoleBindingList [rbac/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>roleRef</CODE><BR /><I><a href="#roleref-v1beta1-rbac-authorization-k8s-io">RoleRef</a></I></TD><TD>RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.</TD></TR>
<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1beta1-rbac-authorization-k8s-io">Subject</a> array</I></TD><TD>Subjects holds references to the objects the role applies to.</TD></TR>
</TBODY>
</TABLE>
<H3 id="clusterrolebindinglist-v1beta1-rbac-authorization-k8s-io">ClusterRoleBindingList v1beta1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a> array</I></TD><TD>Items is a list of ClusterRoleBindings</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-clusterrolebinding-v1beta1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-clusterrolebinding-v1beta1-rbac-authorization-k8s-io">Create</H2>
<P>create a ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-clusterrolebinding-v1beta1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-clusterrolebinding-v1beta1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-clusterrolebinding-v1beta1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-clusterrolebinding-v1beta1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-clusterrolebinding-v1beta1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-clusterrolebinding-v1beta1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-clusterrolebinding-v1beta1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebindinglist-v1beta1-rbac-authorization-k8s-io">ClusterRoleBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-clusterrolebinding-v1beta1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-clusterrolebinding-v1beta1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding v1alpha1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>ClusterRoleBinding</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#clusterrolebinding-v1-rbac-authorization-k8s-io">v1</a>
<a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolebindinglist-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBindingList [rbac/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>roleRef</CODE><BR /><I><a href="#roleref-v1alpha1-rbac-authorization-k8s-io">RoleRef</a></I></TD><TD>RoleRef can only reference a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.</TD></TR>
<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1alpha1-rbac-authorization-k8s-io">Subject</a> array</I></TD><TD>Subjects holds references to the objects the role applies to.</TD></TR>
</TBODY>
</TABLE>
<H3 id="clusterrolebindinglist-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBindingList v1alpha1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a> array</I></TD><TD>Items is a list of ClusterRoleBindings</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">Create</H2>
<P>create a ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#clusterrolebindinglist-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterrolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ClusterRoleBinding</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of ClusterRoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/clusterrolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="controllerrevision-v1beta2-apps">ControllerRevision v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>ControllerRevision</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#controllerrevision-v1-apps">v1</a>
<a href="#controllerrevision-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#controllerrevisionlist-v1beta2-apps">ControllerRevisionList [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>data</CODE></TD><TD>Data is the serialized representation of the state.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>revision</CODE><BR /><I>integer</I></TD><TD>Revision indicates the revision of the state represented by Data.</TD></TR>
</TBODY>
</TABLE>
<H3 id="controllerrevisionlist-v1beta2-apps">ControllerRevisionList v1beta2 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a> array</I></TD><TD>Items is the list of ControllerRevisions</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-controllerrevision-v1beta2-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-controllerrevision-v1beta2-apps">Create</H2>
<P>create a ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1beta2/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-controllerrevision-v1beta2-apps">Patch</H2>
<P>partially update the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-controllerrevision-v1beta2-apps">Replace</H2>
<P>replace the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-controllerrevision-v1beta2-apps">Delete</H2>
<P>delete a ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-controllerrevision-v1beta2-apps">Delete Collection</H2>
<P>delete collection of ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-controllerrevision-v1beta2-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-controllerrevision-v1beta2-apps">Read</H2>
<P>read the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1beta2-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-controllerrevision-v1beta2-apps">List</H2>
<P>list or watch objects of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevisionlist-v1beta2-apps">ControllerRevisionList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-controllerrevision-v1beta2-apps">List All Namespaces</H2>
<P>list or watch objects of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/controllerrevisions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevisionlist-v1beta2-apps">ControllerRevisionList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-controllerrevision-v1beta2-apps">Watch</H2>
<P>watch changes to an object of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-controllerrevision-v1beta2-apps">Watch List</H2>
<P>watch individual changes to a list of ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-controllerrevision-v1beta2-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/controllerrevisions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="controllerrevision-v1beta1-apps">ControllerRevision v1beta1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ControllerRevision</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#controllerrevision-v1-apps">v1</a>
<a href="#controllerrevision-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#controllerrevisionlist-v1beta1-apps">ControllerRevisionList [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>data</CODE></TD><TD>Data is the serialized representation of the state.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>revision</CODE><BR /><I>integer</I></TD><TD>Revision indicates the revision of the state represented by Data.</TD></TR>
</TBODY>
</TABLE>
<H3 id="controllerrevisionlist-v1beta1-apps">ControllerRevisionList v1beta1 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a> array</I></TD><TD>Items is the list of ControllerRevisions</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-controllerrevision-v1beta1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-controllerrevision-v1beta1-apps">Create</H2>
<P>create a ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1beta1/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-controllerrevision-v1beta1-apps">Patch</H2>
<P>partially update the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-controllerrevision-v1beta1-apps">Replace</H2>
<P>replace the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-controllerrevision-v1beta1-apps">Delete</H2>
<P>delete a ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-controllerrevision-v1beta1-apps">Delete Collection</H2>
<P>delete collection of ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta1/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-controllerrevision-v1beta1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-controllerrevision-v1beta1-apps">Read</H2>
<P>read the specified ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevision-v1beta1-apps">ControllerRevision</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-controllerrevision-v1beta1-apps">List</H2>
<P>list or watch objects of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevisionlist-v1beta1-apps">ControllerRevisionList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-controllerrevision-v1beta1-apps">List All Namespaces</H2>
<P>list or watch objects of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/controllerrevisions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#controllerrevisionlist-v1beta1-apps">ControllerRevisionList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-controllerrevision-v1beta1-apps">Watch</H2>
<P>watch changes to an object of kind ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/watch/namespaces/{namespace}/controllerrevisions/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ControllerRevision</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-controllerrevision-v1beta1-apps">Watch List</H2>
<P>watch individual changes to a list of ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/watch/namespaces/{namespace}/controllerrevisions</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-controllerrevision-v1beta1-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ControllerRevision</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/watch/controllerrevisions</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="cronjob-v2alpha1-batch">CronJob v2alpha1 batch</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>batch</CODE></TD><TD><CODE>v2alpha1</CODE></TD><TD><CODE>CronJob</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#cronjob-v1beta1-batch">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjoblist-v2alpha1-batch">CronJobList [batch/v2alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#cronjobspec-v2alpha1-batch">CronJobSpec</a></I></TD><TD>Specification of the desired behavior of a cron job, including the schedule. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#cronjobstatus-v2alpha1-batch">CronJobStatus</a></I></TD><TD>Current status of a cron job. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="cronjobspec-v2alpha1-batch">CronJobSpec v2alpha1 batch</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjob-v2alpha1-batch">CronJob [batch/v2alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>concurrencyPolicy</CODE><BR /><I>string</I></TD><TD>Specifies how to treat concurrent executions of a Job. Valid values are: - &#34;Allow&#34; (default): allows CronJobs to run concurrently; - &#34;Forbid&#34;: forbids concurrent runs, skipping next run if previous run hasn&#39;t finished yet; - &#34;Replace&#34;: cancels currently running job and replaces it with a new one</TD></TR>
<TR><TD><CODE>failedJobsHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of failed finished jobs to retain. This is a pointer to distinguish between explicit zero and not specified.</TD></TR>
<TR><TD><CODE>jobTemplate</CODE><BR /><I><a href="#jobtemplatespec-v2alpha1-batch">JobTemplateSpec</a></I></TD><TD>Specifies the job that will be created when executing a CronJob.</TD></TR>
<TR><TD><CODE>schedule</CODE><BR /><I>string</I></TD><TD>The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.</TD></TR>
<TR><TD><CODE>startingDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>Optional deadline in seconds for starting the job if it misses scheduled time for any reason. Missed jobs executions will be counted as failed ones.</TD></TR>
<TR><TD><CODE>successfulJobsHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of successful finished jobs to retain. This is a pointer to distinguish between explicit zero and not specified.</TD></TR>
<TR><TD><CODE>suspend</CODE><BR /><I>boolean</I></TD><TD>This flag tells the controller to suspend subsequent executions, it does not apply to already started executions. Defaults to false.</TD></TR>
</TBODY>
</TABLE>
<H3 id="cronjobstatus-v2alpha1-batch">CronJobStatus v2alpha1 batch</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjob-v2alpha1-batch">CronJob [batch/v2alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>active</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a> array</I></TD><TD>A list of pointers to currently running jobs.</TD></TR>
<TR><TD><CODE>lastScheduleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Information when was the last time the job was successfully scheduled.</TD></TR>
</TBODY>
</TABLE>
<H3 id="cronjoblist-v2alpha1-batch">CronJobList v2alpha1 batch</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#cronjob-v2alpha1-batch">CronJob</a> array</I></TD><TD>items is the list of CronJobs.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-cronjob-v2alpha1-batch-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-cronjob-v2alpha1-batch">Create</H2>
<P>create a CronJob</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-cronjob-v2alpha1-batch">Patch</H2>
<P>partially update the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-cronjob-v2alpha1-batch">Replace</H2>
<P>replace the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-cronjob-v2alpha1-batch">Delete</H2>
<P>delete a CronJob</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-cronjob-v2alpha1-batch">Delete Collection</H2>
<P>delete collection of CronJob</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-cronjob-v2alpha1-batch-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-cronjob-v2alpha1-batch">Read</H2>
<P>read the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-cronjob-v2alpha1-batch">List</H2>
<P>list or watch objects of kind CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjoblist-v2alpha1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-cronjob-v2alpha1-batch">List All Namespaces</H2>
<P>list or watch objects of kind CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v2alpha1/cronjobs</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjoblist-v2alpha1-batch">CronJobList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-cronjob-v2alpha1-batch">Watch</H2>
<P>watch changes to an object of kind CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v2alpha1/watch/namespaces/{namespace}/cronjobs/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-cronjob-v2alpha1-batch">Watch List</H2>
<P>watch individual changes to a list of CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v2alpha1/watch/namespaces/{namespace}/cronjobs</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-cronjob-v2alpha1-batch">Watch List All Namespaces</H2>
<P>watch individual changes to a list of CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v2alpha1/watch/cronjobs</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-cronjob-v2alpha1-batch-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-cronjob-v2alpha1-batch">Patch Status</H2>
<P>partially update status of the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-cronjob-v2alpha1-batch">Read Status</H2>
<P>read status of the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-cronjob-v2alpha1-batch">Replace Status</H2>
<P>replace status of the specified CronJob</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/batch/v2alpha1/namespaces/{namespace}/cronjobs/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the CronJob</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#cronjob-v2alpha1-batch">CronJob</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="crossversionobjectreference-v2beta1-autoscaling">CrossVersionObjectReference v2beta1 autoscaling</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>CrossVersionObjectReference</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#crossversionobjectreference-v1-autoscaling">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscalerspec-v2beta1-autoscaling">HorizontalPodAutoscalerSpec [autoscaling/v2beta1]</a></LI>
<LI><a href="#objectmetricsource-v2beta1-autoscaling">ObjectMetricSource [autoscaling/v2beta1]</a></LI>
<LI><a href="#objectmetricstatus-v2beta1-autoscaling">ObjectMetricStatus [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>API version of the referent</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds&#34;</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names</TD></TR>
</TBODY>
</TABLE>
<H1 id="daemonset-v1beta2-apps">DaemonSet v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>DaemonSet</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#daemonset-v1-apps">v1</a>
<a href="#daemonset-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetlist-v1beta2-apps">DaemonSetList [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#daemonsetspec-v1beta2-apps">DaemonSetSpec</a></I></TD><TD>The desired behavior of this daemon set. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#daemonsetstatus-v1beta2-apps">DaemonSetStatus</a></I></TD><TD>The current status of this daemon set. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="daemonsetspec-v1beta2-apps">DaemonSetSpec v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonset-v1beta2-apps">DaemonSet [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over pods that are managed by the daemon set. Must match in order to be controlled. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>An object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template&#39;s node selector (or on every node if no node selector is specified). More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
<TR><TD><CODE>updateStrategy</CODE><BR /><I><a href="#daemonsetupdatestrategy-v1beta2-apps">DaemonSetUpdateStrategy</a></I></TD><TD>An update strategy to replace existing DaemonSet pods with new pods.</TD></TR>
</TBODY>
</TABLE>
<H3 id="daemonsetstatus-v1beta2-apps">DaemonSetStatus v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonset-v1beta2-apps">DaemonSet [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#daemonsetcondition-v1beta2-apps">DaemonSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a DaemonSet&#39;s current state.</TD></TR>
<TR><TD><CODE>currentNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
<TR><TD><CODE>desiredNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
<TR><TD><CODE>numberAvailable</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)</TD></TR>
<TR><TD><CODE>numberMisscheduled</CODE><BR /><I>integer</I></TD><TD>The number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
<TR><TD><CODE>numberReady</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.</TD></TR>
<TR><TD><CODE>numberUnavailable</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The most recent generation observed by the daemon set controller.</TD></TR>
<TR><TD><CODE>updatedNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The total number of nodes that are running updated daemon pod</TD></TR>
</TBODY>
</TABLE>
<H3 id="daemonsetlist-v1beta2-apps">DaemonSetList v1beta2 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a> array</I></TD><TD>A list of daemon sets.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H3 id="rollingupdatedaemonset-v1beta2-apps">RollingUpdateDaemonSet v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetupdatestrategy-v1beta2-apps">DaemonSetUpdateStrategy [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxUnavailable</CODE></TD><TD>The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-daemonset-v1beta2-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-daemonset-v1beta2-apps">Create</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-create-daemonset-v1beta2-apps" aria-controls="req-kubectl-create-daemonset-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-create-daemonset-v1beta2-apps" aria-controls="req-curl-create-daemonset-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-create-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
name: daemonset-example
spec:
template:
metadata:
labels:
app: daemonset-example
spec:
containers:
- name: daemonset-example
image: ubuntu:trusty
command:
- /bin/sh
args:
- -c
- >-
while [ true ]; do
echo "DaemonSet running on $(hostname)" ;
sleep 10 ;
done
' | kubectl create -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-create-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X POST -H 'Content-Type: application/yaml' --data '
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
name: daemonset-example
spec:
template:
metadata:
labels:
app: daemonset-example
spec:
containers:
- name: daemonset-example
image: ubuntu:trusty
command:
- /bin/sh
args:
- -c
- >-
while [ true ]; do
echo "DaemonSet running on $(hostname)" ;
sleep 10 ;
done
' http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/daemonsets
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-create-daemonset-v1beta2-apps" aria-controls="res-kubectl-create-daemonset-v1beta2-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-create-daemonset-v1beta2-apps" aria-controls="res-curl-create-daemonset-v1beta2-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-create-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
daemonset "daemonset-example" created
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-create-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "DaemonSet",
"apiVersion": "extensions/v1beta1",
"metadata": {
"name": "daemonset-example",
"namespace": "default",
"selfLink": "/apis/extensions/v1beta1/namespaces/default/daemonsets/daemonset-example",
"uid": "65552ced-b0e2-11e6-aef0-42010af00229",
"resourceVersion": "3558",
"generation": 1,
"creationTimestamp": "2016-11-22T18:35:09Z",
"labels": {
"app": "daemonset-example"
}
},
"spec": {
"selector": {
"matchLabels": {
"app": "daemonset-example"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "daemonset-example"
}
},
"spec": {
"containers": [
{
"name": "daemonset-example",
"image": "ubuntu:trusty",
"command": [
"/bin/sh"
],
"args": [
"-c",
"while [ true ]; do echo \"DaemonSet running on $(hostname)\" ; sleep 10 ; done"
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
}
},
"status": {
"currentNumberScheduled": 0,
"numberMisscheduled": 0,
"desiredNumberScheduled": 0
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>create a DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1beta2/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-daemonset-v1beta2-apps">Patch</H2>
<P>partially update the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-daemonset-v1beta2-apps">Replace</H2>
<P>replace the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-daemonset-v1beta2-apps">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-delete-daemonset-v1beta2-apps" aria-controls="req-kubectl-delete-daemonset-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-delete-daemonset-v1beta2-apps" aria-controls="req-curl-delete-daemonset-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-delete-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl delete daemonset daemonset-example
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-delete-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
gracePeriodSeconds: 0
orphanDependents: false
' 'http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/daemonsets/daemonset-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-delete-daemonset-v1beta2-apps" aria-controls="res-kubectl-delete-daemonset-v1beta2-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-delete-daemonset-v1beta2-apps" aria-controls="res-curl-delete-daemonset-v1beta2-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-delete-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
daemonset "daemonset-example" deleted
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-delete-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"code": 200
}
</CODE></PRE></DIV></DIV></DIV>
<P>delete a DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-daemonset-v1beta2-apps">Delete Collection</H2>
<P>delete collection of DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-daemonset-v1beta2-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-daemonset-v1beta2-apps">Read</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-read-daemonset-v1beta2-apps" aria-controls="req-kubectl-read-daemonset-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-read-daemonset-v1beta2-apps" aria-controls="req-curl-read-daemonset-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-read-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get daemonset daemonset-example -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-read-daemonset-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/daemonsets/daemonset-example
</CODE></PRE></DIV></DIV></DIV>
<P>read the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-daemonset-v1beta2-apps">List</H2>
<P>list or watch objects of kind DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonsetlist-v1beta2-apps">DaemonSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-daemonset-v1beta2-apps">List All Namespaces</H2>
<P>list or watch objects of kind DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/daemonsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonsetlist-v1beta2-apps">DaemonSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-daemonset-v1beta2-apps">Watch</H2>
<P>watch changes to an object of kind DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-daemonset-v1beta2-apps">Watch List</H2>
<P>watch individual changes to a list of DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-daemonset-v1beta2-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/daemonsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-daemonset-v1beta2-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-daemonset-v1beta2-apps">Patch Status</H2>
<P>partially update status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/daemonsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-daemonset-v1beta2-apps">Read Status</H2>
<P>read status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/daemonsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-daemonset-v1beta2-apps">Replace Status</H2>
<P>replace status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/daemonsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#daemonset-v1beta2-apps">DaemonSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="daemonset-v1beta1-extensions">DaemonSet v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DaemonSet</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#daemonset-v1-apps">v1</a>
<a href="#daemonset-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetlist-v1beta1-extensions">DaemonSetList [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#daemonsetspec-v1beta1-extensions">DaemonSetSpec</a></I></TD><TD>The desired behavior of this daemon set. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#daemonsetstatus-v1beta1-extensions">DaemonSetStatus</a></I></TD><TD>The current status of this daemon set. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="daemonsetspec-v1beta1-extensions">DaemonSetSpec v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonset-v1beta1-extensions">DaemonSet [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>The minimum number of seconds for which a newly created DaemonSet pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready).</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of old history to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>A label query over pods that are managed by the daemon set. Must match in order to be controlled. If empty, defaulted to labels on Pod template. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>An object that describes the pod that will be created. The DaemonSet will create exactly one copy of this pod on every node that matches the template&#39;s node selector (or on every node if no node selector is specified). More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
<TR><TD><CODE>templateGeneration</CODE><BR /><I>integer</I></TD><TD>DEPRECATED. A sequence number representing a specific generation of the template. Populated by the system. It can be set only during the creation.</TD></TR>
<TR><TD><CODE>updateStrategy</CODE><BR /><I><a href="#daemonsetupdatestrategy-v1beta1-extensions">DaemonSetUpdateStrategy</a></I></TD><TD>An update strategy to replace existing DaemonSet pods with new pods.</TD></TR>
</TBODY>
</TABLE>
<H3 id="daemonsetstatus-v1beta1-extensions">DaemonSetStatus v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonset-v1beta1-extensions">DaemonSet [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>Count of hash collisions for the DaemonSet. The DaemonSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#daemonsetcondition-v1beta1-extensions">DaemonSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a DaemonSet&#39;s current state.</TD></TR>
<TR><TD><CODE>currentNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
<TR><TD><CODE>desiredNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The total number of nodes that should be running the daemon pod (including nodes correctly running the daemon pod). More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
<TR><TD><CODE>numberAvailable</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and available (ready for at least spec.minReadySeconds)</TD></TR>
<TR><TD><CODE>numberMisscheduled</CODE><BR /><I>integer</I></TD><TD>The number of nodes that are running the daemon pod, but are not supposed to run the daemon pod. More info: https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/</TD></TR>
<TR><TD><CODE>numberReady</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have one or more of the daemon pod running and ready.</TD></TR>
<TR><TD><CODE>numberUnavailable</CODE><BR /><I>integer</I></TD><TD>The number of nodes that should be running the daemon pod and have none of the daemon pod running and available (ready for at least spec.minReadySeconds)</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The most recent generation observed by the daemon set controller.</TD></TR>
<TR><TD><CODE>updatedNumberScheduled</CODE><BR /><I>integer</I></TD><TD>The total number of nodes that are running updated daemon pod</TD></TR>
</TBODY>
</TABLE>
<H3 id="daemonsetlist-v1beta1-extensions">DaemonSetList v1beta1 extensions</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a> array</I></TD><TD>A list of daemon sets.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H3 id="rollingupdatedaemonset-v1beta1-extensions">RollingUpdateDaemonSet v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetupdatestrategy-v1beta1-extensions">DaemonSetUpdateStrategy [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxUnavailable</CODE></TD><TD>The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0. Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-daemonset-v1beta1-extensions-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-daemonset-v1beta1-extensions">Create</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-create-daemonset-v1beta1-extensions" aria-controls="req-kubectl-create-daemonset-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-create-daemonset-v1beta1-extensions" aria-controls="req-curl-create-daemonset-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-create-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
name: daemonset-example
spec:
template:
metadata:
labels:
app: daemonset-example
spec:
containers:
- name: daemonset-example
image: ubuntu:trusty
command:
- /bin/sh
args:
- -c
- >-
while [ true ]; do
echo "DaemonSet running on $(hostname)" ;
sleep 10 ;
done
' | kubectl create -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-create-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X POST -H 'Content-Type: application/yaml' --data '
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
name: daemonset-example
spec:
template:
metadata:
labels:
app: daemonset-example
spec:
containers:
- name: daemonset-example
image: ubuntu:trusty
command:
- /bin/sh
args:
- -c
- >-
while [ true ]; do
echo "DaemonSet running on $(hostname)" ;
sleep 10 ;
done
' http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/daemonsets
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-create-daemonset-v1beta1-extensions" aria-controls="res-kubectl-create-daemonset-v1beta1-extensions"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-create-daemonset-v1beta1-extensions" aria-controls="res-curl-create-daemonset-v1beta1-extensions"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-create-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
daemonset "daemonset-example" created
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-create-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "DaemonSet",
"apiVersion": "extensions/v1beta1",
"metadata": {
"name": "daemonset-example",
"namespace": "default",
"selfLink": "/apis/extensions/v1beta1/namespaces/default/daemonsets/daemonset-example",
"uid": "65552ced-b0e2-11e6-aef0-42010af00229",
"resourceVersion": "3558",
"generation": 1,
"creationTimestamp": "2016-11-22T18:35:09Z",
"labels": {
"app": "daemonset-example"
}
},
"spec": {
"selector": {
"matchLabels": {
"app": "daemonset-example"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "daemonset-example"
}
},
"spec": {
"containers": [
{
"name": "daemonset-example",
"image": "ubuntu:trusty",
"command": [
"/bin/sh"
],
"args": [
"-c",
"while [ true ]; do echo \"DaemonSet running on $(hostname)\" ; sleep 10 ; done"
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
}
},
"status": {
"currentNumberScheduled": 0,
"numberMisscheduled": 0,
"desiredNumberScheduled": 0
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>create a DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-daemonset-v1beta1-extensions">Patch</H2>
<P>partially update the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-daemonset-v1beta1-extensions">Replace</H2>
<P>replace the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-daemonset-v1beta1-extensions">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-delete-daemonset-v1beta1-extensions" aria-controls="req-kubectl-delete-daemonset-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-delete-daemonset-v1beta1-extensions" aria-controls="req-curl-delete-daemonset-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-delete-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl delete daemonset daemonset-example
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-delete-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
gracePeriodSeconds: 0
orphanDependents: false
' 'http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/daemonsets/daemonset-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-delete-daemonset-v1beta1-extensions" aria-controls="res-kubectl-delete-daemonset-v1beta1-extensions"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-delete-daemonset-v1beta1-extensions" aria-controls="res-curl-delete-daemonset-v1beta1-extensions"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-delete-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
daemonset "daemonset-example" deleted
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-delete-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"code": 200
}
</CODE></PRE></DIV></DIV></DIV>
<P>delete a DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-daemonset-v1beta1-extensions">Delete Collection</H2>
<P>delete collection of DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-daemonset-v1beta1-extensions-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-daemonset-v1beta1-extensions">Read</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-read-daemonset-v1beta1-extensions" aria-controls="req-kubectl-read-daemonset-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-read-daemonset-v1beta1-extensions" aria-controls="req-curl-read-daemonset-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-read-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get daemonset daemonset-example -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-read-daemonset-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/daemonsets/daemonset-example
</CODE></PRE></DIV></DIV></DIV>
<P>read the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-daemonset-v1beta1-extensions">List</H2>
<P>list or watch objects of kind DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonsetlist-v1beta1-extensions">DaemonSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-daemonset-v1beta1-extensions">List All Namespaces</H2>
<P>list or watch objects of kind DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/daemonsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonsetlist-v1beta1-extensions">DaemonSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-daemonset-v1beta1-extensions">Watch</H2>
<P>watch changes to an object of kind DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/daemonsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-daemonset-v1beta1-extensions">Watch List</H2>
<P>watch individual changes to a list of DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/daemonsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-daemonset-v1beta1-extensions">Watch List All Namespaces</H2>
<P>watch individual changes to a list of DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/daemonsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-daemonset-v1beta1-extensions-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-daemonset-v1beta1-extensions">Patch Status</H2>
<P>partially update status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-daemonset-v1beta1-extensions">Read Status</H2>
<P>read status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-daemonset-v1beta1-extensions">Replace Status</H2>
<P>replace status of the specified DaemonSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/daemonsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DaemonSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#daemonset-v1beta1-extensions">DaemonSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="daemonsetcondition-v1beta2-apps">DaemonSetCondition v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>DaemonSetCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#daemonsetcondition-v1-apps">v1</a>
<a href="#daemonsetcondition-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetstatus-v1beta2-apps">DaemonSetStatus [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of DaemonSet condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="daemonsetcondition-v1beta1-extensions">DaemonSetCondition v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DaemonSetCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#daemonsetcondition-v1-apps">v1</a>
<a href="#daemonsetcondition-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetstatus-v1beta1-extensions">DaemonSetStatus [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of DaemonSet condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="daemonsetupdatestrategy-v1beta2-apps">DaemonSetUpdateStrategy v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>DaemonSetUpdateStrategy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#daemonsetupdatestrategy-v1-apps">v1</a>
<a href="#daemonsetupdatestrategy-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetspec-v1beta2-apps">DaemonSetSpec [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatedaemonset-v1beta2-apps">RollingUpdateDaemonSet</a></I></TD><TD>Rolling update config params. Present only if type = &#34;RollingUpdate&#34;.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of daemon set update. Can be &#34;RollingUpdate&#34; or &#34;OnDelete&#34;. Default is RollingUpdate.</TD></TR>
</TBODY>
</TABLE>
<H1 id="daemonsetupdatestrategy-v1beta1-extensions">DaemonSetUpdateStrategy v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DaemonSetUpdateStrategy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#daemonsetupdatestrategy-v1-apps">v1</a>
<a href="#daemonsetupdatestrategy-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#daemonsetspec-v1beta1-extensions">DaemonSetSpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatedaemonset-v1beta1-extensions">RollingUpdateDaemonSet</a></I></TD><TD>Rolling update config params. Present only if type = &#34;RollingUpdate&#34;.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of daemon set update. Can be &#34;RollingUpdate&#34; or &#34;OnDelete&#34;. Default is OnDelete.</TD></TR>
</TBODY>
</TABLE>
<H1 id="deployment-v1beta2-apps">Deployment v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>Deployment</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#deployment-v1-apps">v1</a>
<a href="#deployment-v1beta1-apps">v1beta1</a>
<a href="#deployment-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentlist-v1beta2-apps">DeploymentList [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#deploymentspec-v1beta2-apps">DeploymentSpec</a></I></TD><TD>Specification of the desired behavior of the Deployment.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#deploymentstatus-v1beta2-apps">DeploymentStatus</a></I></TD><TD>Most recently observed status of the Deployment.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentspec-v1beta2-apps">DeploymentSpec v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deployment-v1beta2-apps">Deployment [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
<TR><TD><CODE>paused</CODE><BR /><I>boolean</I></TD><TD>Indicates that the deployment is paused.</TD></TR>
<TR><TD><CODE>progressDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. Defaults to 600s.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 10.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment. It must match the pod template&#39;s labels.</TD></TR>
<TR><TD><CODE>strategy</CODE><BR /><I><a href="#deploymentstrategy-v1beta2-apps">DeploymentStrategy</a></I></TD><TD>The deployment strategy to use to replace existing pods with new ones.</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template describes the pods that will be created.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentstatus-v1beta2-apps">DeploymentStatus v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deployment-v1beta2-apps">Deployment [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.</TD></TR>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#deploymentcondition-v1beta2-apps">DeploymentCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a deployment&#39;s current state.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The generation observed by the deployment controller.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of ready pods targeted by this deployment.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment (their labels match the selector).</TD></TR>
<TR><TD><CODE>unavailableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.</TD></TR>
<TR><TD><CODE>updatedReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment that have the desired template spec.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentlist-v1beta2-apps">DeploymentList v1beta2 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#deployment-v1beta2-apps">Deployment</a> array</I></TD><TD>Items is the list of Deployments.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentstrategy-v1beta2-apps">DeploymentStrategy v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentspec-v1beta2-apps">DeploymentSpec [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatedeployment-v1beta2-apps">RollingUpdateDeployment</a></I></TD><TD>Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment. Can be &#34;Recreate&#34; or &#34;RollingUpdate&#34;. Default is RollingUpdate.</TD></TR>
</TBODY>
</TABLE>
<H3 id="rollingupdatedeployment-v1beta2-apps">RollingUpdateDeployment v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentstrategy-v1beta2-apps">DeploymentStrategy [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxSurge</CODE></TD><TD>The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new ReplicaSet can be scaled up further, ensuring that total number of pods running at any time during the update is atmost 130% of desired pods.</TD></TR>
<TR><TD><CODE>maxUnavailable</CODE></TD><TD>The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old ReplicaSet can be scaled down further, followed by scaling up the new ReplicaSet, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-deployment-v1beta2-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-deployment-v1beta2-apps">Create</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-create-deployment-v1beta2-apps" aria-controls="req-kubectl-create-deployment-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-create-deployment-v1beta2-apps" aria-controls="req-curl-create-deployment-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-create-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.10
ports:
- containerPort: 80
' | kubectl create -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-create-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X POST -H 'Content-Type: application/yaml' --data '
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.10
ports:
- containerPort: 80
' http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/deployments
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-create-deployment-v1beta2-apps" aria-controls="res-kubectl-create-deployment-v1beta2-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-create-deployment-v1beta2-apps" aria-controls="res-curl-create-deployment-v1beta2-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-create-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" created
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-create-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
"resourceVersion": "2118306",
"generation": 1,
"creationTimestamp": "2016-10-28T01:53:19Z",
"labels": {
"app": "nginx"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {}
}
</CODE></PRE></DIV></DIV></DIV>
<P>create a Deployment</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1beta2/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-deployment-v1beta2-apps">Patch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-patch-deployment-v1beta2-apps" aria-controls="req-kubectl-patch-deployment-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-patch-deployment-v1beta2-apps" aria-controls="req-curl-patch-deployment-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-patch-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl patch deployment deployment-example -p \
'{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.11"}]}}}}'
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-patch-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PATCH -H 'Content-Type: application/strategic-merge-patch+json' --data '
{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.11"}]}}}}' \
'http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-patch-deployment-v1beta2-apps" aria-controls="res-kubectl-patch-deployment-v1beta2-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-patch-deployment-v1beta2-apps" aria-controls="res-curl-patch-deployment-v1beta2-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-patch-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
"deployment-example" patched
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-patch-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "5dc3a8e6-b0ee-11e6-aef0-42010af00229",
"resourceVersion": "164489",
"generation": 11,
"creationTimestamp": "2016-11-22T20:00:50Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "5"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.11",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {
"observedGeneration": 10,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>partially update the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-deployment-v1beta2-apps">Replace</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-replace-deployment-v1beta2-apps" aria-controls="req-kubectl-replace-deployment-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-replace-deployment-v1beta2-apps" aria-controls="req-curl-replace-deployment-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-replace-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.11
ports:
- containerPort: 80
' | kubectl replace -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-replace-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PUT -H 'Content-Type: application/yaml' --data '
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.11
ports:
- containerPort: 80
' http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/deployments/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-replace-deployment-v1beta2-apps" aria-controls="res-kubectl-replace-deployment-v1beta2-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-replace-deployment-v1beta2-apps" aria-controls="res-curl-replace-deployment-v1beta2-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-replace-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" replaced
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-replace-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
"resourceVersion": "2119082",
"generation": 5,
"creationTimestamp": "2016-10-28T01:53:19Z",
"labels": {
"app": "nginx"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.11",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>replace the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-deployment-v1beta2-apps">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-delete-deployment-v1beta2-apps" aria-controls="req-kubectl-delete-deployment-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-delete-deployment-v1beta2-apps" aria-controls="req-curl-delete-deployment-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-delete-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl delete deployment deployment-example
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-delete-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
gracePeriodSeconds: 0
orphanDependents: false
' 'http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-delete-deployment-v1beta2-apps" aria-controls="res-kubectl-delete-deployment-v1beta2-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-delete-deployment-v1beta2-apps" aria-controls="res-curl-delete-deployment-v1beta2-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-delete-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" deleted
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-delete-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"code": 200
}
</CODE></PRE></DIV></DIV></DIV>
<P>delete a Deployment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-deployment-v1beta2-apps">Delete Collection</H2>
<P>delete collection of Deployment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-deployment-v1beta2-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-deployment-v1beta2-apps">Read</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-read-deployment-v1beta2-apps" aria-controls="req-kubectl-read-deployment-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-read-deployment-v1beta2-apps" aria-controls="req-curl-read-deployment-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-read-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment deployment-example -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-read-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/deployments/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-read-deployment-v1beta2-apps" aria-controls="res-kubectl-read-deployment-v1beta2-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-read-deployment-v1beta2-apps" aria-controls="res-curl-read-deployment-v1beta2-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-read-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-read-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>read the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-deployment-v1beta2-apps">List</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-list-deployment-v1beta2-apps" aria-controls="req-kubectl-list-deployment-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-list-deployment-v1beta2-apps" aria-controls="req-curl-list-deployment-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-list-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-list-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1beta2/namespaces/default/deployments'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-list-deployment-v1beta2-apps" aria-controls="res-kubectl-list-deployment-v1beta2-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-list-deployment-v1beta2-apps" aria-controls="res-curl-list-deployment-v1beta2-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-list-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "List",
"apiVersion": "v1",
"metadata": {},
"items": [
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "docs",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
"uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
"resourceVersion": "1924126",
"generation": 21,
"creationTimestamp": "2016-10-13T16:06:00Z",
"labels": {
"run": "docs"
},
"annotations": {
"deployment.kubernetes.io/revision": "10",
"replicatingperfection.net/push-image": "true"
}
},
"spec": {
"replicas": 1,
"selector": {
"matchLabels": {
"run": "docs"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"auto-pushed-image-pwittrock/api-docs": "1477496453",
"run": "docs"
}
},
"spec": {
"containers": [
{
"name": "docs",
"image": "pwittrock/api-docs:v9",
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 21,
"replicas": 1,
"updatedReplicas": 1,
"availableReplicas": 1
}
},
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-list-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "List",
"apiVersion": "v1",
"metadata": {},
"items": [
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "docs",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
"uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
"resourceVersion": "1924126",
"generation": 21,
"creationTimestamp": "2016-10-13T16:06:00Z",
"labels": {
"run": "docs"
},
"annotations": {
"deployment.kubernetes.io/revision": "10",
"replicatingperfection.net/push-image": "true"
}
},
"spec": {
"replicas": 1,
"selector": {
"matchLabels": {
"run": "docs"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"auto-pushed-image-pwittrock/api-docs": "1477496453",
"run": "docs"
}
},
"spec": {
"containers": [
{
"name": "docs",
"image": "pwittrock/api-docs:v9",
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 21,
"replicas": 1,
"updatedReplicas": 1,
"availableReplicas": 1
}
},
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<P>list or watch objects of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deploymentlist-v1beta2-apps">DeploymentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-deployment-v1beta2-apps">List All Namespaces</H2>
<P>list or watch objects of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/deployments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deploymentlist-v1beta2-apps">DeploymentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-deployment-v1beta2-apps">Watch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-watch-deployment-v1beta2-apps" aria-controls="req-kubectl-watch-deployment-v1beta2-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-watch-deployment-v1beta2-apps" aria-controls="req-curl-watch-deployment-v1beta2-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-watch-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment deployment-example --watch -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-watch-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1beta2/watch/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-watch-deployment-v1beta2-apps" aria-controls="res-kubectl-watch-deployment-v1beta2-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-watch-deployment-v1beta2-apps" aria-controls="res-curl-watch-deployment-v1beta2-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-watch-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
"resourceVersion": "2128095",
"generation": 2,
"creationTimestamp": "2016-10-28T03:34:12Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "3"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 2,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-watch-deployment-v1beta2-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
"resourceVersion": "2128095",
"generation": 2,
"creationTimestamp": "2016-10-28T03:34:12Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "3"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 2,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>watch changes to an object of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-deployment-v1beta2-apps">Watch List</H2>
<P>watch individual changes to a list of Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-deployment-v1beta2-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/deployments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-deployment-v1beta2-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-deployment-v1beta2-apps">Patch Status</H2>
<P>partially update status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-deployment-v1beta2-apps">Read Status</H2>
<P>read status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-deployment-v1beta2-apps">Replace Status</H2>
<P>replace status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#deployment-v1beta2-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-deployment-v1beta2-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-deployment-v1beta2-apps">Read Scale</H2>
<P>read scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-deployment-v1beta2-apps">Replace Scale</H2>
<P>replace scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-deployment-v1beta2-apps">Patch Scale</H2>
<P>partially update scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="deployment-v1beta1-apps">Deployment v1beta1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Deployment</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#deployment-v1-apps">v1</a>
<a href="#deployment-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentlist-v1beta1-apps">DeploymentList [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#deploymentspec-v1beta1-apps">DeploymentSpec</a></I></TD><TD>Specification of the desired behavior of the Deployment.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#deploymentstatus-v1beta1-apps">DeploymentStatus</a></I></TD><TD>Most recently observed status of the Deployment.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentspec-v1beta1-apps">DeploymentSpec v1beta1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deployment-v1beta1-apps">Deployment [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
<TR><TD><CODE>paused</CODE><BR /><I>boolean</I></TD><TD>Indicates that the deployment is paused.</TD></TR>
<TR><TD><CODE>progressDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. Defaults to 600s.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified. Defaults to 2.</TD></TR>
<TR><TD><CODE>rollbackTo</CODE><BR /><I><a href="#rollbackconfig-v1beta1-apps">RollbackConfig</a></I></TD><TD>DEPRECATED. The config this deployment is rolling back to. Will be cleared after rollback is done.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment.</TD></TR>
<TR><TD><CODE>strategy</CODE><BR /><I><a href="#deploymentstrategy-v1beta1-apps">DeploymentStrategy</a></I></TD><TD>The deployment strategy to use to replace existing pods with new ones.</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template describes the pods that will be created.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentstatus-v1beta1-apps">DeploymentStatus v1beta1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deployment-v1beta1-apps">Deployment [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.</TD></TR>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#deploymentcondition-v1beta1-apps">DeploymentCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a deployment&#39;s current state.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The generation observed by the deployment controller.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of ready pods targeted by this deployment.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment (their labels match the selector).</TD></TR>
<TR><TD><CODE>unavailableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.</TD></TR>
<TR><TD><CODE>updatedReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment that have the desired template spec.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentlist-v1beta1-apps">DeploymentList v1beta1 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#deployment-v1beta1-apps">Deployment</a> array</I></TD><TD>Items is the list of Deployments.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentstrategy-v1beta1-apps">DeploymentStrategy v1beta1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentspec-v1beta1-apps">DeploymentSpec [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatedeployment-v1beta1-apps">RollingUpdateDeployment</a></I></TD><TD>Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment. Can be &#34;Recreate&#34; or &#34;RollingUpdate&#34;. Default is RollingUpdate.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentrollback-v1beta1-apps">DeploymentRollback v1beta1 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Required: This must match the Name of a deployment.</TD></TR>
<TR><TD><CODE>rollbackTo</CODE><BR /><I><a href="#rollbackconfig-v1beta1-apps">RollbackConfig</a></I></TD><TD>The config of this deployment rollback.</TD></TR>
<TR><TD><CODE>updatedAnnotations</CODE><BR /><I>object</I></TD><TD>The annotations to be updated to a deployment</TD></TR>
</TBODY>
</TABLE>
<H3 id="rollingupdatedeployment-v1beta1-apps">RollingUpdateDeployment v1beta1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentstrategy-v1beta1-apps">DeploymentStrategy [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxSurge</CODE></TD><TD>The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%. Example: when this is set to 30%, the new ReplicaSet can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new ReplicaSet can be scaled up further, ensuring that total number of pods running at any time during the update is atmost 130% of desired pods.</TD></TR>
<TR><TD><CODE>maxUnavailable</CODE></TD><TD>The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old ReplicaSet can be scaled down further, followed by scaling up the new ReplicaSet, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-deployment-v1beta1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-deployment-v1beta1-apps">Create</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-create-deployment-v1beta1-apps" aria-controls="req-kubectl-create-deployment-v1beta1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-create-deployment-v1beta1-apps" aria-controls="req-curl-create-deployment-v1beta1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-create-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.10
ports:
- containerPort: 80
' | kubectl create -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-create-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X POST -H 'Content-Type: application/yaml' --data '
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.10
ports:
- containerPort: 80
' http://127.0.0.1:8001/apis/apps/v1beta1/namespaces/default/deployments
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-create-deployment-v1beta1-apps" aria-controls="res-kubectl-create-deployment-v1beta1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-create-deployment-v1beta1-apps" aria-controls="res-curl-create-deployment-v1beta1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-create-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" created
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-create-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
"resourceVersion": "2118306",
"generation": 1,
"creationTimestamp": "2016-10-28T01:53:19Z",
"labels": {
"app": "nginx"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {}
}
</CODE></PRE></DIV></DIV></DIV>
<P>create a Deployment</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1beta1/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-deployment-v1beta1-apps">Patch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-patch-deployment-v1beta1-apps" aria-controls="req-kubectl-patch-deployment-v1beta1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-patch-deployment-v1beta1-apps" aria-controls="req-curl-patch-deployment-v1beta1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-patch-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl patch deployment deployment-example -p \
'{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.11"}]}}}}'
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-patch-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PATCH -H 'Content-Type: application/strategic-merge-patch+json' --data '
{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.11"}]}}}}' \
'http://127.0.0.1:8001/apis/apps/v1beta1/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-patch-deployment-v1beta1-apps" aria-controls="res-kubectl-patch-deployment-v1beta1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-patch-deployment-v1beta1-apps" aria-controls="res-curl-patch-deployment-v1beta1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-patch-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
"deployment-example" patched
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-patch-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "5dc3a8e6-b0ee-11e6-aef0-42010af00229",
"resourceVersion": "164489",
"generation": 11,
"creationTimestamp": "2016-11-22T20:00:50Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "5"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.11",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {
"observedGeneration": 10,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>partially update the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-deployment-v1beta1-apps">Replace</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-replace-deployment-v1beta1-apps" aria-controls="req-kubectl-replace-deployment-v1beta1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-replace-deployment-v1beta1-apps" aria-controls="req-curl-replace-deployment-v1beta1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-replace-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.11
ports:
- containerPort: 80
' | kubectl replace -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-replace-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PUT -H 'Content-Type: application/yaml' --data '
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.11
ports:
- containerPort: 80
' http://127.0.0.1:8001/apis/apps/v1beta1/namespaces/default/deployments/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-replace-deployment-v1beta1-apps" aria-controls="res-kubectl-replace-deployment-v1beta1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-replace-deployment-v1beta1-apps" aria-controls="res-curl-replace-deployment-v1beta1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-replace-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" replaced
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-replace-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
"resourceVersion": "2119082",
"generation": 5,
"creationTimestamp": "2016-10-28T01:53:19Z",
"labels": {
"app": "nginx"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.11",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>replace the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-deployment-v1beta1-apps">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-delete-deployment-v1beta1-apps" aria-controls="req-kubectl-delete-deployment-v1beta1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-delete-deployment-v1beta1-apps" aria-controls="req-curl-delete-deployment-v1beta1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-delete-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl delete deployment deployment-example
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-delete-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
gracePeriodSeconds: 0
orphanDependents: false
' 'http://127.0.0.1:8001/apis/apps/v1beta1/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-delete-deployment-v1beta1-apps" aria-controls="res-kubectl-delete-deployment-v1beta1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-delete-deployment-v1beta1-apps" aria-controls="res-curl-delete-deployment-v1beta1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-delete-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" deleted
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-delete-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"code": 200
}
</CODE></PRE></DIV></DIV></DIV>
<P>delete a Deployment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-deployment-v1beta1-apps">Delete Collection</H2>
<P>delete collection of Deployment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta1/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-deployment-v1beta1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-deployment-v1beta1-apps">Read</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-read-deployment-v1beta1-apps" aria-controls="req-kubectl-read-deployment-v1beta1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-read-deployment-v1beta1-apps" aria-controls="req-curl-read-deployment-v1beta1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-read-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment deployment-example -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-read-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET http://127.0.0.1:8001/apis/apps/v1beta1/namespaces/default/deployments/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-read-deployment-v1beta1-apps" aria-controls="res-kubectl-read-deployment-v1beta1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-read-deployment-v1beta1-apps" aria-controls="res-curl-read-deployment-v1beta1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-read-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-read-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>read the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-deployment-v1beta1-apps">List</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-list-deployment-v1beta1-apps" aria-controls="req-kubectl-list-deployment-v1beta1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-list-deployment-v1beta1-apps" aria-controls="req-curl-list-deployment-v1beta1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-list-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-list-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1beta1/namespaces/default/deployments'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-list-deployment-v1beta1-apps" aria-controls="res-kubectl-list-deployment-v1beta1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-list-deployment-v1beta1-apps" aria-controls="res-curl-list-deployment-v1beta1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-list-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "List",
"apiVersion": "v1",
"metadata": {},
"items": [
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "docs",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
"uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
"resourceVersion": "1924126",
"generation": 21,
"creationTimestamp": "2016-10-13T16:06:00Z",
"labels": {
"run": "docs"
},
"annotations": {
"deployment.kubernetes.io/revision": "10",
"replicatingperfection.net/push-image": "true"
}
},
"spec": {
"replicas": 1,
"selector": {
"matchLabels": {
"run": "docs"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"auto-pushed-image-pwittrock/api-docs": "1477496453",
"run": "docs"
}
},
"spec": {
"containers": [
{
"name": "docs",
"image": "pwittrock/api-docs:v9",
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 21,
"replicas": 1,
"updatedReplicas": 1,
"availableReplicas": 1
}
},
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-list-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "List",
"apiVersion": "v1",
"metadata": {},
"items": [
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "docs",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
"uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
"resourceVersion": "1924126",
"generation": 21,
"creationTimestamp": "2016-10-13T16:06:00Z",
"labels": {
"run": "docs"
},
"annotations": {
"deployment.kubernetes.io/revision": "10",
"replicatingperfection.net/push-image": "true"
}
},
"spec": {
"replicas": 1,
"selector": {
"matchLabels": {
"run": "docs"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"auto-pushed-image-pwittrock/api-docs": "1477496453",
"run": "docs"
}
},
"spec": {
"containers": [
{
"name": "docs",
"image": "pwittrock/api-docs:v9",
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 21,
"replicas": 1,
"updatedReplicas": 1,
"availableReplicas": 1
}
},
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<P>list or watch objects of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deploymentlist-v1beta1-apps">DeploymentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-deployment-v1beta1-apps">List All Namespaces</H2>
<P>list or watch objects of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/deployments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deploymentlist-v1beta1-apps">DeploymentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-deployment-v1beta1-apps">Watch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-watch-deployment-v1beta1-apps" aria-controls="req-kubectl-watch-deployment-v1beta1-apps"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-watch-deployment-v1beta1-apps" aria-controls="req-curl-watch-deployment-v1beta1-apps"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-watch-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment deployment-example --watch -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-watch-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/apps/v1beta1/watch/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-watch-deployment-v1beta1-apps" aria-controls="res-kubectl-watch-deployment-v1beta1-apps"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-watch-deployment-v1beta1-apps" aria-controls="res-curl-watch-deployment-v1beta1-apps"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-watch-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
"resourceVersion": "2128095",
"generation": 2,
"creationTimestamp": "2016-10-28T03:34:12Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "3"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 2,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-watch-deployment-v1beta1-apps">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
"resourceVersion": "2128095",
"generation": 2,
"creationTimestamp": "2016-10-28T03:34:12Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "3"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 2,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>watch changes to an object of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/watch/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-deployment-v1beta1-apps">Watch List</H2>
<P>watch individual changes to a list of Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/watch/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-deployment-v1beta1-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/watch/deployments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-deployment-v1beta1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-deployment-v1beta1-apps">Patch Status</H2>
<P>partially update status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-deployment-v1beta1-apps">Read Status</H2>
<P>read status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-deployment-v1beta1-apps">Replace Status</H2>
<P>replace status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-apps">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-deployment-v1beta1-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-deployment-v1beta1-apps">Read Scale</H2>
<P>read scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-deployment-v1beta1-apps">Replace Scale</H2>
<P>replace scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-deployment-v1beta1-apps">Patch Scale</H2>
<P>partially update scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="rollback-deployment-v1beta1-apps">Rollback</H2>
<P>create rollback of a Deployment</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1beta1/namespaces/{namespace}/deployments/{name}/rollback</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeploymentRollback</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deploymentrollback-v1beta1-apps">DeploymentRollback</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#deploymentrollback-v1beta1-apps">DeploymentRollback</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#deploymentrollback-v1beta1-apps">DeploymentRollback</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#deploymentrollback-v1beta1-apps">DeploymentRollback</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="deployment-v1beta1-extensions">Deployment v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Deployment</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#deployment-v1-apps">v1</a>
<a href="#deployment-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentlist-v1beta1-extensions">DeploymentList [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#deploymentspec-v1beta1-extensions">DeploymentSpec</a></I></TD><TD>Specification of the desired behavior of the Deployment.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#deploymentstatus-v1beta1-extensions">DeploymentStatus</a></I></TD><TD>Most recently observed status of the Deployment.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentspec-v1beta1-extensions">DeploymentSpec v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deployment-v1beta1-extensions">Deployment [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
<TR><TD><CODE>paused</CODE><BR /><I>boolean</I></TD><TD>Indicates that the deployment is paused and will not be processed by the deployment controller.</TD></TR>
<TR><TD><CODE>progressDeadlineSeconds</CODE><BR /><I>integer</I></TD><TD>The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Note that progress will not be estimated during the time a deployment is paused. This is not set by default.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified.</TD></TR>
<TR><TD><CODE>rollbackTo</CODE><BR /><I><a href="#rollbackconfig-v1beta1-extensions">RollbackConfig</a></I></TD><TD>DEPRECATED. The config this deployment is rolling back to. Will be cleared after rollback is done.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment.</TD></TR>
<TR><TD><CODE>strategy</CODE><BR /><I><a href="#deploymentstrategy-v1beta1-extensions">DeploymentStrategy</a></I><BR /><B>patch strategy</B>: <I>retainKeys</I></TD><TD>The deployment strategy to use to replace existing pods with new ones.</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template describes the pods that will be created.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentstatus-v1beta1-extensions">DeploymentStatus v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deployment-v1beta1-extensions">Deployment [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of available pods (ready for at least minReadySeconds) targeted by this deployment.</TD></TR>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>Count of hash collisions for the Deployment. The Deployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ReplicaSet.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#deploymentcondition-v1beta1-extensions">DeploymentCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a deployment&#39;s current state.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>The generation observed by the deployment controller.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of ready pods targeted by this deployment.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment (their labels match the selector).</TD></TR>
<TR><TD><CODE>unavailableReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of unavailable pods targeted by this deployment. This is the total number of pods that are still required for the deployment to have 100% available capacity. They may either be pods that are running but not yet available or pods that still have not been created.</TD></TR>
<TR><TD><CODE>updatedReplicas</CODE><BR /><I>integer</I></TD><TD>Total number of non-terminated pods targeted by this deployment that have the desired template spec.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentlist-v1beta1-extensions">DeploymentList v1beta1 extensions</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#deployment-v1beta1-extensions">Deployment</a> array</I></TD><TD>Items is the list of Deployments.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentstrategy-v1beta1-extensions">DeploymentStrategy v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentspec-v1beta1-extensions">DeploymentSpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatedeployment-v1beta1-extensions">RollingUpdateDeployment</a></I></TD><TD>Rolling update config params. Present only if DeploymentStrategyType = RollingUpdate.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment. Can be &#34;Recreate&#34; or &#34;RollingUpdate&#34;. Default is RollingUpdate.</TD></TR>
</TBODY>
</TABLE>
<H3 id="deploymentrollback-v1beta1-extensions">DeploymentRollback v1beta1 extensions</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Required: This must match the Name of a deployment.</TD></TR>
<TR><TD><CODE>rollbackTo</CODE><BR /><I><a href="#rollbackconfig-v1beta1-extensions">RollbackConfig</a></I></TD><TD>The config of this deployment rollback.</TD></TR>
<TR><TD><CODE>updatedAnnotations</CODE><BR /><I>object</I></TD><TD>The annotations to be updated to a deployment</TD></TR>
</TBODY>
</TABLE>
<H3 id="rollingupdatedeployment-v1beta1-extensions">RollingUpdateDeployment v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentstrategy-v1beta1-extensions">DeploymentStrategy [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxSurge</CODE></TD><TD>The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. By default, a value of 1 is used. Example: when this is set to 30%, the new RC can be scaled up immediately when the rolling update starts, such that the total number of old and new pods do not exceed 130% of desired pods. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is atmost 130% of desired pods.</TD></TR>
<TR><TD><CODE>maxUnavailable</CODE></TD><TD>The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. By default, a fixed value of 1 is used. Example: when this is set to 30%, the old RC can be scaled down to 70% of desired pods immediately when the rolling update starts. Once new pods are ready, old RC can be scaled down further, followed by scaling up the new RC, ensuring that the total number of pods available at all times during the update is at least 70% of desired pods.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-deployment-v1beta1-extensions-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-deployment-v1beta1-extensions">Create</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-create-deployment-v1beta1-extensions" aria-controls="req-kubectl-create-deployment-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-create-deployment-v1beta1-extensions" aria-controls="req-curl-create-deployment-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-create-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.10
ports:
- containerPort: 80
' | kubectl create -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-create-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X POST -H 'Content-Type: application/yaml' --data '
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.10
ports:
- containerPort: 80
' http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/deployments
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-create-deployment-v1beta1-extensions" aria-controls="res-kubectl-create-deployment-v1beta1-extensions"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-create-deployment-v1beta1-extensions" aria-controls="res-curl-create-deployment-v1beta1-extensions"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-create-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" created
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-create-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
"resourceVersion": "2118306",
"generation": 1,
"creationTimestamp": "2016-10-28T01:53:19Z",
"labels": {
"app": "nginx"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {}
}
</CODE></PRE></DIV></DIV></DIV>
<P>create a Deployment</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/extensions/v1beta1/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-deployment-v1beta1-extensions">Patch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-patch-deployment-v1beta1-extensions" aria-controls="req-kubectl-patch-deployment-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-patch-deployment-v1beta1-extensions" aria-controls="req-curl-patch-deployment-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-patch-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl patch deployment deployment-example -p \
'{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.11"}]}}}}'
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-patch-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PATCH -H 'Content-Type: application/strategic-merge-patch+json' --data '
{"spec":{"template":{"spec":{"containers":[{"name":"nginx","image":"nginx:1.11"}]}}}}' \
'http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-patch-deployment-v1beta1-extensions" aria-controls="res-kubectl-patch-deployment-v1beta1-extensions"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-patch-deployment-v1beta1-extensions" aria-controls="res-curl-patch-deployment-v1beta1-extensions"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-patch-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
"deployment-example" patched
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-patch-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "5dc3a8e6-b0ee-11e6-aef0-42010af00229",
"resourceVersion": "164489",
"generation": 11,
"creationTimestamp": "2016-11-22T20:00:50Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "5"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.11",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {
"observedGeneration": 10,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>partially update the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-deployment-v1beta1-extensions">Replace</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-replace-deployment-v1beta1-extensions" aria-controls="req-kubectl-replace-deployment-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-replace-deployment-v1beta1-extensions" aria-controls="req-curl-replace-deployment-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-replace-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ echo 'apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.11
ports:
- containerPort: 80
' | kubectl replace -f -
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-replace-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X PUT -H 'Content-Type: application/yaml' --data '
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: deployment-example
spec:
replicas: 3
revisionHistoryLimit: 10
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:1.11
ports:
- containerPort: 80
' http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/deployments/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-replace-deployment-v1beta1-extensions" aria-controls="res-kubectl-replace-deployment-v1beta1-extensions"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-replace-deployment-v1beta1-extensions" aria-controls="res-curl-replace-deployment-v1beta1-extensions"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-replace-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" replaced
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-replace-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "4ccca349-9cb1-11e6-9c54-42010a800148",
"resourceVersion": "2119082",
"generation": 5,
"creationTimestamp": "2016-10-28T01:53:19Z",
"labels": {
"app": "nginx"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.11",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
},
"revisionHistoryLimit": 10
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>replace the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-deployment-v1beta1-extensions">Delete</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-delete-deployment-v1beta1-extensions" aria-controls="req-kubectl-delete-deployment-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-delete-deployment-v1beta1-extensions" aria-controls="req-curl-delete-deployment-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-delete-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl delete deployment deployment-example
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-delete-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X DELETE -H 'Content-Type: application/yaml' --data '
gracePeriodSeconds: 0
orphanDependents: false
' 'http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-delete-deployment-v1beta1-extensions" aria-controls="res-kubectl-delete-deployment-v1beta1-extensions"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-delete-deployment-v1beta1-extensions" aria-controls="res-curl-delete-deployment-v1beta1-extensions"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-delete-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
deployment "deployment-example" deleted
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-delete-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Success",
"code": 200
}
</CODE></PRE></DIV></DIV></DIV>
<P>delete a Deployment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-deployment-v1beta1-extensions">Delete Collection</H2>
<P>delete collection of Deployment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-deployment-v1beta1-extensions-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-deployment-v1beta1-extensions">Read</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-read-deployment-v1beta1-extensions" aria-controls="req-kubectl-read-deployment-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-read-deployment-v1beta1-extensions" aria-controls="req-curl-read-deployment-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-read-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment deployment-example -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-read-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/deployments/deployment-example
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-read-deployment-v1beta1-extensions" aria-controls="res-kubectl-read-deployment-v1beta1-extensions"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-read-deployment-v1beta1-extensions" aria-controls="res-curl-read-deployment-v1beta1-extensions"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-read-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-read-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>read the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-deployment-v1beta1-extensions">List</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-list-deployment-v1beta1-extensions" aria-controls="req-kubectl-list-deployment-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-list-deployment-v1beta1-extensions" aria-controls="req-curl-list-deployment-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-list-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-list-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/extensions/v1beta1/namespaces/default/deployments'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-list-deployment-v1beta1-extensions" aria-controls="res-kubectl-list-deployment-v1beta1-extensions"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-list-deployment-v1beta1-extensions" aria-controls="res-curl-list-deployment-v1beta1-extensions"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-list-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"kind": "List",
"apiVersion": "v1",
"metadata": {},
"items": [
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "docs",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
"uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
"resourceVersion": "1924126",
"generation": 21,
"creationTimestamp": "2016-10-13T16:06:00Z",
"labels": {
"run": "docs"
},
"annotations": {
"deployment.kubernetes.io/revision": "10",
"replicatingperfection.net/push-image": "true"
}
},
"spec": {
"replicas": 1,
"selector": {
"matchLabels": {
"run": "docs"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"auto-pushed-image-pwittrock/api-docs": "1477496453",
"run": "docs"
}
},
"spec": {
"containers": [
{
"name": "docs",
"image": "pwittrock/api-docs:v9",
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 21,
"replicas": 1,
"updatedReplicas": 1,
"availableReplicas": 1
}
},
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-list-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"kind": "List",
"apiVersion": "v1",
"metadata": {},
"items": [
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "docs",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/docs",
"uid": "ef49e1d2-915e-11e6-be81-42010a80003f",
"resourceVersion": "1924126",
"generation": 21,
"creationTimestamp": "2016-10-13T16:06:00Z",
"labels": {
"run": "docs"
},
"annotations": {
"deployment.kubernetes.io/revision": "10",
"replicatingperfection.net/push-image": "true"
}
},
"spec": {
"replicas": 1,
"selector": {
"matchLabels": {
"run": "docs"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"auto-pushed-image-pwittrock/api-docs": "1477496453",
"run": "docs"
}
},
"spec": {
"containers": [
{
"name": "docs",
"image": "pwittrock/api-docs:v9",
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "Always"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 21,
"replicas": 1,
"updatedReplicas": 1,
"availableReplicas": 1
}
},
{
"kind": "Deployment",
"apiVersion": "app/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/app/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "1b33145a-9c63-11e6-9c54-42010a800148",
"resourceVersion": "2064726",
"generation": 4,
"creationTimestamp": "2016-10-27T16:33:35Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "1"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 4,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
]
}
</CODE></PRE></DIV></DIV></DIV>
<P>list or watch objects of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deploymentlist-v1beta1-extensions">DeploymentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-deployment-v1beta1-extensions">List All Namespaces</H2>
<P>list or watch objects of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/deployments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deploymentlist-v1beta1-extensions">DeploymentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-deployment-v1beta1-extensions">Watch</H2>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-kubectl-watch-deployment-v1beta1-extensions" aria-controls="req-kubectl-watch-deployment-v1beta1-extensions"
aria-expanded="false">kubectl request example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#req-curl-watch-deployment-v1beta1-extensions" aria-controls="req-curl-watch-deployment-v1beta1-extensions"
aria-expanded="false">curl request example</BUTTON>
<DIV class="collapse" id="req-kubectl-watch-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>kubectl</CODE> command</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-shell">
$ kubectl get deployment deployment-example --watch -o json
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="req-curl-watch-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading"><CODE>curl</CODE> command (<I>requires <code>kubectl proxy</code> to be running</I>)</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-shell">
$ kubectl proxy
$ curl -X GET 'http://127.0.0.1:8001/apis/extensions/v1beta1/watch/namespaces/default/deployments/deployment-example'
</CODE></PRE></DIV></DIV></DIV>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-kubectl-watch-deployment-v1beta1-extensions" aria-controls="res-kubectl-watch-deployment-v1beta1-extensions"
aria-expanded="false">kubectl response example</BUTTON>
<BUTTON class="btn btn-info" type="button" data-toggle="collapse"
data-target="#res-curl-watch-deployment-v1beta1-extensions" aria-controls="res-curl-watch-deployment-v1beta1-extensions"
aria-expanded="false">curl response example</BUTTON>
<DIV class="collapse" id="res-kubectl-watch-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Output</DIV>
<DIV class="panel-body">
<PRE class="kubectl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
"resourceVersion": "2128095",
"generation": 2,
"creationTimestamp": "2016-10-28T03:34:12Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "3"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 2,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<DIV class="collapse" id="res-curl-watch-deployment-v1beta1-extensions">
<DIV class="panel panel-default">
<DIV class="panel-heading">Response Body</DIV>
<DIV class="panel-body">
<PRE class="curl"><CODE class="lang-json">
{
"type": "ADDED",
"object": {
"kind": "Deployment",
"apiVersion": "apps/v1beta1",
"metadata": {
"name": "deployment-example",
"namespace": "default",
"selfLink": "/apis/apps/v1beta1/namespaces/default/deployments/deployment-example",
"uid": "64c12290-9cbf-11e6-9c54-42010a800148",
"resourceVersion": "2128095",
"generation": 2,
"creationTimestamp": "2016-10-28T03:34:12Z",
"labels": {
"app": "nginx"
},
"annotations": {
"deployment.kubernetes.io/revision": "3"
}
},
"spec": {
"replicas": 3,
"selector": {
"matchLabels": {
"app": "nginx"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "nginx"
}
},
"spec": {
"containers": [
{
"name": "nginx",
"image": "nginx:1.10",
"ports": [
{
"containerPort": 80,
"protocol": "TCP"
}
],
"resources": {
},
"terminationMessagePath": "/dev/termination-log",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"securityContext": {
}
}
},
"strategy": {
"type": "RollingUpdate",
"rollingUpdate": {
"maxUnavailable": 1,
"maxSurge": 1
}
}
},
"status": {
"observedGeneration": 2,
"replicas": 3,
"updatedReplicas": 3,
"availableReplicas": 3
}
}
}
</CODE></PRE></DIV></DIV></DIV>
<P>watch changes to an object of kind Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/deployments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-deployment-v1beta1-extensions">Watch List</H2>
<P>watch individual changes to a list of Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/deployments</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-deployment-v1beta1-extensions">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/deployments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-deployment-v1beta1-extensions-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-deployment-v1beta1-extensions">Patch Status</H2>
<P>partially update status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-deployment-v1beta1-extensions">Read Status</H2>
<P>read status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-deployment-v1beta1-extensions">Replace Status</H2>
<P>replace status of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Deployment</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#deployment-v1beta1-extensions">Deployment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-deployment-v1beta1-extensions-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-deployment-v1beta1-extensions">Read Scale</H2>
<P>read scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-deployment-v1beta1-extensions">Replace Scale</H2>
<P>replace scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-deployment-v1beta1-extensions">Patch Scale</H2>
<P>partially update scale of the specified Deployment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="rollback-deployment-v1beta1-extensions">Rollback</H2>
<P>create rollback of a Deployment</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/extensions/v1beta1/namespaces/{namespace}/deployments/{name}/rollback</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the DeploymentRollback</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deploymentrollback-v1beta1-extensions">DeploymentRollback</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#deploymentrollback-v1beta1-extensions">DeploymentRollback</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#deploymentrollback-v1beta1-extensions">DeploymentRollback</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#deploymentrollback-v1beta1-extensions">DeploymentRollback</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="deploymentcondition-v1beta2-apps">DeploymentCondition v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>DeploymentCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#deploymentcondition-v1-apps">v1</a>
<a href="#deploymentcondition-v1beta1-apps">v1beta1</a>
<a href="#deploymentcondition-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentstatus-v1beta2-apps">DeploymentStatus [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>lastUpdateTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time this condition was updated.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="deploymentcondition-v1beta1-apps">DeploymentCondition v1beta1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeploymentCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#deploymentcondition-v1-apps">v1</a>
<a href="#deploymentcondition-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentstatus-v1beta1-apps">DeploymentStatus [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>lastUpdateTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time this condition was updated.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="deploymentcondition-v1beta1-extensions">DeploymentCondition v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>DeploymentCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#deploymentcondition-v1-apps">v1</a>
<a href="#deploymentcondition-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentstatus-v1beta1-extensions">DeploymentStatus [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>lastUpdateTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time this condition was updated.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of deployment condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="event-v1beta1-events-k8s-io">Event v1beta1 events.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Event</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#event-v1-core">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#eventlist-v1beta1-events-k8s-io">EventList [events/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>action</CODE><BR /><I>string</I></TD><TD>What action was taken/failed regarding to the regarding object.</TD></TR>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>deprecatedCount</CODE><BR /><I>integer</I></TD><TD>Deprecated field assuring backward compatibility with core.v1 Event type</TD></TR>
<TR><TD><CODE>deprecatedFirstTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Deprecated field assuring backward compatibility with core.v1 Event type</TD></TR>
<TR><TD><CODE>deprecatedLastTimestamp</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Deprecated field assuring backward compatibility with core.v1 Event type</TD></TR>
<TR><TD><CODE>deprecatedSource</CODE><BR /><I><a href="#eventsource-v1-core">EventSource</a></I></TD><TD>Deprecated field assuring backward compatibility with core.v1 Event type</TD></TR>
<TR><TD><CODE>eventTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>Required. Time when this Event was first observed.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>note</CODE><BR /><I>string</I></TD><TD>Optional. A human-readable description of the status of this operation. Maximal length of the note is 1kB, but libraries should be prepared to handle values up to 64kB.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Why the action was taken.</TD></TR>
<TR><TD><CODE>regarding</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>The object this Event is about. In most cases it&#39;s an Object reporting controller implements. E.g. ReplicaSetController implements ReplicaSets and this event is emitted because it acts on some changes in a ReplicaSet object.</TD></TR>
<TR><TD><CODE>related</CODE><BR /><I><a href="#objectreference-v1-core">ObjectReference</a></I></TD><TD>Optional secondary object for more complex actions. E.g. when regarding object triggers a creation or deletion of related object.</TD></TR>
<TR><TD><CODE>reportingController</CODE><BR /><I>string</I></TD><TD>Name of the controller that emitted this Event, e.g. `kubernetes.io/kubelet`.</TD></TR>
<TR><TD><CODE>reportingInstance</CODE><BR /><I>string</I></TD><TD>ID of the controller instance, e.g. `kubelet-xyzf`.</TD></TR>
<TR><TD><CODE>series</CODE><BR /><I><a href="#eventseries-v1beta1-events-k8s-io">EventSeries</a></I></TD><TD>Data about the Event series this event represents or nil if it&#39;s a singleton Event.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of this event (Normal, Warning), new types could be added in the future.</TD></TR>
</TBODY>
</TABLE>
<H3 id="eventlist-v1beta1-events-k8s-io">EventList v1beta1 events</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#event-v1beta1-events-k8s-io">Event</a> array</I></TD><TD>Items is a list of schema objects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-event-v1beta1-events-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-event-v1beta1-events-k8s-io">Create</H2>
<P>create an Event</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-event-v1beta1-events-k8s-io">Patch</H2>
<P>partially update the specified Event</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-event-v1beta1-events-k8s-io">Replace</H2>
<P>replace the specified Event</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-event-v1beta1-events-k8s-io">Delete</H2>
<P>delete an Event</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-event-v1beta1-events-k8s-io">Delete Collection</H2>
<P>delete collection of Event</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-event-v1beta1-events-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-event-v1beta1-events-k8s-io">Read</H2>
<P>read the specified Event</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#event-v1beta1-events-k8s-io">Event</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-event-v1beta1-events-k8s-io">List</H2>
<P>list or watch objects of kind Event</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/events.k8s.io/v1beta1/namespaces/{namespace}/events</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#eventlist-v1beta1-events-k8s-io">EventList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-event-v1beta1-events-k8s-io">List All Namespaces</H2>
<P>list or watch objects of kind Event</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/events.k8s.io/v1beta1/events</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#eventlist-v1beta1-events-k8s-io">EventList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-event-v1beta1-events-k8s-io">Watch</H2>
<P>watch changes to an object of kind Event</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/events.k8s.io/v1beta1/watch/namespaces/{namespace}/events/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Event</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-event-v1beta1-events-k8s-io">Watch List</H2>
<P>watch individual changes to a list of Event</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/events.k8s.io/v1beta1/watch/namespaces/{namespace}/events</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-event-v1beta1-events-k8s-io">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Event</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/events.k8s.io/v1beta1/watch/events</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="eventseries-v1beta1-events-k8s-io">EventSeries v1beta1 events.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>events.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>EventSeries</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#eventseries-v1-core">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#event-v1beta1-events-k8s-io">Event [events/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>count</CODE><BR /><I>integer</I></TD><TD>Number of occurrences in this series up to the last heartbeat time</TD></TR>
<TR><TD><CODE>lastObservedTime</CODE><BR /><I><a href="#microtime-v1-meta">MicroTime</a></I></TD><TD>Time when last Event from the series was seen before last heartbeat.</TD></TR>
<TR><TD><CODE>state</CODE><BR /><I>string</I></TD><TD>Information whether this series is ongoing or finished.</TD></TR>
</TBODY>
</TABLE>
<H1 id="fsgroupstrategyoptions-v1beta1-policy">FSGroupStrategyOptions v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>FSGroupStrategyOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-policy">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of fs groups. If you would like to force a single fs group then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate what FSGroup is used in the SecurityContext.</TD></TR>
</TBODY>
</TABLE>
<H1 id="horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler v2beta1 autoscaling</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>autoscaling</CODE></TD><TD><CODE>v2beta1</CODE></TD><TD><CODE>HorizontalPodAutoscaler</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#horizontalpodautoscaler-v1-autoscaling">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>metadata is the standard object metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#horizontalpodautoscalerspec-v2beta1-autoscaling">HorizontalPodAutoscalerSpec</a></I></TD><TD>spec is the specification for the behaviour of the autoscaler. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus</a></I></TD><TD>status is the current information about the autoscaler.</TD></TR>
</TBODY>
</TABLE>
<H3 id="horizontalpodautoscalerspec-v2beta1-autoscaling">HorizontalPodAutoscalerSpec v2beta1 autoscaling</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>maxReplicas</CODE><BR /><I>integer</I></TD><TD>maxReplicas is the upper limit for the number of replicas to which the autoscaler can scale up. It cannot be less that minReplicas.</TD></TR>
<TR><TD><CODE>metrics</CODE><BR /><I><a href="#metricspec-v2beta1-autoscaling">MetricSpec</a> array</I></TD><TD>metrics contains the specifications for which to use to calculate the desired replica count (the maximum replica count across all metrics will be used). The desired replica count is calculated multiplying the ratio between the target value and the current value by the current number of pods. Ergo, metrics used must decrease as the pod count is increased, and vice-versa. See the individual metric source types for more information about how each type of metric must respond.</TD></TR>
<TR><TD><CODE>minReplicas</CODE><BR /><I>integer</I></TD><TD>minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down. It defaults to 1 pod.</TD></TR>
<TR><TD><CODE>scaleTargetRef</CODE><BR /><I><a href="#crossversionobjectreference-v2beta1-autoscaling">CrossVersionObjectReference</a></I></TD><TD>scaleTargetRef points to the target resource to scale, and is used to the pods for which metrics should be collected, as well as to actually change the replica count.</TD></TR>
</TBODY>
</TABLE>
<H3 id="horizontalpodautoscalerstatus-v2beta1-autoscaling">HorizontalPodAutoscalerStatus v2beta1 autoscaling</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler [autoscaling/v2beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#horizontalpodautoscalercondition-v2beta1-autoscaling">HorizontalPodAutoscalerCondition</a> array</I></TD><TD>conditions is the set of conditions required for this autoscaler to scale its target, and indicates whether or not those conditions are met.</TD></TR>
<TR><TD><CODE>currentMetrics</CODE><BR /><I><a href="#metricstatus-v2beta1-autoscaling">MetricStatus</a> array</I></TD><TD>currentMetrics is the last read state of the metrics used by this autoscaler.</TD></TR>
<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>currentReplicas is current number of replicas of pods managed by this autoscaler, as last seen by the autoscaler.</TD></TR>
<TR><TD><CODE>desiredReplicas</CODE><BR /><I>integer</I></TD><TD>desiredReplicas is the desired number of replicas of pods managed by this autoscaler, as last calculated by the autoscaler.</TD></TR>
<TR><TD><CODE>lastScaleTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>lastScaleTime is the last time the HorizontalPodAutoscaler scaled the number of pods, used by the autoscaler to control how often the number of pods is changed.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>observedGeneration is the most recent generation observed by this autoscaler.</TD></TR>
</TBODY>
</TABLE>
<H3 id="horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList v2beta1 autoscaling</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a> array</I></TD><TD>items is the list of horizontal pod autoscaler objects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>metadata is the standard list metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-horizontalpodautoscaler-v2beta1-autoscaling">Create</H2>
<P>create a HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-horizontalpodautoscaler-v2beta1-autoscaling">Patch</H2>
<P>partially update the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-horizontalpodautoscaler-v2beta1-autoscaling">Replace</H2>
<P>replace the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-horizontalpodautoscaler-v2beta1-autoscaling">Delete</H2>
<P>delete a HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-horizontalpodautoscaler-v2beta1-autoscaling">Delete Collection</H2>
<P>delete collection of HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-horizontalpodautoscaler-v2beta1-autoscaling">Read</H2>
<P>read the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-horizontalpodautoscaler-v2beta1-autoscaling">List</H2>
<P>list or watch objects of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling">List All Namespaces</H2>
<P>list or watch objects of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v2beta1/horizontalpodautoscalers</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscalerlist-v2beta1-autoscaling">HorizontalPodAutoscalerList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-horizontalpodautoscaler-v2beta1-autoscaling">Watch</H2>
<P>watch changes to an object of kind HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v2beta1/watch/namespaces/{namespace}/horizontalpodautoscalers/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-horizontalpodautoscaler-v2beta1-autoscaling">Watch List</H2>
<P>watch individual changes to a list of HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v2beta1/watch/namespaces/{namespace}/horizontalpodautoscalers</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-horizontalpodautoscaler-v2beta1-autoscaling">Watch List All Namespaces</H2>
<P>watch individual changes to a list of HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v2beta1/watch/horizontalpodautoscalers</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-horizontalpodautoscaler-v2beta1-autoscaling-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-horizontalpodautoscaler-v2beta1-autoscaling">Patch Status</H2>
<P>partially update status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-horizontalpodautoscaler-v2beta1-autoscaling">Read Status</H2>
<P>read status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-horizontalpodautoscaler-v2beta1-autoscaling">Replace Status</H2>
<P>replace status of the specified HorizontalPodAutoscaler</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/autoscaling/v2beta1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the HorizontalPodAutoscaler</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#horizontalpodautoscaler-v2beta1-autoscaling">HorizontalPodAutoscaler</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="hostportrange-v1beta1-policy">HostPortRange v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>HostPortRange</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>max</CODE><BR /><I>integer</I></TD><TD>max is the end of the range, inclusive.</TD></TR>
<TR><TD><CODE>min</CODE><BR /><I>integer</I></TD><TD>min is the start of the range, inclusive.</TD></TR>
</TBODY>
</TABLE>
<H1 id="idrange-v1beta1-policy">IDRange v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>IDRange</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#fsgroupstrategyoptions-v1beta1-policy">FSGroupStrategyOptions [policy/v1beta1]</a></LI>
<LI><a href="#runasuserstrategyoptions-v1beta1-policy">RunAsUserStrategyOptions [policy/v1beta1]</a></LI>
<LI><a href="#supplementalgroupsstrategyoptions-v1beta1-policy">SupplementalGroupsStrategyOptions [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>max</CODE><BR /><I>integer</I></TD><TD>max is the end of the range, inclusive.</TD></TR>
<TR><TD><CODE>min</CODE><BR /><I>integer</I></TD><TD>min is the start of the range, inclusive.</TD></TR>
</TBODY>
</TABLE>
<H1 id="ipblock-v1beta1-extensions">IPBlock v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>IPBlock</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#ipblock-v1-networking-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicypeer-v1beta1-extensions">NetworkPolicyPeer [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>cidr</CODE><BR /><I>string</I></TD><TD>CIDR is a string representing the IP Block Valid examples are &#34;192.168.1.1/24&#34;</TD></TR>
<TR><TD><CODE>except</CODE><BR /><I>string array</I></TD><TD>Except is a slice of CIDRs that should not be included within an IP Block Valid examples are &#34;192.168.1.1/24&#34; Except values will be rejected if they are outside the CIDR range</TD></TR>
</TBODY>
</TABLE>
<H1 id="initializer-v1alpha1-admissionregistration-k8s-io">Initializer v1alpha1 admissionregistration.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>Initializer</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#initializer-v1-meta">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#initializerconfiguration-v1alpha1-admissionregistration-k8s-io">InitializerConfiguration [admissionregistration/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the identifier of the initializer. It will be added to the object that needs to be initialized. Name should be fully qualified, e.g., alwayspullimages.kubernetes.io, where &#34;alwayspullimages&#34; is the name of the webhook, and kubernetes.io is the name of the organization. Required</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#rule-v1alpha1-admissionregistration-k8s-io">Rule</a> array</I></TD><TD>Rules describes what resources/subresources the initializer cares about. The initializer cares about an operation if it matches _any_ Rule. Rule.Resources must not include subresources.</TD></TR>
</TBODY>
</TABLE>
<H1 id="jobtemplatespec-v2alpha1-batch">JobTemplateSpec v2alpha1 batch</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>batch</CODE></TD><TD><CODE>v2alpha1</CODE></TD><TD><CODE>JobTemplateSpec</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#jobtemplatespec-v1beta1-batch">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#cronjobspec-v2alpha1-batch">CronJobSpec [batch/v2alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata of the jobs created from this template. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#jobspec-v1-batch">JobSpec</a></I></TD><TD>Specification of the desired behavior of the job. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H1 id="localsubjectaccessreview-v1beta1-authorization-k8s-io">LocalSubjectAccessReview v1beta1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>LocalSubjectAccessReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#localsubjectaccessreview-v1-authorization-k8s-io">v1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#subjectaccessreviewspec-v1beta1-authorization-k8s-io">SubjectAccessReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated. spec.namespace must be equal to the namespace you made the request against. If empty, it is defaulted.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectaccessreviewstatus-v1beta1-authorization-k8s-io">SubjectAccessReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request is allowed or not</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-localsubjectaccessreview-v1beta1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-localsubjectaccessreview-v1beta1-authorization-k8s-io">Create</H2>
<P>create a LocalSubjectAccessReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authorization.k8s.io/v1beta1/namespaces/{namespace}/localsubjectaccessreviews</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#localsubjectaccessreview-v1beta1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#localsubjectaccessreview-v1beta1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#localsubjectaccessreview-v1beta1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#localsubjectaccessreview-v1beta1-authorization-k8s-io">LocalSubjectAccessReview</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="networkpolicy-v1beta1-extensions">NetworkPolicy v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>NetworkPolicy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicy-v1-networking-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicylist-v1beta1-extensions">NetworkPolicyList [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#networkpolicyspec-v1beta1-extensions">NetworkPolicySpec</a></I></TD><TD>Specification of the desired behavior for this NetworkPolicy.</TD></TR>
</TBODY>
</TABLE>
<H3 id="networkpolicyspec-v1beta1-extensions">NetworkPolicySpec v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>egress</CODE><BR /><I><a href="#networkpolicyegressrule-v1beta1-extensions">NetworkPolicyEgressRule</a> array</I></TD><TD>List of egress rules to be applied to the selected pods. Outgoing traffic is allowed if there are no NetworkPolicies selecting the pod (and cluster policy otherwise allows the traffic), OR if the traffic matches at least one egress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy limits all outgoing traffic (and serves solely to ensure that the pods it selects are isolated by default). This field is beta-level in 1.8</TD></TR>
<TR><TD><CODE>ingress</CODE><BR /><I><a href="#networkpolicyingressrule-v1beta1-extensions">NetworkPolicyIngressRule</a> array</I></TD><TD>List of ingress rules to be applied to the selected pods. Traffic is allowed to a pod if there are no NetworkPolicies selecting the pod OR if the traffic source is the pod&#39;s local node, OR if the traffic matches at least one ingress rule across all of the NetworkPolicy objects whose podSelector matches the pod. If this field is empty then this NetworkPolicy does not allow any traffic (and serves solely to ensure that the pods it selects are isolated by default).</TD></TR>
<TR><TD><CODE>podSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selects the pods to which this NetworkPolicy object applies. The array of ingress rules is applied to any pods selected by this field. Multiple network policies can select the same set of pods. In this case, the ingress rules for each are combined additively. This field is NOT optional and follows standard label selector semantics. An empty podSelector matches all pods in this namespace.</TD></TR>
<TR><TD><CODE>policyTypes</CODE><BR /><I>string array</I></TD><TD>List of rule types that the NetworkPolicy relates to. Valid options are Ingress, Egress, or Ingress,Egress. If this field is not specified, it will default based on the existence of Ingress or Egress rules; policies that contain an Egress section are assumed to affect Egress, and all policies (whether or not they contain an Ingress section) are assumed to affect Ingress. If you want to write an egress-only policy, you must explicitly specify policyTypes [ &#34;Egress&#34; ]. Likewise, if you want to write a policy that specifies that no egress is allowed, you must specify a policyTypes value that include &#34;Egress&#34; (since such a policy would not include an Egress section and would otherwise default to just [ &#34;Ingress&#34; ]). This field is beta-level in 1.8</TD></TR>
</TBODY>
</TABLE>
<H3 id="networkpolicylist-v1beta1-extensions">NetworkPolicyList v1beta1 extensions</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a> array</I></TD><TD>Items is a list of schema objects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-networkpolicy-v1beta1-extensions-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-networkpolicy-v1beta1-extensions">Create</H2>
<P>create a NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-networkpolicy-v1beta1-extensions">Patch</H2>
<P>partially update the specified NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-networkpolicy-v1beta1-extensions">Replace</H2>
<P>replace the specified NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-networkpolicy-v1beta1-extensions">Delete</H2>
<P>delete a NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-networkpolicy-v1beta1-extensions">Delete Collection</H2>
<P>delete collection of NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-networkpolicy-v1beta1-extensions-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-networkpolicy-v1beta1-extensions">Read</H2>
<P>read the specified NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicy-v1beta1-extensions">NetworkPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-networkpolicy-v1beta1-extensions">List</H2>
<P>list or watch objects of kind NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/networkpolicies</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicylist-v1beta1-extensions">NetworkPolicyList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-networkpolicy-v1beta1-extensions">List All Namespaces</H2>
<P>list or watch objects of kind NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/networkpolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#networkpolicylist-v1beta1-extensions">NetworkPolicyList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-networkpolicy-v1beta1-extensions">Watch</H2>
<P>watch changes to an object of kind NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/networkpolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the NetworkPolicy</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-networkpolicy-v1beta1-extensions">Watch List</H2>
<P>watch individual changes to a list of NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/networkpolicies</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-networkpolicy-v1beta1-extensions">Watch List All Namespaces</H2>
<P>watch individual changes to a list of NetworkPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/networkpolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="networkpolicyegressrule-v1beta1-extensions">NetworkPolicyEgressRule v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>NetworkPolicyEgressRule</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicyegressrule-v1-networking-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicyspec-v1beta1-extensions">NetworkPolicySpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ports</CODE><BR /><I><a href="#networkpolicyport-v1beta1-extensions">NetworkPolicyPort</a> array</I></TD><TD>List of destination ports for outgoing traffic. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.</TD></TR>
<TR><TD><CODE>to</CODE><BR /><I><a href="#networkpolicypeer-v1beta1-extensions">NetworkPolicyPeer</a> array</I></TD><TD>List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.</TD></TR>
</TBODY>
</TABLE>
<H1 id="networkpolicyingressrule-v1beta1-extensions">NetworkPolicyIngressRule v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>NetworkPolicyIngressRule</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicyingressrule-v1-networking-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicyspec-v1beta1-extensions">NetworkPolicySpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>from</CODE><BR /><I><a href="#networkpolicypeer-v1beta1-extensions">NetworkPolicyPeer</a> array</I></TD><TD>List of sources which should be able to access the pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all sources (traffic not restricted by source). If this field is present and contains at least on item, this rule allows traffic only if the traffic matches at least one item in the from list.</TD></TR>
<TR><TD><CODE>ports</CODE><BR /><I><a href="#networkpolicyport-v1beta1-extensions">NetworkPolicyPort</a> array</I></TD><TD>List of ports which should be made accessible on the pods selected for this rule. Each item in this list is combined using a logical OR. If this field is empty or missing, this rule matches all ports (traffic not restricted by port). If this field is present and contains at least one item, then this rule allows traffic only if the traffic matches at least one port in the list.</TD></TR>
</TBODY>
</TABLE>
<H1 id="networkpolicypeer-v1beta1-extensions">NetworkPolicyPeer v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>NetworkPolicyPeer</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicypeer-v1-networking-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicyegressrule-v1beta1-extensions">NetworkPolicyEgressRule [extensions/v1beta1]</a></LI>
<LI><a href="#networkpolicyingressrule-v1beta1-extensions">NetworkPolicyIngressRule [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ipBlock</CODE><BR /><I><a href="#ipblock-v1beta1-extensions">IPBlock</a></I></TD><TD>IPBlock defines policy on a particular IPBlock. If this field is set then neither of the other fields can be.</TD></TR>
<TR><TD><CODE>namespaceSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selects Namespaces using cluster-scoped labels. This field follows standard label selector semantics; if present but empty, it selects all namespaces. If PodSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects all Pods in the Namespaces selected by NamespaceSelector.</TD></TR>
<TR><TD><CODE>podSelector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>This is a label selector which selects Pods. This field follows standard label selector semantics; if present but empty, it selects all pods. If NamespaceSelector is also set, then the NetworkPolicyPeer as a whole selects the Pods matching PodSelector in the Namespaces selected by NamespaceSelector. Otherwise it selects the Pods matching PodSelector in the policy&#39;s own Namespace.</TD></TR>
</TBODY>
</TABLE>
<H1 id="networkpolicyport-v1beta1-extensions">NetworkPolicyPort v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>NetworkPolicyPort</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#networkpolicyport-v1-networking-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#networkpolicyegressrule-v1beta1-extensions">NetworkPolicyEgressRule [extensions/v1beta1]</a></LI>
<LI><a href="#networkpolicyingressrule-v1beta1-extensions">NetworkPolicyIngressRule [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>port</CODE></TD><TD>If specified, the port on the given protocol. This can either be a numerical or named port on a pod. If this field is not provided, this matches all port names and numbers. If present, only traffic on the specified protocol AND port will be matched.</TD></TR>
<TR><TD><CODE>protocol</CODE><BR /><I>string</I></TD><TD>Optional. The protocol (TCP or UDP) which traffic must match. If not specified, this field defaults to TCP.</TD></TR>
</TBODY>
</TABLE>
<H1 id="nonresourceattributes-v1beta1-authorization-k8s-io">NonResourceAttributes v1beta1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>NonResourceAttributes</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#nonresourceattributes-v1-authorization-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectaccessreviewspec-v1beta1-authorization-k8s-io">SelfSubjectAccessReviewSpec [authorization/v1beta1]</a></LI>
<LI><a href="#subjectaccessreviewspec-v1beta1-authorization-k8s-io">SubjectAccessReviewSpec [authorization/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>Path is the URL path of the request</TD></TR>
<TR><TD><CODE>verb</CODE><BR /><I>string</I></TD><TD>Verb is the standard HTTP verb</TD></TR>
</TBODY>
</TABLE>
<H1 id="nonresourcerule-v1beta1-authorization-k8s-io">NonResourceRule v1beta1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>NonResourceRule</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#nonresourcerule-v1-authorization-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#subjectrulesreviewstatus-v1beta1-authorization-k8s-io">SubjectRulesReviewStatus [authorization/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>nonResourceURLs</CODE><BR /><I>string array</I></TD><TD>NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verb is a list of kubernetes non-resource API verbs, like: get, post, put, delete, patch, head, options. &#34;*&#34; means all.</TD></TR>
</TBODY>
</TABLE>
<H1 id="podsecuritypolicy-v1beta1-policy">PodSecurityPolicy v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PodSecurityPolicy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicylist-v1beta1-policy">PodSecurityPolicyList [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec</a></I></TD><TD>spec defines the policy enforced.</TD></TR>
</TBODY>
</TABLE>
<H3 id="podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec v1beta1 policy</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowPrivilegeEscalation</CODE><BR /><I>boolean</I></TD><TD>allowPrivilegeEscalation determines if a pod can request to allow privilege escalation. If unspecified, defaults to true.</TD></TR>
<TR><TD><CODE>allowedCapabilities</CODE><BR /><I>string array</I></TD><TD>allowedCapabilities is a list of capabilities that can be requested to add to the container. Capabilities in this field may be added at the pod author&#39;s discretion. You must not list a capability in both allowedCapabilities and requiredDropCapabilities.</TD></TR>
<TR><TD><CODE>allowedFlexVolumes</CODE><BR /><I><a href="#allowedflexvolume-v1beta1-policy">AllowedFlexVolume</a> array</I></TD><TD>allowedFlexVolumes is a whitelist of allowed Flexvolumes. Empty or nil indicates that all Flexvolumes may be used. This parameter is effective only when the usage of the Flexvolumes is allowed in the &#34;volumes&#34; field.</TD></TR>
<TR><TD><CODE>allowedHostPaths</CODE><BR /><I><a href="#allowedhostpath-v1beta1-policy">AllowedHostPath</a> array</I></TD><TD>allowedHostPaths is a white list of allowed host paths. Empty indicates that all host paths may be used.</TD></TR>
<TR><TD><CODE>allowedUnsafeSysctls</CODE><BR /><I>string array</I></TD><TD>allowedUnsafeSysctls is a list of explicitly allowed unsafe sysctls, defaults to none. Each entry is either a plain sysctl name or ends in &#34;*&#34; in which case it is considered as a prefix of allowed sysctls. Single * means all unsafe sysctls are allowed. Kubelet has to whitelist all allowed unsafe sysctls explicitly to avoid rejection. Examples: e.g. &#34;foo/*&#34; allows &#34;foo/bar&#34;, &#34;foo/baz&#34;, etc. e.g. &#34;foo.*&#34; allows &#34;foo.bar&#34;, &#34;foo.baz&#34;, etc.</TD></TR>
<TR><TD><CODE>defaultAddCapabilities</CODE><BR /><I>string array</I></TD><TD>defaultAddCapabilities is the default set of capabilities that will be added to the container unless the pod spec specifically drops the capability. You may not list a capability in both defaultAddCapabilities and requiredDropCapabilities. Capabilities added here are implicitly allowed, and need not be included in the allowedCapabilities list.</TD></TR>
<TR><TD><CODE>defaultAllowPrivilegeEscalation</CODE><BR /><I>boolean</I></TD><TD>defaultAllowPrivilegeEscalation controls the default setting for whether a process can gain more privileges than its parent process.</TD></TR>
<TR><TD><CODE>forbiddenSysctls</CODE><BR /><I>string array</I></TD><TD>forbiddenSysctls is a list of explicitly forbidden sysctls, defaults to none. Each entry is either a plain sysctl name or ends in &#34;*&#34; in which case it is considered as a prefix of forbidden sysctls. Single * means all sysctls are forbidden. Examples: e.g. &#34;foo/*&#34; forbids &#34;foo/bar&#34;, &#34;foo/baz&#34;, etc. e.g. &#34;foo.*&#34; forbids &#34;foo.bar&#34;, &#34;foo.baz&#34;, etc.</TD></TR>
<TR><TD><CODE>fsGroup</CODE><BR /><I><a href="#fsgroupstrategyoptions-v1beta1-policy">FSGroupStrategyOptions</a></I></TD><TD>fsGroup is the strategy that will dictate what fs group is used by the SecurityContext.</TD></TR>
<TR><TD><CODE>hostIPC</CODE><BR /><I>boolean</I></TD><TD>hostIPC determines if the policy allows the use of HostIPC in the pod spec.</TD></TR>
<TR><TD><CODE>hostNetwork</CODE><BR /><I>boolean</I></TD><TD>hostNetwork determines if the policy allows the use of HostNetwork in the pod spec.</TD></TR>
<TR><TD><CODE>hostPID</CODE><BR /><I>boolean</I></TD><TD>hostPID determines if the policy allows the use of HostPID in the pod spec.</TD></TR>
<TR><TD><CODE>hostPorts</CODE><BR /><I><a href="#hostportrange-v1beta1-policy">HostPortRange</a> array</I></TD><TD>hostPorts determines which host port ranges are allowed to be exposed.</TD></TR>
<TR><TD><CODE>privileged</CODE><BR /><I>boolean</I></TD><TD>privileged determines if a pod can request to be run as privileged.</TD></TR>
<TR><TD><CODE>readOnlyRootFilesystem</CODE><BR /><I>boolean</I></TD><TD>readOnlyRootFilesystem when set to true will force containers to run with a read only root file system. If the container specifically requests to run with a non-read only root file system the PSP should deny the pod. If set to false the container may run with a read only root file system if it wishes but it will not be forced to.</TD></TR>
<TR><TD><CODE>requiredDropCapabilities</CODE><BR /><I>string array</I></TD><TD>requiredDropCapabilities are the capabilities that will be dropped from the container. These are required to be dropped and cannot be added.</TD></TR>
<TR><TD><CODE>runAsUser</CODE><BR /><I><a href="#runasuserstrategyoptions-v1beta1-policy">RunAsUserStrategyOptions</a></I></TD><TD>runAsUser is the strategy that will dictate the allowable RunAsUser values that may be set.</TD></TR>
<TR><TD><CODE>seLinux</CODE><BR /><I><a href="#selinuxstrategyoptions-v1beta1-policy">SELinuxStrategyOptions</a></I></TD><TD>seLinux is the strategy that will dictate the allowable labels that may be set.</TD></TR>
<TR><TD><CODE>supplementalGroups</CODE><BR /><I><a href="#supplementalgroupsstrategyoptions-v1beta1-policy">SupplementalGroupsStrategyOptions</a></I></TD><TD>supplementalGroups is the strategy that will dictate what supplemental groups are used by the SecurityContext.</TD></TR>
<TR><TD><CODE>volumes</CODE><BR /><I>string array</I></TD><TD>volumes is a white list of allowed volume plugins. Empty indicates that no volumes may be used. To allow all volumes you may use &#39;\*&#39;.</TD></TR>
</TBODY>
</TABLE>
<H3 id="podsecuritypolicylist-v1beta1-policy">PodSecurityPolicyList v1beta1 policy</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a> array</I></TD><TD>items is a list of schema objects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-podsecuritypolicy-v1beta1-policy-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-podsecuritypolicy-v1beta1-policy">Create</H2>
<P>create a PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/policy/v1beta1/podsecuritypolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-podsecuritypolicy-v1beta1-policy">Patch</H2>
<P>partially update the specified PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/policy/v1beta1/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-podsecuritypolicy-v1beta1-policy">Replace</H2>
<P>replace the specified PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/policy/v1beta1/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-podsecuritypolicy-v1beta1-policy">Delete</H2>
<P>delete a PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/policy/v1beta1/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-podsecuritypolicy-v1beta1-policy">Delete Collection</H2>
<P>delete collection of PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/policy/v1beta1/podsecuritypolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-podsecuritypolicy-v1beta1-policy-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-podsecuritypolicy-v1beta1-policy">Read</H2>
<P>read the specified PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podsecuritypolicy-v1beta1-policy">PodSecurityPolicy</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-podsecuritypolicy-v1beta1-policy">List</H2>
<P>list or watch objects of kind PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/podsecuritypolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#podsecuritypolicylist-v1beta1-policy">PodSecurityPolicyList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-podsecuritypolicy-v1beta1-policy">Watch</H2>
<P>watch changes to an object of kind PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/watch/podsecuritypolicies/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PodSecurityPolicy</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-podsecuritypolicy-v1beta1-policy">Watch List</H2>
<P>watch individual changes to a list of PodSecurityPolicy</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/policy/v1beta1/watch/podsecuritypolicies</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="policyrule-v1beta1-rbac-authorization-k8s-io">PolicyRule v1beta1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>PolicyRule</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#policyrule-v1-rbac-authorization-k8s-io">v1</a>
<a href="#policyrule-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrole-v1beta1-rbac-authorization-k8s-io">ClusterRole [rbac/v1beta1]</a></LI>
<LI><a href="#role-v1beta1-rbac-authorization-k8s-io">Role [rbac/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.</TD></TR>
<TR><TD><CODE>nonResourceURLs</CODE><BR /><I>string array</I></TD><TD>NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as &#34;pods&#34; or &#34;secrets&#34;) or non-resource URL paths (such as &#34;/api&#34;), but not both.</TD></TR>
<TR><TD><CODE>resourceNames</CODE><BR /><I>string array</I></TD><TD>ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to. &#39;\*&#39; represents all resources in the specified apiGroups. &#39;\*/foo&#39; represents the subresource &#39;foo&#39; for all resources in the specified apiGroups.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verbs is a list of Verbs that apply to ALL the ResourceKinds and AttributeRestrictions contained in this rule. VerbAll represents all kinds.</TD></TR>
</TBODY>
</TABLE>
<H1 id="policyrule-v1alpha1-rbac-authorization-k8s-io">PolicyRule v1alpha1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>PolicyRule</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#policyrule-v1-rbac-authorization-k8s-io">v1</a>
<a href="#policyrule-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrole-v1alpha1-rbac-authorization-k8s-io">ClusterRole [rbac/v1alpha1]</a></LI>
<LI><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role [rbac/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed.</TD></TR>
<TR><TD><CODE>nonResourceURLs</CODE><BR /><I>string array</I></TD><TD>NonResourceURLs is a set of partial urls that a user should have access to. *s are allowed, but only as the full, final step in the path This name is intentionally different than the internal type so that the DefaultConvert works nicely and because the ordering may be different. Since non-resource URLs are not namespaced, this field is only applicable for ClusterRoles referenced from a ClusterRoleBinding. Rules can either apply to API resources (such as &#34;pods&#34; or &#34;secrets&#34;) or non-resource URL paths (such as &#34;/api&#34;), but not both.</TD></TR>
<TR><TD><CODE>resourceNames</CODE><BR /><I>string array</I></TD><TD>ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to. ResourceAll represents all resources.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verbs is a list of Verbs that apply to ALL the ResourceKinds and AttributeRestrictions contained in this rule. VerbAll represents all kinds.</TD></TR>
</TBODY>
</TABLE>
<H1 id="priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass v1alpha1 scheduling.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>scheduling.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>PriorityClass</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#priorityclass-v1beta1-scheduling-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#priorityclasslist-v1alpha1-scheduling-k8s-io">PriorityClassList [scheduling/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>description</CODE><BR /><I>string</I></TD><TD>description is an arbitrary string that usually provides guidelines on when this priority class should be used.</TD></TR>
<TR><TD><CODE>globalDefault</CODE><BR /><I>boolean</I></TD><TD>globalDefault specifies whether this PriorityClass should be considered as the default priority for pods that do not have any priority class. Only one PriorityClass can be marked as `globalDefault`. However, if more than one PriorityClasses exists with their `globalDefault` field set to true, the smallest value of such global default PriorityClasses will be used as the default priority.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>value</CODE><BR /><I>integer</I></TD><TD>The value of this priority class. This is the actual priority that pods receive when they have the name of this class in their pod spec.</TD></TR>
</TBODY>
</TABLE>
<H3 id="priorityclasslist-v1alpha1-scheduling-k8s-io">PriorityClassList v1alpha1 scheduling</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a> array</I></TD><TD>items is the list of PriorityClasses</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-priorityclass-v1alpha1-scheduling-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-priorityclass-v1alpha1-scheduling-k8s-io">Create</H2>
<P>create a PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/scheduling.k8s.io/v1alpha1/priorityclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-priorityclass-v1alpha1-scheduling-k8s-io">Patch</H2>
<P>partially update the specified PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/scheduling.k8s.io/v1alpha1/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-priorityclass-v1alpha1-scheduling-k8s-io">Replace</H2>
<P>replace the specified PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/scheduling.k8s.io/v1alpha1/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-priorityclass-v1alpha1-scheduling-k8s-io">Delete</H2>
<P>delete a PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/scheduling.k8s.io/v1alpha1/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-priorityclass-v1alpha1-scheduling-k8s-io">Delete Collection</H2>
<P>delete collection of PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/scheduling.k8s.io/v1alpha1/priorityclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-priorityclass-v1alpha1-scheduling-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-priorityclass-v1alpha1-scheduling-k8s-io">Read</H2>
<P>read the specified PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/scheduling.k8s.io/v1alpha1/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#priorityclass-v1alpha1-scheduling-k8s-io">PriorityClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-priorityclass-v1alpha1-scheduling-k8s-io">List</H2>
<P>list or watch objects of kind PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/scheduling.k8s.io/v1alpha1/priorityclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#priorityclasslist-v1alpha1-scheduling-k8s-io">PriorityClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-priorityclass-v1alpha1-scheduling-k8s-io">Watch</H2>
<P>watch changes to an object of kind PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/scheduling.k8s.io/v1alpha1/watch/priorityclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the PriorityClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-priorityclass-v1alpha1-scheduling-k8s-io">Watch List</H2>
<P>watch individual changes to a list of PriorityClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/scheduling.k8s.io/v1alpha1/watch/priorityclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="replicaset-v1beta2-apps">ReplicaSet v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>ReplicaSet</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#replicaset-v1-apps">v1</a>
<a href="#replicaset-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicasetlist-v1beta2-apps">ReplicaSetList [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>If the Labels of a ReplicaSet are empty, they are defaulted to be the same as the Pod(s) that the ReplicaSet manages. Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#replicasetspec-v1beta2-apps">ReplicaSetSpec</a></I></TD><TD>Spec defines the specification of the desired behavior of the ReplicaSet. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#replicasetstatus-v1beta2-apps">ReplicaSetStatus</a></I></TD><TD>Status is the most recently observed status of the ReplicaSet. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicasetspec-v1beta2-apps">ReplicaSetSpec v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicaset-v1beta2-apps">ReplicaSet [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selector is a label query over pods that should match the replica count. Label keys and values that must match in order to be controlled by this replica set. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template is the object that describes the pod that will be created if insufficient replicas are detected. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicasetstatus-v1beta2-apps">ReplicaSetStatus v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicaset-v1beta2-apps">ReplicaSet [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>The number of available replicas (ready for at least minReadySeconds) for this replica set.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#replicasetcondition-v1beta2-apps">ReplicaSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a replica set&#39;s current state.</TD></TR>
<TR><TD><CODE>fullyLabeledReplicas</CODE><BR /><I>integer</I></TD><TD>The number of pods that have labels matching the labels of the pod template of the replicaset.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>ObservedGeneration reflects the generation of the most recently observed ReplicaSet.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>The number of ready replicas for this replica set.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicasetlist-v1beta2-apps">ReplicaSetList v1beta2 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a> array</I></TD><TD>List of ReplicaSets. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-replicaset-v1beta2-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-replicaset-v1beta2-apps">Create</H2>
<P>create a ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1beta2/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-replicaset-v1beta2-apps">Patch</H2>
<P>partially update the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-replicaset-v1beta2-apps">Replace</H2>
<P>replace the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-replicaset-v1beta2-apps">Delete</H2>
<P>delete a ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-replicaset-v1beta2-apps">Delete Collection</H2>
<P>delete collection of ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-replicaset-v1beta2-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-replicaset-v1beta2-apps">Read</H2>
<P>read the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-replicaset-v1beta2-apps">List</H2>
<P>list or watch objects of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicasetlist-v1beta2-apps">ReplicaSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-replicaset-v1beta2-apps">List All Namespaces</H2>
<P>list or watch objects of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/replicasets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicasetlist-v1beta2-apps">ReplicaSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-replicaset-v1beta2-apps">Watch</H2>
<P>watch changes to an object of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-replicaset-v1beta2-apps">Watch List</H2>
<P>watch individual changes to a list of ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-replicaset-v1beta2-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/replicasets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-replicaset-v1beta2-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-replicaset-v1beta2-apps">Patch Status</H2>
<P>partially update status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-replicaset-v1beta2-apps">Read Status</H2>
<P>read status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-replicaset-v1beta2-apps">Replace Status</H2>
<P>replace status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicaset-v1beta2-apps">ReplicaSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-replicaset-v1beta2-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-replicaset-v1beta2-apps">Read Scale</H2>
<P>read scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-replicaset-v1beta2-apps">Replace Scale</H2>
<P>replace scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-replicaset-v1beta2-apps">Patch Scale</H2>
<P>partially update scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/replicasets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="replicaset-v1beta1-extensions">ReplicaSet v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ReplicaSet</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#replicaset-v1-apps">v1</a>
<a href="#replicaset-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicasetlist-v1beta1-extensions">ReplicaSetList [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>If the Labels of a ReplicaSet are empty, they are defaulted to be the same as the Pod(s) that the ReplicaSet manages. Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#replicasetspec-v1beta1-extensions">ReplicaSetSpec</a></I></TD><TD>Spec defines the specification of the desired behavior of the ReplicaSet. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#replicasetstatus-v1beta1-extensions">ReplicaSetStatus</a></I></TD><TD>Status is the most recently observed status of the ReplicaSet. This data may be out of date by some window of time. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicasetspec-v1beta1-extensions">ReplicaSetSpec v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicaset-v1beta1-extensions">ReplicaSet [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>minReadySeconds</CODE><BR /><I>integer</I></TD><TD>Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the number of desired replicas. This is a pointer to distinguish between explicit zero and unspecified. Defaults to 1. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>Selector is a label query over pods that should match the replica count. If the selector is empty, it is defaulted to the labels present on the pod template. Label keys and values that must match in order to be controlled by this replica set. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>Template is the object that describes the pod that will be created if insufficient replicas are detected. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller#pod-template</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicasetstatus-v1beta1-extensions">ReplicaSetStatus v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicaset-v1beta1-extensions">ReplicaSet [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>availableReplicas</CODE><BR /><I>integer</I></TD><TD>The number of available replicas (ready for at least minReadySeconds) for this replica set.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#replicasetcondition-v1beta1-extensions">ReplicaSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a replica set&#39;s current state.</TD></TR>
<TR><TD><CODE>fullyLabeledReplicas</CODE><BR /><I>integer</I></TD><TD>The number of pods that have labels matching the labels of the pod template of the replicaset.</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>ObservedGeneration reflects the generation of the most recently observed ReplicaSet.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>The number of ready replicas for this replica set.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>Replicas is the most recently oberved number of replicas. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller</TD></TR>
</TBODY>
</TABLE>
<H3 id="replicasetlist-v1beta1-extensions">ReplicaSetList v1beta1 extensions</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a> array</I></TD><TD>List of ReplicaSets. More info: https://kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-replicaset-v1beta1-extensions-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-replicaset-v1beta1-extensions">Create</H2>
<P>create a ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/extensions/v1beta1/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-replicaset-v1beta1-extensions">Patch</H2>
<P>partially update the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-replicaset-v1beta1-extensions">Replace</H2>
<P>replace the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-replicaset-v1beta1-extensions">Delete</H2>
<P>delete a ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-replicaset-v1beta1-extensions">Delete Collection</H2>
<P>delete collection of ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/extensions/v1beta1/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-replicaset-v1beta1-extensions-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-replicaset-v1beta1-extensions">Read</H2>
<P>read the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-replicaset-v1beta1-extensions">List</H2>
<P>list or watch objects of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicasetlist-v1beta1-extensions">ReplicaSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-replicaset-v1beta1-extensions">List All Namespaces</H2>
<P>list or watch objects of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/replicasets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicasetlist-v1beta1-extensions">ReplicaSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-replicaset-v1beta1-extensions">Watch</H2>
<P>watch changes to an object of kind ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/replicasets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-replicaset-v1beta1-extensions">Watch List</H2>
<P>watch individual changes to a list of ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/namespaces/{namespace}/replicasets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-replicaset-v1beta1-extensions">Watch List All Namespaces</H2>
<P>watch individual changes to a list of ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/watch/replicasets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-replicaset-v1beta1-extensions-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-replicaset-v1beta1-extensions">Patch Status</H2>
<P>partially update status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-replicaset-v1beta1-extensions">Read Status</H2>
<P>read status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-replicaset-v1beta1-extensions">Replace Status</H2>
<P>replace status of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the ReplicaSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#replicaset-v1beta1-extensions">ReplicaSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-replicaset-v1beta1-extensions-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-replicaset-v1beta1-extensions">Read Scale</H2>
<P>read scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-replicaset-v1beta1-extensions">Replace Scale</H2>
<P>replace scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-replicaset-v1beta1-extensions">Patch Scale</H2>
<P>partially update scale of the specified ReplicaSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/extensions/v1beta1/namespaces/{namespace}/replicasets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-extensions">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="replicasetcondition-v1beta2-apps">ReplicaSetCondition v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>ReplicaSetCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#replicasetcondition-v1-apps">v1</a>
<a href="#replicasetcondition-v1beta1-extensions">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicasetstatus-v1beta2-apps">ReplicaSetStatus [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of replica set condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="replicasetcondition-v1beta1-extensions">ReplicaSetCondition v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ReplicaSetCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#replicasetcondition-v1-apps">v1</a>
<a href="#replicasetcondition-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#replicasetstatus-v1beta1-extensions">ReplicaSetStatus [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>The last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of replica set condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="resourceattributes-v1beta1-authorization-k8s-io">ResourceAttributes v1beta1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ResourceAttributes</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#resourceattributes-v1-authorization-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectaccessreviewspec-v1beta1-authorization-k8s-io">SelfSubjectAccessReviewSpec [authorization/v1beta1]</a></LI>
<LI><a href="#subjectaccessreviewspec-v1beta1-authorization-k8s-io">SubjectAccessReviewSpec [authorization/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>group</CODE><BR /><I>string</I></TD><TD>Group is the API Group of the Resource. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the resource being requested for a &#34;get&#34; or deleted for a &#34;delete&#34;. &#34;&#34; (empty) means all.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of the action being requested. Currently, there is no distinction between no namespace and all namespaces &#34;&#34; (empty) is defaulted for LocalSubjectAccessReviews &#34;&#34; (empty) is empty for cluster-scoped resources &#34;&#34; (empty) means &#34;all&#34; for namespace scoped resources from a SubjectAccessReview or SelfSubjectAccessReview</TD></TR>
<TR><TD><CODE>resource</CODE><BR /><I>string</I></TD><TD>Resource is one of the existing resource types. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>subresource</CODE><BR /><I>string</I></TD><TD>Subresource is one of the existing resource types. &#34;&#34; means none.</TD></TR>
<TR><TD><CODE>verb</CODE><BR /><I>string</I></TD><TD>Verb is a kubernetes resource API verb, like: get, list, watch, create, update, delete, proxy. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>version</CODE><BR /><I>string</I></TD><TD>Version is the API Version of the Resource. &#34;*&#34; means all.</TD></TR>
</TBODY>
</TABLE>
<H1 id="resourcerule-v1beta1-authorization-k8s-io">ResourceRule v1beta1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ResourceRule</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#resourcerule-v1-authorization-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#subjectrulesreviewstatus-v1beta1-authorization-k8s-io">SubjectRulesReviewStatus [authorization/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroups</CODE><BR /><I>string array</I></TD><TD>APIGroups is the name of the APIGroup that contains the resources. If multiple API groups are specified, any action requested against one of the enumerated resources in any API group will be allowed. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>resourceNames</CODE><BR /><I>string array</I></TD><TD>ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed. &#34;*&#34; means all.</TD></TR>
<TR><TD><CODE>resources</CODE><BR /><I>string array</I></TD><TD>Resources is a list of resources this rule applies to. &#34;*&#34; means all in the specified apiGroups. &#34;*/foo&#34; represents the subresource &#39;foo&#39; for all resources in the specified apiGroups.</TD></TR>
<TR><TD><CODE>verbs</CODE><BR /><I>string array</I></TD><TD>Verb is a list of kubernetes resource API verbs, like: get, list, watch, create, update, delete, proxy. &#34;*&#34; means all.</TD></TR>
</TBODY>
</TABLE>
<H1 id="role-v1beta1-rbac-authorization-k8s-io">Role v1beta1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Role</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#role-v1-rbac-authorization-k8s-io">v1</a>
<a href="#role-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#rolelist-v1beta1-rbac-authorization-k8s-io">RoleList [rbac/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyrule-v1beta1-rbac-authorization-k8s-io">PolicyRule</a> array</I></TD><TD>Rules holds all the PolicyRules for this Role</TD></TR>
</TBODY>
</TABLE>
<H3 id="rolelist-v1beta1-rbac-authorization-k8s-io">RoleList v1beta1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a> array</I></TD><TD>Items is a list of Roles</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-role-v1beta1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-role-v1beta1-rbac-authorization-k8s-io">Create</H2>
<P>create a Role</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-role-v1beta1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified Role</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-role-v1beta1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified Role</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-role-v1beta1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a Role</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-role-v1beta1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of Role</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-role-v1beta1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-role-v1beta1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1beta1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-role-v1beta1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolelist-v1beta1-rbac-authorization-k8s-io">RoleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-role-v1beta1-rbac-authorization-k8s-io">List All Namespaces</H2>
<P>list or watch objects of kind Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/roles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolelist-v1beta1-rbac-authorization-k8s-io">RoleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-role-v1beta1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-role-v1beta1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-role-v1beta1-rbac-authorization-k8s-io">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/roles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="role-v1alpha1-rbac-authorization-k8s-io">Role v1alpha1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>Role</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#role-v1-rbac-authorization-k8s-io">v1</a>
<a href="#role-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#rolelist-v1alpha1-rbac-authorization-k8s-io">RoleList [rbac/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>rules</CODE><BR /><I><a href="#policyrule-v1alpha1-rbac-authorization-k8s-io">PolicyRule</a> array</I></TD><TD>Rules holds all the PolicyRules for this Role</TD></TR>
</TBODY>
</TABLE>
<H3 id="rolelist-v1alpha1-rbac-authorization-k8s-io">RoleList v1alpha1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a> array</I></TD><TD>Items is a list of Roles</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-role-v1alpha1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-role-v1alpha1-rbac-authorization-k8s-io">Create</H2>
<P>create a Role</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-role-v1alpha1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified Role</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-role-v1alpha1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified Role</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-role-v1alpha1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a Role</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-role-v1alpha1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of Role</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-role-v1alpha1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-role-v1alpha1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#role-v1alpha1-rbac-authorization-k8s-io">Role</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-role-v1alpha1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolelist-v1alpha1-rbac-authorization-k8s-io">RoleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-role-v1alpha1-rbac-authorization-k8s-io">List All Namespaces</H2>
<P>list or watch objects of kind Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/roles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolelist-v1alpha1-rbac-authorization-k8s-io">RoleList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-role-v1alpha1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/namespaces/{namespace}/roles/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Role</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-role-v1alpha1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/namespaces/{namespace}/roles</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-role-v1alpha1-rbac-authorization-k8s-io">Watch List All Namespaces</H2>
<P>watch individual changes to a list of Role</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/roles</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding v1beta1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RoleBinding</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#rolebinding-v1-rbac-authorization-k8s-io">v1</a>
<a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#rolebindinglist-v1beta1-rbac-authorization-k8s-io">RoleBindingList [rbac/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>roleRef</CODE><BR /><I><a href="#roleref-v1beta1-rbac-authorization-k8s-io">RoleRef</a></I></TD><TD>RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.</TD></TR>
<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1beta1-rbac-authorization-k8s-io">Subject</a> array</I></TD><TD>Subjects holds references to the objects the role applies to.</TD></TR>
</TBODY>
</TABLE>
<H3 id="rolebindinglist-v1beta1-rbac-authorization-k8s-io">RoleBindingList v1beta1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a> array</I></TD><TD>Items is a list of RoleBindings</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-rolebinding-v1beta1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-rolebinding-v1beta1-rbac-authorization-k8s-io">Create</H2>
<P>create a RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-rolebinding-v1beta1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-rolebinding-v1beta1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-rolebinding-v1beta1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-rolebinding-v1beta1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-rolebinding-v1beta1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-rolebinding-v1beta1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-rolebinding-v1beta1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebindinglist-v1beta1-rbac-authorization-k8s-io">RoleBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-rolebinding-v1beta1-rbac-authorization-k8s-io">List All Namespaces</H2>
<P>list or watch objects of kind RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/rolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebindinglist-v1beta1-rbac-authorization-k8s-io">RoleBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-rolebinding-v1beta1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-rolebinding-v1beta1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-rolebinding-v1beta1-rbac-authorization-k8s-io">Watch List All Namespaces</H2>
<P>watch individual changes to a list of RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1beta1/watch/rolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding v1alpha1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>RoleBinding</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#rolebinding-v1-rbac-authorization-k8s-io">v1</a>
<a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#rolebindinglist-v1alpha1-rbac-authorization-k8s-io">RoleBindingList [rbac/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
<TR><TD><CODE>roleRef</CODE><BR /><I><a href="#roleref-v1alpha1-rbac-authorization-k8s-io">RoleRef</a></I></TD><TD>RoleRef can reference a Role in the current namespace or a ClusterRole in the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error.</TD></TR>
<TR><TD><CODE>subjects</CODE><BR /><I><a href="#subject-v1alpha1-rbac-authorization-k8s-io">Subject</a> array</I></TD><TD>Subjects holds references to the objects the role applies to.</TD></TR>
</TBODY>
</TABLE>
<H3 id="rolebindinglist-v1alpha1-rbac-authorization-k8s-io">RoleBindingList v1alpha1 rbac</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a> array</I></TD><TD>Items is a list of RoleBindings</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard object&#39;s metadata.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-rolebinding-v1alpha1-rbac-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-rolebinding-v1alpha1-rbac-authorization-k8s-io">Create</H2>
<P>create a RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-rolebinding-v1alpha1-rbac-authorization-k8s-io">Patch</H2>
<P>partially update the specified RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-rolebinding-v1alpha1-rbac-authorization-k8s-io">Replace</H2>
<P>replace the specified RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-rolebinding-v1alpha1-rbac-authorization-k8s-io">Delete</H2>
<P>delete a RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-rolebinding-v1alpha1-rbac-authorization-k8s-io">Delete Collection</H2>
<P>delete collection of RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-rolebinding-v1alpha1-rbac-authorization-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-rolebinding-v1alpha1-rbac-authorization-k8s-io">Read</H2>
<P>read the specified RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-rolebinding-v1alpha1-rbac-authorization-k8s-io">List</H2>
<P>list or watch objects of kind RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebindinglist-v1alpha1-rbac-authorization-k8s-io">RoleBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-rolebinding-v1alpha1-rbac-authorization-k8s-io">List All Namespaces</H2>
<P>list or watch objects of kind RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/rolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#rolebindinglist-v1alpha1-rbac-authorization-k8s-io">RoleBindingList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-rolebinding-v1alpha1-rbac-authorization-k8s-io">Watch</H2>
<P>watch changes to an object of kind RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/namespaces/{namespace}/rolebindings/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the RoleBinding</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-rolebinding-v1alpha1-rbac-authorization-k8s-io">Watch List</H2>
<P>watch individual changes to a list of RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/namespaces/{namespace}/rolebindings</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-rolebinding-v1alpha1-rbac-authorization-k8s-io">Watch List All Namespaces</H2>
<P>watch individual changes to a list of RoleBinding</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/rbac.authorization.k8s.io/v1alpha1/watch/rolebindings</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="roleref-v1beta1-rbac-authorization-k8s-io">RoleRef v1beta1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RoleRef</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#roleref-v1-rbac-authorization-k8s-io">v1</a>
<a href="#roleref-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1beta1]</a></LI>
<LI><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding [rbac/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup is the group for the resource being referenced</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the type of resource being referenced</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of resource being referenced</TD></TR>
</TBODY>
</TABLE>
<H1 id="roleref-v1alpha1-rbac-authorization-k8s-io">RoleRef v1alpha1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>RoleRef</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#roleref-v1-rbac-authorization-k8s-io">v1</a>
<a href="#roleref-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1alpha1]</a></LI>
<LI><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding [rbac/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup is the group for the resource being referenced</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is the type of resource being referenced</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of resource being referenced</TD></TR>
</TBODY>
</TABLE>
<H1 id="rollbackconfig-v1beta1-extensions">RollbackConfig v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RollbackConfig</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#deploymentrollback-v1beta1-extensions">DeploymentRollback [extensions/v1beta1]</a></LI>
<LI><a href="#deploymentspec-v1beta1-extensions">DeploymentSpec [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>revision</CODE><BR /><I>integer</I></TD><TD>The revision to rollback to. If set to 0, rollback to the last revision.</TD></TR>
</TBODY>
</TABLE>
<H1 id="rollingupdatestatefulsetstrategy-v1beta2-apps">RollingUpdateStatefulSetStrategy v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>RollingUpdateStatefulSetStrategy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#rollingupdatestatefulsetstrategy-v1-apps">v1</a>
<a href="#rollingupdatestatefulsetstrategy-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetupdatestrategy-v1beta2-apps">StatefulSetUpdateStrategy [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>Partition indicates the ordinal at which the StatefulSet should be partitioned. Default value is 0.</TD></TR>
</TBODY>
</TABLE>
<H1 id="rollingupdatestatefulsetstrategy-v1beta1-apps">RollingUpdateStatefulSetStrategy v1beta1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RollingUpdateStatefulSetStrategy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#rollingupdatestatefulsetstrategy-v1-apps">v1</a>
<a href="#rollingupdatestatefulsetstrategy-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetupdatestrategy-v1beta1-apps">StatefulSetUpdateStrategy [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>partition</CODE><BR /><I>integer</I></TD><TD>Partition indicates the ordinal at which the StatefulSet should be partitioned.</TD></TR>
</TBODY>
</TABLE>
<H1 id="runasuserstrategyoptions-v1beta1-policy">RunAsUserStrategyOptions v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>RunAsUserStrategyOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-policy">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of uids that may be used. If you would like to force a single uid then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate the allowable RunAsUser values that may be set.</TD></TR>
</TBODY>
</TABLE>
<H1 id="selinuxstrategyoptions-v1beta1-policy">SELinuxStrategyOptions v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SELinuxStrategyOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate the allowable labels that may be set.</TD></TR>
<TR><TD><CODE>seLinuxOptions</CODE><BR /><I><a href="#selinuxoptions-v1-core">SELinuxOptions</a></I></TD><TD>seLinuxOptions required to run as; required for MustRunAs More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/</TD></TR>
</TBODY>
</TABLE>
<H1 id="scale-v1beta2-apps">Scale v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>Scale</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#scale-v1-autoscaling">v1</a>
<a href="#scale-v1beta1-apps">v1beta1</a>
<a href="#scale-v1beta1-extensions">v1beta1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#scalespec-v1beta2-apps">ScaleSpec</a></I></TD><TD>defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#scalestatus-v1beta2-apps">ScaleStatus</a></I></TD><TD>current status of the scale. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status. Read-only.</TD></TR>
</TBODY>
</TABLE>
<H3 id="scalespec-v1beta2-apps">ScaleSpec v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#scale-v1beta2-apps">Scale [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>desired number of instances for the scaled object.</TD></TR>
</TBODY>
</TABLE>
<H3 id="scalestatus-v1beta2-apps">ScaleStatus v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#scale-v1beta2-apps">Scale [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>actual number of observed instances of the scaled object.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I>object</I></TD><TD>label query over pods that should match the replicas count. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors</TD></TR>
<TR><TD><CODE>targetSelector</CODE><BR /><I>string</I></TD><TD>label selector for pods that should match the replicas count. This is a serializated version of both map-based and more expressive set-based selectors. This is done to avoid introspection in the clients. The string will be in the same format as the query-param syntax. If the target type only supports map-based selectors, both this field and map-based selector field are populated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
</TBODY>
</TABLE>
<H1 id="scale-v1beta1-apps">Scale v1beta1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Scale</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#scale-v1-autoscaling">v1</a>
<a href="#scale-v1beta2-apps">v1beta2</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#scalespec-v1beta1-apps">ScaleSpec</a></I></TD><TD>defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#scalestatus-v1beta1-apps">ScaleStatus</a></I></TD><TD>current status of the scale. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status. Read-only.</TD></TR>
</TBODY>
</TABLE>
<H3 id="scalespec-v1beta1-apps">ScaleSpec v1beta1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#scale-v1beta1-apps">Scale [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>desired number of instances for the scaled object.</TD></TR>
</TBODY>
</TABLE>
<H3 id="scalestatus-v1beta1-apps">ScaleStatus v1beta1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#scale-v1beta1-apps">Scale [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>actual number of observed instances of the scaled object.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I>object</I></TD><TD>label query over pods that should match the replicas count. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors</TD></TR>
<TR><TD><CODE>targetSelector</CODE><BR /><I>string</I></TD><TD>label selector for pods that should match the replicas count. This is a serializated version of both map-based and more expressive set-based selectors. This is done to avoid introspection in the clients. The string will be in the same format as the query-param syntax. If the target type only supports map-based selectors, both this field and map-based selector field are populated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
</TBODY>
</TABLE>
<H1 id="scale-v1beta1-extensions">Scale v1beta1 extensions</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extensions</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Scale</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#scale-v1-autoscaling">v1</a>
<a href="#scale-v1beta2-apps">v1beta2</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata; More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata.</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#scalespec-v1beta1-extensions">ScaleSpec</a></I></TD><TD>defines the behavior of the scale. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#scalestatus-v1beta1-extensions">ScaleStatus</a></I></TD><TD>current status of the scale. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status. Read-only.</TD></TR>
</TBODY>
</TABLE>
<H3 id="scalespec-v1beta1-extensions">ScaleSpec v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#scale-v1beta1-extensions">Scale [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>desired number of instances for the scaled object.</TD></TR>
</TBODY>
</TABLE>
<H3 id="scalestatus-v1beta1-extensions">ScaleStatus v1beta1 extensions</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#scale-v1beta1-extensions">Scale [extensions/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>actual number of observed instances of the scaled object.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I>object</I></TD><TD>label query over pods that should match the replicas count. More info: http://kubernetes.io/docs/user-guide/labels#label-selectors</TD></TR>
<TR><TD><CODE>targetSelector</CODE><BR /><I>string</I></TD><TD>label selector for pods that should match the replicas count. This is a serializated version of both map-based and more expressive set-based selectors. This is done to avoid introspection in the clients. The string will be in the same format as the query-param syntax. If the target type only supports map-based selectors, both this field and map-based selector field are populated. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
</TBODY>
</TABLE>
<H1 id="selfsubjectaccessreview-v1beta1-authorization-k8s-io">SelfSubjectAccessReview v1beta1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SelfSubjectAccessReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#selfsubjectaccessreview-v1-authorization-k8s-io">v1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#selfsubjectaccessreviewspec-v1beta1-authorization-k8s-io">SelfSubjectAccessReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated. user and groups must be empty</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectaccessreviewstatus-v1beta1-authorization-k8s-io">SubjectAccessReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request is allowed or not</TD></TR>
</TBODY>
</TABLE>
<H3 id="selfsubjectaccessreviewspec-v1beta1-authorization-k8s-io">SelfSubjectAccessReviewSpec v1beta1 authorization</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectaccessreview-v1beta1-authorization-k8s-io">SelfSubjectAccessReview [authorization/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>nonResourceAttributes</CODE><BR /><I><a href="#nonresourceattributes-v1beta1-authorization-k8s-io">NonResourceAttributes</a></I></TD><TD>NonResourceAttributes describes information for a non-resource access request</TD></TR>
<TR><TD><CODE>resourceAttributes</CODE><BR /><I><a href="#resourceattributes-v1beta1-authorization-k8s-io">ResourceAttributes</a></I></TD><TD>ResourceAuthorizationAttributes describes information for a resource access request</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-selfsubjectaccessreview-v1beta1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-selfsubjectaccessreview-v1beta1-authorization-k8s-io">Create</H2>
<P>create a SelfSubjectAccessReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authorization.k8s.io/v1beta1/selfsubjectaccessreviews</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#selfsubjectaccessreview-v1beta1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#selfsubjectaccessreview-v1beta1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#selfsubjectaccessreview-v1beta1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#selfsubjectaccessreview-v1beta1-authorization-k8s-io">SelfSubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H1 id="selfsubjectrulesreview-v1beta1-authorization-k8s-io">SelfSubjectRulesReview v1beta1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SelfSubjectRulesReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#selfsubjectrulesreview-v1-authorization-k8s-io">v1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#selfsubjectrulesreviewspec-v1beta1-authorization-k8s-io">SelfSubjectRulesReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectrulesreviewstatus-v1beta1-authorization-k8s-io">SubjectRulesReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates the set of actions a user can perform.</TD></TR>
</TBODY>
</TABLE>
<H3 id="selfsubjectrulesreviewspec-v1beta1-authorization-k8s-io">SelfSubjectRulesReviewSpec v1beta1 authorization</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectrulesreview-v1beta1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace to evaluate rules for. Required.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-selfsubjectrulesreview-v1beta1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-selfsubjectrulesreview-v1beta1-authorization-k8s-io">Create</H2>
<P>create a SelfSubjectRulesReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authorization.k8s.io/v1beta1/selfsubjectrulesreviews</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#selfsubjectrulesreview-v1beta1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>202<br /><I><a href="#selfsubjectrulesreview-v1beta1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#selfsubjectrulesreview-v1beta1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#selfsubjectrulesreview-v1beta1-authorization-k8s-io">SelfSubjectRulesReview</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H1 id="servicereference-v1beta1-admissionregistration-k8s-io">ServiceReference v1beta1 admissionregistration.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>admissionregistration.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ServiceReference</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#servicereference-v1-apiregistration-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#webhookclientconfig-v1beta1-admissionregistration-k8s-io">WebhookClientConfig [admissionregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>`name` is the name of the service. Required</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>`namespace` is the namespace of the service. Required</TD></TR>
<TR><TD><CODE>path</CODE><BR /><I>string</I></TD><TD>`path` is an optional URL path which will be sent in any request to this service.</TD></TR>
</TBODY>
</TABLE>
<H1 id="servicereference-v1beta1-apiregistration-k8s-io">ServiceReference v1beta1 apiregistration.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiregistration.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>ServiceReference</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#servicereference-v1-apiregistration-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#apiservicespec-v1beta1-apiregistration-k8s-io">APIServiceSpec [apiregistration/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name is the name of the service</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace is the namespace of the service</TD></TR>
</TBODY>
</TABLE>
<H1 id="statefulset-v1beta2-apps">StatefulSet v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>StatefulSet</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#statefulset-v1-apps">v1</a>
<a href="#statefulset-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetlist-v1beta2-apps">StatefulSetList [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#statefulsetspec-v1beta2-apps">StatefulSetSpec</a></I></TD><TD>Spec defines the desired identities of pods in this set.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#statefulsetstatus-v1beta2-apps">StatefulSetStatus</a></I></TD><TD>Status is the current status of Pods in this StatefulSet. This data may be out of date by some window of time.</TD></TR>
</TBODY>
</TABLE>
<H3 id="statefulsetspec-v1beta2-apps">StatefulSetSpec v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulset-v1beta2-apps">StatefulSet [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>podManagementPolicy</CODE><BR /><I>string</I></TD><TD>podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet&#39;s revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is a label query over pods that should match the replica count. It must match the pod template&#39;s labels. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>serviceName</CODE><BR /><I>string</I></TD><TD>serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where &#34;pod-specific-string&#34; is managed by the StatefulSet controller.</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.</TD></TR>
<TR><TD><CODE>updateStrategy</CODE><BR /><I><a href="#statefulsetupdatestrategy-v1beta2-apps">StatefulSetUpdateStrategy</a></I></TD><TD>updateStrategy indicates the StatefulSetUpdateStrategy that will be employed to update Pods in the StatefulSet when a revision is made to Template.</TD></TR>
<TR><TD><CODE>volumeClaimTemplates</CODE><BR /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a> array</I></TD><TD>volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.</TD></TR>
</TBODY>
</TABLE>
<H3 id="statefulsetstatus-v1beta2-apps">StatefulSetStatus v1beta2 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulset-v1beta2-apps">StatefulSet [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#statefulsetcondition-v1beta2-apps">StatefulSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a statefulset&#39;s current state.</TD></TR>
<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>currentReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by currentRevision.</TD></TR>
<TR><TD><CODE>currentRevision</CODE><BR /><I>string</I></TD><TD>currentRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [0,currentReplicas).</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet&#39;s generation, which is updated on mutation by the API Server.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>readyReplicas is the number of Pods created by the StatefulSet controller that have a Ready Condition.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>replicas is the number of Pods created by the StatefulSet controller.</TD></TR>
<TR><TD><CODE>updateRevision</CODE><BR /><I>string</I></TD><TD>updateRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [replicas-updatedReplicas,replicas)</TD></TR>
<TR><TD><CODE>updatedReplicas</CODE><BR /><I>integer</I></TD><TD>updatedReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by updateRevision.</TD></TR>
</TBODY>
</TABLE>
<H3 id="statefulsetlist-v1beta2-apps">StatefulSetList v1beta2 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-statefulset-v1beta2-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-statefulset-v1beta2-apps">Create</H2>
<P>create a StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1beta2/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-statefulset-v1beta2-apps">Patch</H2>
<P>partially update the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-statefulset-v1beta2-apps">Replace</H2>
<P>replace the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-statefulset-v1beta2-apps">Delete</H2>
<P>delete a StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-statefulset-v1beta2-apps">Delete Collection</H2>
<P>delete collection of StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta2/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-statefulset-v1beta2-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-statefulset-v1beta2-apps">Read</H2>
<P>read the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-statefulset-v1beta2-apps">List</H2>
<P>list or watch objects of kind StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulsetlist-v1beta2-apps">StatefulSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-statefulset-v1beta2-apps">List All Namespaces</H2>
<P>list or watch objects of kind StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/statefulsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulsetlist-v1beta2-apps">StatefulSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-statefulset-v1beta2-apps">Watch</H2>
<P>watch changes to an object of kind StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-statefulset-v1beta2-apps">Watch List</H2>
<P>watch individual changes to a list of StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-statefulset-v1beta2-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/watch/statefulsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-statefulset-v1beta2-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-statefulset-v1beta2-apps">Patch Status</H2>
<P>partially update status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-statefulset-v1beta2-apps">Read Status</H2>
<P>read status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-statefulset-v1beta2-apps">Replace Status</H2>
<P>replace status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#statefulset-v1beta2-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-statefulset-v1beta2-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-statefulset-v1beta2-apps">Read Scale</H2>
<P>read scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-statefulset-v1beta2-apps">Replace Scale</H2>
<P>replace scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-statefulset-v1beta2-apps">Patch Scale</H2>
<P>partially update scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta2/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta2-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="statefulset-v1beta1-apps">StatefulSet v1beta1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>StatefulSet</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#statefulset-v1-apps">v1</a>
<a href="#statefulset-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetlist-v1beta1-apps">StatefulSetList [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#statefulsetspec-v1beta1-apps">StatefulSetSpec</a></I></TD><TD>Spec defines the desired identities of pods in this set.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#statefulsetstatus-v1beta1-apps">StatefulSetStatus</a></I></TD><TD>Status is the current status of Pods in this StatefulSet. This data may be out of date by some window of time.</TD></TR>
</TBODY>
</TABLE>
<H3 id="statefulsetspec-v1beta1-apps">StatefulSetSpec v1beta1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulset-v1beta1-apps">StatefulSet [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>podManagementPolicy</CODE><BR /><I>string</I></TD><TD>podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete all pods at once.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>replicas is the desired number of replicas of the given Template. These are replicas in the sense that they are instantiations of the same Template, but individual replicas also have a consistent identity. If unspecified, defaults to 1.</TD></TR>
<TR><TD><CODE>revisionHistoryLimit</CODE><BR /><I>integer</I></TD><TD>revisionHistoryLimit is the maximum number of revisions that will be maintained in the StatefulSet&#39;s revision history. The revision history consists of all revisions not represented by a currently applied StatefulSetSpec version. The default value is 10.</TD></TR>
<TR><TD><CODE>selector</CODE><BR /><I><a href="#labelselector-v1-meta">LabelSelector</a></I></TD><TD>selector is a label query over pods that should match the replica count. If empty, defaulted to labels on the pod template. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors</TD></TR>
<TR><TD><CODE>serviceName</CODE><BR /><I>string</I></TD><TD>serviceName is the name of the service that governs this StatefulSet. This service must exist before the StatefulSet, and is responsible for the network identity of the set. Pods get DNS/hostnames that follow the pattern: pod-specific-string.serviceName.default.svc.cluster.local where &#34;pod-specific-string&#34; is managed by the StatefulSet controller.</TD></TR>
<TR><TD><CODE>template</CODE><BR /><I><a href="#podtemplatespec-v1-core">PodTemplateSpec</a></I></TD><TD>template is the object that describes the pod that will be created if insufficient replicas are detected. Each pod stamped out by the StatefulSet will fulfill this Template, but have a unique identity from the rest of the StatefulSet.</TD></TR>
<TR><TD><CODE>updateStrategy</CODE><BR /><I><a href="#statefulsetupdatestrategy-v1beta1-apps">StatefulSetUpdateStrategy</a></I></TD><TD>updateStrategy indicates the StatefulSetUpdateStrategy that will be employed to update Pods in the StatefulSet when a revision is made to Template.</TD></TR>
<TR><TD><CODE>volumeClaimTemplates</CODE><BR /><I><a href="#persistentvolumeclaim-v1-core">PersistentVolumeClaim</a> array</I></TD><TD>volumeClaimTemplates is a list of claims that pods are allowed to reference. The StatefulSet controller is responsible for mapping network identities to claims in a way that maintains the identity of a pod. Every claim in this list must have at least one matching (by name) volumeMount in one container in the template. A claim in this list takes precedence over any volumes in the template, with the same name.</TD></TR>
</TBODY>
</TABLE>
<H3 id="statefulsetstatus-v1beta1-apps">StatefulSetStatus v1beta1 apps</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulset-v1beta1-apps">StatefulSet [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>collisionCount</CODE><BR /><I>integer</I></TD><TD>collisionCount is the count of hash collisions for the StatefulSet. The StatefulSet controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest ControllerRevision.</TD></TR>
<TR><TD><CODE>conditions</CODE><BR /><I><a href="#statefulsetcondition-v1beta1-apps">StatefulSetCondition</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>type</I></TD><TD>Represents the latest available observations of a statefulset&#39;s current state.</TD></TR>
<TR><TD><CODE>currentReplicas</CODE><BR /><I>integer</I></TD><TD>currentReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by currentRevision.</TD></TR>
<TR><TD><CODE>currentRevision</CODE><BR /><I>string</I></TD><TD>currentRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [0,currentReplicas).</TD></TR>
<TR><TD><CODE>observedGeneration</CODE><BR /><I>integer</I></TD><TD>observedGeneration is the most recent generation observed for this StatefulSet. It corresponds to the StatefulSet&#39;s generation, which is updated on mutation by the API Server.</TD></TR>
<TR><TD><CODE>readyReplicas</CODE><BR /><I>integer</I></TD><TD>readyReplicas is the number of Pods created by the StatefulSet controller that have a Ready Condition.</TD></TR>
<TR><TD><CODE>replicas</CODE><BR /><I>integer</I></TD><TD>replicas is the number of Pods created by the StatefulSet controller.</TD></TR>
<TR><TD><CODE>updateRevision</CODE><BR /><I>string</I></TD><TD>updateRevision, if not empty, indicates the version of the StatefulSet used to generate Pods in the sequence [replicas-updatedReplicas,replicas)</TD></TR>
<TR><TD><CODE>updatedReplicas</CODE><BR /><I>integer</I></TD><TD>updatedReplicas is the number of Pods created by the StatefulSet controller from the StatefulSet version indicated by updateRevision.</TD></TR>
</TBODY>
</TABLE>
<H3 id="statefulsetlist-v1beta1-apps">StatefulSetList v1beta1 apps</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a> array</I></TD><TD></TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-statefulset-v1beta1-apps-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-statefulset-v1beta1-apps">Create</H2>
<P>create a StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/apps/v1beta1/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-statefulset-v1beta1-apps">Patch</H2>
<P>partially update the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-statefulset-v1beta1-apps">Replace</H2>
<P>replace the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-statefulset-v1beta1-apps">Delete</H2>
<P>delete a StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-statefulset-v1beta1-apps">Delete Collection</H2>
<P>delete collection of StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/apps/v1beta1/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-statefulset-v1beta1-apps-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-statefulset-v1beta1-apps">Read</H2>
<P>read the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-statefulset-v1beta1-apps">List</H2>
<P>list or watch objects of kind StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulsetlist-v1beta1-apps">StatefulSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-all-namespaces-statefulset-v1beta1-apps">List All Namespaces</H2>
<P>list or watch objects of kind StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/statefulsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulsetlist-v1beta1-apps">StatefulSetList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-statefulset-v1beta1-apps">Watch</H2>
<P>watch changes to an object of kind StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/watch/namespaces/{namespace}/statefulsets/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-statefulset-v1beta1-apps">Watch List</H2>
<P>watch individual changes to a list of StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/watch/namespaces/{namespace}/statefulsets</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-all-namespaces-statefulset-v1beta1-apps">Watch List All Namespaces</H2>
<P>watch individual changes to a list of StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/watch/statefulsets</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-status-operations-statefulset-v1beta1-apps-strong-"><STRONG>Status Operations</STRONG></H2>
<H2 id="patch-status-statefulset-v1beta1-apps">Patch Status</H2>
<P>partially update status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="read-status-statefulset-v1beta1-apps">Read Status</H2>
<P>read status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-status-statefulset-v1beta1-apps">Replace Status</H2>
<P>replace status of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/status</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StatefulSet</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>Created</TD></TR>
<TR><TD>200<br /><I><a href="#statefulset-v1beta1-apps">StatefulSet</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-misc-operations-statefulset-v1beta1-apps-strong-"><STRONG>Misc Operations</STRONG></H2>
<H2 id="read-scale-statefulset-v1beta1-apps">Read Scale</H2>
<P>read scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-scale-statefulset-v1beta1-apps">Replace Scale</H2>
<P>replace scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-scale-statefulset-v1beta1-apps">Patch Scale</H2>
<P>partially update scale of the specified StatefulSet</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/apps/v1beta1/namespaces/{namespace}/statefulsets/{name}/scale</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the Scale</TD></TR>
<TR><TD><CODE>namespace</CODE></TD><TD>object name and auth scope, such as for teams and projects</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#scale-v1beta1-apps">Scale</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="statefulsetcondition-v1beta2-apps">StatefulSetCondition v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>StatefulSetCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#statefulsetcondition-v1-apps">v1</a>
<a href="#statefulsetcondition-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetstatus-v1beta2-apps">StatefulSetStatus [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of statefulset condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="statefulsetcondition-v1beta1-apps">StatefulSetCondition v1beta1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>StatefulSetCondition</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#statefulsetcondition-v1-apps">v1</a>
<a href="#statefulsetcondition-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetstatus-v1beta1-apps">StatefulSetStatus [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>lastTransitionTime</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Last time the condition transitioned from one status to another.</TD></TR>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>A human readable message indicating details about the transition.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>The reason for the condition&#39;s last transition.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I>string</I></TD><TD>Status of the condition, one of True, False, Unknown.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type of statefulset condition.</TD></TR>
</TBODY>
</TABLE>
<H1 id="statefulsetupdatestrategy-v1beta2-apps">StatefulSetUpdateStrategy v1beta2 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta2</CODE></TD><TD><CODE>StatefulSetUpdateStrategy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#statefulsetupdatestrategy-v1-apps">v1</a>
<a href="#statefulsetupdatestrategy-v1beta1-apps">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetspec-v1beta2-apps">StatefulSetSpec [apps/v1beta2]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatestatefulsetstrategy-v1beta2-apps">RollingUpdateStatefulSetStrategy</a></I></TD><TD>RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type indicates the type of the StatefulSetUpdateStrategy. Default is RollingUpdate.</TD></TR>
</TBODY>
</TABLE>
<H1 id="statefulsetupdatestrategy-v1beta1-apps">StatefulSetUpdateStrategy v1beta1 apps</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apps</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>StatefulSetUpdateStrategy</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#statefulsetupdatestrategy-v1-apps">v1</a>
<a href="#statefulsetupdatestrategy-v1beta2-apps">v1beta2</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#statefulsetspec-v1beta1-apps">StatefulSetSpec [apps/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rollingUpdate</CODE><BR /><I><a href="#rollingupdatestatefulsetstrategy-v1beta1-apps">RollingUpdateStatefulSetStrategy</a></I></TD><TD>RollingUpdate is used to communicate parameters when Type is RollingUpdateStatefulSetStrategyType.</TD></TR>
<TR><TD><CODE>type</CODE><BR /><I>string</I></TD><TD>Type indicates the type of the StatefulSetUpdateStrategy.</TD></TR>
</TBODY>
</TABLE>
<H1 id="storageclass-v1beta1-storage-k8s-io">StorageClass v1beta1 storage.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>StorageClass</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#storageclass-v1-storage-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#storageclasslist-v1beta1-storage-k8s-io">StorageClassList [storage/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowVolumeExpansion</CODE><BR /><I>boolean</I></TD><TD>AllowVolumeExpansion shows whether the storage class allow volume expand</TD></TR>
<TR><TD><CODE>allowedTopologies</CODE><BR /><I><a href="#topologyselectorterm-v1-core">TopologySelectorTerm</a> array</I></TD><TD>Restrict the node topologies where volumes can be dynamically provisioned. Each volume plugin defines its own supported topology specifications. An empty TopologySelectorTerm list means there is no topology restriction. This field is alpha-level and is only honored by servers that enable the DynamicProvisioningScheduling feature.</TD></TR>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object&#39;s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>mountOptions</CODE><BR /><I>string array</I></TD><TD>Dynamically provisioned PersistentVolumes of this storage class are created with these mountOptions, e.g. [&#34;ro&#34;, &#34;soft&#34;]. Not validated - mount of the PVs will simply fail if one is invalid.</TD></TR>
<TR><TD><CODE>parameters</CODE><BR /><I>object</I></TD><TD>Parameters holds the parameters for the provisioner that should create volumes of this storage class.</TD></TR>
<TR><TD><CODE>provisioner</CODE><BR /><I>string</I></TD><TD>Provisioner indicates the type of the provisioner.</TD></TR>
<TR><TD><CODE>reclaimPolicy</CODE><BR /><I>string</I></TD><TD>Dynamically provisioned PersistentVolumes of this storage class are created with this reclaimPolicy. Defaults to Delete.</TD></TR>
<TR><TD><CODE>volumeBindingMode</CODE><BR /><I>string</I></TD><TD>VolumeBindingMode indicates how PersistentVolumeClaims should be provisioned and bound. When unset, VolumeBindingImmediate is used. This field is alpha-level and is only honored by servers that enable the VolumeScheduling feature.</TD></TR>
</TBODY>
</TABLE>
<H3 id="storageclasslist-v1beta1-storage-k8s-io">StorageClassList v1beta1 storage</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a> array</I></TD><TD>Items is the list of StorageClasses</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-storageclass-v1beta1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-storageclass-v1beta1-storage-k8s-io">Create</H2>
<P>create a StorageClass</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/storage.k8s.io/v1beta1/storageclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-storageclass-v1beta1-storage-k8s-io">Patch</H2>
<P>partially update the specified StorageClass</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/storage.k8s.io/v1beta1/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-storageclass-v1beta1-storage-k8s-io">Replace</H2>
<P>replace the specified StorageClass</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/storage.k8s.io/v1beta1/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-storageclass-v1beta1-storage-k8s-io">Delete</H2>
<P>delete a StorageClass</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/storage.k8s.io/v1beta1/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-storageclass-v1beta1-storage-k8s-io">Delete Collection</H2>
<P>delete collection of StorageClass</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/storage.k8s.io/v1beta1/storageclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-storageclass-v1beta1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-storageclass-v1beta1-storage-k8s-io">Read</H2>
<P>read the specified StorageClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1beta1/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageclass-v1beta1-storage-k8s-io">StorageClass</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-storageclass-v1beta1-storage-k8s-io">List</H2>
<P>list or watch objects of kind StorageClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1beta1/storageclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#storageclasslist-v1beta1-storage-k8s-io">StorageClassList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-storageclass-v1beta1-storage-k8s-io">Watch</H2>
<P>watch changes to an object of kind StorageClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1beta1/watch/storageclasses/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the StorageClass</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-storageclass-v1beta1-storage-k8s-io">Watch List</H2>
<P>watch individual changes to a list of StorageClass</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1beta1/watch/storageclasses</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="subject-v1beta1-rbac-authorization-k8s-io">Subject v1beta1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>Subject</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#subject-v1-rbac-authorization-k8s-io">v1</a>
<a href="#subject-v1alpha1-rbac-authorization-k8s-io">v1alpha1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolebinding-v1beta1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1beta1]</a></LI>
<LI><a href="#rolebinding-v1beta1-rbac-authorization-k8s-io">RoleBinding [rbac/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiGroup</CODE><BR /><I>string</I></TD><TD>APIGroup holds the API group of the referenced subject. Defaults to &#34;&#34; for ServiceAccount subjects. Defaults to &#34;rbac.authorization.k8s.io&#34; for User and Group subjects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of object being referenced. Values defined by this API group are &#34;User&#34;, &#34;Group&#34;, and &#34;ServiceAccount&#34;. If the Authorizer does not recognized the kind value, the Authorizer should report an error.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the object being referenced.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace of the referenced object. If the object kind is non-namespace, such as &#34;User&#34; or &#34;Group&#34;, and this value is not empty the Authorizer should report an error.</TD></TR>
</TBODY>
</TABLE>
<H1 id="subject-v1alpha1-rbac-authorization-k8s-io">Subject v1alpha1 rbac.authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>rbac.authorization.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>Subject</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#subject-v1-rbac-authorization-k8s-io">v1</a>
<a href="#subject-v1beta1-rbac-authorization-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#clusterrolebinding-v1alpha1-rbac-authorization-k8s-io">ClusterRoleBinding [rbac/v1alpha1]</a></LI>
<LI><a href="#rolebinding-v1alpha1-rbac-authorization-k8s-io">RoleBinding [rbac/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>APIVersion holds the API group and version of the referenced subject. Defaults to &#34;v1&#34; for ServiceAccount subjects. Defaults to &#34;rbac.authorization.k8s.io/v1alpha1&#34; for User and Group subjects.</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind of object being referenced. Values defined by this API group are &#34;User&#34;, &#34;Group&#34;, and &#34;ServiceAccount&#34;. If the Authorizer does not recognized the kind value, the Authorizer should report an error.</TD></TR>
<TR><TD><CODE>name</CODE><BR /><I>string</I></TD><TD>Name of the object being referenced.</TD></TR>
<TR><TD><CODE>namespace</CODE><BR /><I>string</I></TD><TD>Namespace of the referenced object. If the object kind is non-namespace, such as &#34;User&#34; or &#34;Group&#34;, and this value is not empty the Authorizer should report an error.</TD></TR>
</TBODY>
</TABLE>
<H1 id="subjectaccessreview-v1beta1-authorization-k8s-io">SubjectAccessReview v1beta1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SubjectAccessReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#subjectaccessreview-v1-authorization-k8s-io">v1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#subjectaccessreviewspec-v1beta1-authorization-k8s-io">SubjectAccessReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#subjectaccessreviewstatus-v1beta1-authorization-k8s-io">SubjectAccessReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request is allowed or not</TD></TR>
</TBODY>
</TABLE>
<H3 id="subjectaccessreviewspec-v1beta1-authorization-k8s-io">SubjectAccessReviewSpec v1beta1 authorization</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#localsubjectaccessreview-v1beta1-authorization-k8s-io">LocalSubjectAccessReview [authorization/v1beta1]</a></LI>
<LI><a href="#subjectaccessreview-v1beta1-authorization-k8s-io">SubjectAccessReview [authorization/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extra</CODE><BR /><I>object</I></TD><TD>Extra corresponds to the user.Info.GetExtra() method from the authenticator. Since that is input to the authorizer it needs a reflection here.</TD></TR>
<TR><TD><CODE>group</CODE><BR /><I>string array</I></TD><TD>Groups is the groups you&#39;re testing for.</TD></TR>
<TR><TD><CODE>nonResourceAttributes</CODE><BR /><I><a href="#nonresourceattributes-v1beta1-authorization-k8s-io">NonResourceAttributes</a></I></TD><TD>NonResourceAttributes describes information for a non-resource access request</TD></TR>
<TR><TD><CODE>resourceAttributes</CODE><BR /><I><a href="#resourceattributes-v1beta1-authorization-k8s-io">ResourceAttributes</a></I></TD><TD>ResourceAuthorizationAttributes describes information for a resource access request</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>UID information about the requesting user.</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I>string</I></TD><TD>User is the user you&#39;re testing for. If you specify &#34;User&#34; but not &#34;Group&#34;, then is it interpreted as &#34;What if User were not a member of any groups</TD></TR>
</TBODY>
</TABLE>
<H3 id="subjectaccessreviewstatus-v1beta1-authorization-k8s-io">SubjectAccessReviewStatus v1beta1 authorization</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#localsubjectaccessreview-v1beta1-authorization-k8s-io">LocalSubjectAccessReview [authorization/v1beta1]</a></LI>
<LI><a href="#selfsubjectaccessreview-v1beta1-authorization-k8s-io">SelfSubjectAccessReview [authorization/v1beta1]</a></LI>
<LI><a href="#subjectaccessreview-v1beta1-authorization-k8s-io">SubjectAccessReview [authorization/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>allowed</CODE><BR /><I>boolean</I></TD><TD>Allowed is required. True if the action would be allowed, false otherwise.</TD></TR>
<TR><TD><CODE>denied</CODE><BR /><I>boolean</I></TD><TD>Denied is optional. True if the action would be denied, otherwise false. If both allowed is false and denied is false, then the authorizer has no opinion on whether to authorize the action. Denied may not be true if Allowed is true.</TD></TR>
<TR><TD><CODE>evaluationError</CODE><BR /><I>string</I></TD><TD>EvaluationError is an indication that some error occurred during the authorization check. It is entirely possible to get an error and be able to continue determine authorization status in spite of it. For instance, RBAC can be missing a role, but enough roles are still present and bound to reason about the request.</TD></TR>
<TR><TD><CODE>reason</CODE><BR /><I>string</I></TD><TD>Reason is optional. It indicates why a request was allowed or denied.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-subjectaccessreview-v1beta1-authorization-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-subjectaccessreview-v1beta1-authorization-k8s-io">Create</H2>
<P>create a SubjectAccessReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authorization.k8s.io/v1beta1/subjectaccessreviews</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#subjectaccessreview-v1beta1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>201<br /><I><a href="#subjectaccessreview-v1beta1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#subjectaccessreview-v1beta1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>Accepted</TD></TR>
<TR><TD>200<br /><I><a href="#subjectaccessreview-v1beta1-authorization-k8s-io">SubjectAccessReview</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="subjectrulesreviewstatus-v1beta1-authorization-k8s-io">SubjectRulesReviewStatus v1beta1 authorization.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authorization.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SubjectRulesReviewStatus</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#subjectrulesreviewstatus-v1-authorization-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#selfsubjectrulesreview-v1beta1-authorization-k8s-io">SelfSubjectRulesReview [authorization/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>evaluationError</CODE><BR /><I>string</I></TD><TD>EvaluationError can appear in combination with Rules. It indicates an error occurred during rule evaluation, such as an authorizer that doesn&#39;t support rule evaluation, and that ResourceRules and/or NonResourceRules may be incomplete.</TD></TR>
<TR><TD><CODE>incomplete</CODE><BR /><I>boolean</I></TD><TD>Incomplete is true when the rules returned by this call are incomplete. This is most commonly encountered when an authorizer, such as an external authorizer, doesn&#39;t support rules evaluation.</TD></TR>
<TR><TD><CODE>nonResourceRules</CODE><BR /><I><a href="#nonresourcerule-v1beta1-authorization-k8s-io">NonResourceRule</a> array</I></TD><TD>NonResourceRules is the list of actions the subject is allowed to perform on non-resources. The list ordering isn&#39;t significant, may contain duplicates, and possibly be incomplete.</TD></TR>
<TR><TD><CODE>resourceRules</CODE><BR /><I><a href="#resourcerule-v1beta1-authorization-k8s-io">ResourceRule</a> array</I></TD><TD>ResourceRules is the list of actions the subject is allowed to perform on resources. The list ordering isn&#39;t significant, may contain duplicates, and possibly be incomplete.</TD></TR>
</TBODY>
</TABLE>
<H1 id="supplementalgroupsstrategyoptions-v1beta1-policy">SupplementalGroupsStrategyOptions v1beta1 policy</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>policy</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>SupplementalGroupsStrategyOptions</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#podsecuritypolicyspec-v1beta1-policy">PodSecurityPolicySpec [policy/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>ranges</CODE><BR /><I><a href="#idrange-v1beta1-policy">IDRange</a> array</I></TD><TD>ranges are the allowed ranges of supplemental groups. If you would like to force a single supplemental group then supply a single range with the same start and end. Required for MustRunAs.</TD></TR>
<TR><TD><CODE>rule</CODE><BR /><I>string</I></TD><TD>rule is the strategy that will dictate what supplemental groups is used in the SecurityContext.</TD></TR>
</TBODY>
</TABLE>
<H1 id="tokenreview-v1beta1-authentication-k8s-io">TokenReview v1beta1 authentication.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>TokenReview</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#tokenreview-v1-authentication-k8s-io">v1</a>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD></TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#tokenreviewspec-v1beta1-authentication-k8s-io">TokenReviewSpec</a></I></TD><TD>Spec holds information about the request being evaluated</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#tokenreviewstatus-v1beta1-authentication-k8s-io">TokenReviewStatus</a></I></TD><TD>Status is filled in by the server and indicates whether the request can be authenticated.</TD></TR>
</TBODY>
</TABLE>
<H3 id="tokenreviewspec-v1beta1-authentication-k8s-io">TokenReviewSpec v1beta1 authentication</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#tokenreview-v1beta1-authentication-k8s-io">TokenReview [authentication/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>token</CODE><BR /><I>string</I></TD><TD>Token is the opaque bearer token.</TD></TR>
</TBODY>
</TABLE>
<H3 id="tokenreviewstatus-v1beta1-authentication-k8s-io">TokenReviewStatus v1beta1 authentication</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#tokenreview-v1beta1-authentication-k8s-io">TokenReview [authentication/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authenticated</CODE><BR /><I>boolean</I></TD><TD>Authenticated indicates that the token was associated with a known user.</TD></TR>
<TR><TD><CODE>error</CODE><BR /><I>string</I></TD><TD>Error indicates that the token couldn&#39;t be checked</TD></TR>
<TR><TD><CODE>user</CODE><BR /><I><a href="#userinfo-v1beta1-authentication-k8s-io">UserInfo</a></I></TD><TD>User is the UserInfo associated with the provided token.</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-tokenreview-v1beta1-authentication-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-tokenreview-v1beta1-authentication-k8s-io">Create</H2>
<P>create a TokenReview</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/authentication.k8s.io/v1beta1/tokenreviews</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#tokenreview-v1beta1-authentication-k8s-io">TokenReview</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#tokenreview-v1beta1-authentication-k8s-io">TokenReview</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#tokenreview-v1beta1-authentication-k8s-io">TokenReview</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#tokenreview-v1beta1-authentication-k8s-io">TokenReview</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H1 id="userinfo-v1beta1-authentication-k8s-io">UserInfo v1beta1 authentication.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>authentication.k8s.io</CODE></TD><TD><CODE>v1beta1</CODE></TD><TD><CODE>UserInfo</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#userinfo-v1-authentication-k8s-io">v1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#tokenreviewstatus-v1beta1-authentication-k8s-io">TokenReviewStatus [authentication/v1beta1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>extra</CODE><BR /><I>object</I></TD><TD>Any additional information provided by the authenticator.</TD></TR>
<TR><TD><CODE>groups</CODE><BR /><I>string array</I></TD><TD>The names of groups this user is a part of.</TD></TR>
<TR><TD><CODE>uid</CODE><BR /><I>string</I></TD><TD>A unique value that identifies this user across time. If this user is deleted and another user by the same name is added, they will have different UIDs.</TD></TR>
<TR><TD><CODE>username</CODE><BR /><I>string</I></TD><TD>The name that uniquely identifies this user among all active users.</TD></TR>
</TBODY>
</TABLE>
<H1 id="volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment v1alpha1 storage.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>VolumeAttachment</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#volumeattachment-v1beta1-storage-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachmentlist-v1alpha1-storage-k8s-io">VolumeAttachmentList [storage/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
<TR><TD><CODE>spec</CODE><BR /><I><a href="#volumeattachmentspec-v1alpha1-storage-k8s-io">VolumeAttachmentSpec</a></I></TD><TD>Specification of the desired attach/detach volume behavior. Populated by the Kubernetes system.</TD></TR>
<TR><TD><CODE>status</CODE><BR /><I><a href="#volumeattachmentstatus-v1alpha1-storage-k8s-io">VolumeAttachmentStatus</a></I></TD><TD>Status of the VolumeAttachment request. Populated by the entity completing the attach or detach operation, i.e. the external-attacher.</TD></TR>
</TBODY>
</TABLE>
<H3 id="volumeattachmentspec-v1alpha1-storage-k8s-io">VolumeAttachmentSpec v1alpha1 storage</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment [storage/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>attacher</CODE><BR /><I>string</I></TD><TD>Attacher indicates the name of the volume driver that MUST handle this request. This is the name returned by GetPluginName().</TD></TR>
<TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>The node that the volume should be attached to.</TD></TR>
<TR><TD><CODE>source</CODE><BR /><I><a href="#volumeattachmentsource-v1alpha1-storage-k8s-io">VolumeAttachmentSource</a></I></TD><TD>Source represents the volume that should be attached.</TD></TR>
</TBODY>
</TABLE>
<H3 id="volumeattachmentstatus-v1alpha1-storage-k8s-io">VolumeAttachmentStatus v1alpha1 storage</H3>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment [storage/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>attachError</CODE><BR /><I><a href="#volumeerror-v1alpha1-storage-k8s-io">VolumeError</a></I></TD><TD>The last error encountered during attach operation, if any. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.</TD></TR>
<TR><TD><CODE>attached</CODE><BR /><I>boolean</I></TD><TD>Indicates the volume is successfully attached. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.</TD></TR>
<TR><TD><CODE>attachmentMetadata</CODE><BR /><I>object</I></TD><TD>Upon successful attach, this field is populated with any information returned by the attach operation that must be passed into subsequent WaitForAttach or Mount calls. This field must only be set by the entity completing the attach operation, i.e. the external-attacher.</TD></TR>
<TR><TD><CODE>detachError</CODE><BR /><I><a href="#volumeerror-v1alpha1-storage-k8s-io">VolumeError</a></I></TD><TD>The last error encountered during detach operation, if any. This field must only be set by the entity completing the detach operation, i.e. the external-attacher.</TD></TR>
</TBODY>
</TABLE>
<H3 id="volumeattachmentlist-v1alpha1-storage-k8s-io">VolumeAttachmentList v1alpha1 storage</H3>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>apiVersion</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#resources</TD></TR>
<TR><TD><CODE>items</CODE><BR /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a> array</I></TD><TD>Items is the list of VolumeAttachments</TD></TR>
<TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>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/api-conventions.md#types-kinds</TD></TR>
<TR><TD><CODE>metadata</CODE><BR /><I><a href="#listmeta-v1-meta">ListMeta</a></I></TD><TD>Standard list metadata More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-write-operations-volumeattachment-v1alpha1-storage-k8s-io-strong-"><STRONG>Write Operations</STRONG></H2>
<H2 id="create-volumeattachment-v1alpha1-storage-k8s-io">Create</H2>
<P>create a VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>POST /apis/storage.k8s.io/v1alpha1/volumeattachments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
<TR><TD>202<br /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Accepted</TD></TR>
</TBODY>
</TABLE>
<H2 id="patch-volumeattachment-v1alpha1-storage-k8s-io">Patch</H2>
<P>partially update the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>PATCH /apis/storage.k8s.io/v1alpha1/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#patch-v1-meta">Patch</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="replace-volumeattachment-v1alpha1-storage-k8s-io">Replace</H2>
<P>replace the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>PUT /apis/storage.k8s.io/v1alpha1/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
<TR><TD>201<br /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>Created</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-volumeattachment-v1alpha1-storage-k8s-io">Delete</H2>
<P>delete a VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/storage.k8s.io/v1alpha1/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>gracePeriodSeconds</CODE></TD><TD>The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately.</TD></TR>
<TR><TD><CODE>orphanDependents</CODE></TD><TD>Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both.</TD></TR>
<TR><TD><CODE>propagationPolicy</CODE></TD><TD>Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground.</TD></TR>
</TBODY>
</TABLE>
<H3>Body Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>body</CODE><br /><I><a href="#deleteoptions-v1-meta">DeleteOptions</a></I></TD><TD></TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="delete-collection-volumeattachment-v1alpha1-storage-k8s-io">Delete Collection</H2>
<P>delete collection of VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>DELETE /apis/storage.k8s.io/v1alpha1/volumeattachments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#status-v1-meta">Status</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="-strong-read-operations-volumeattachment-v1alpha1-storage-k8s-io-strong-"><STRONG>Read Operations</STRONG></H2>
<H2 id="read-volumeattachment-v1alpha1-storage-k8s-io">Read</H2>
<P>read the specified VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1alpha1/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>exact</CODE></TD><TD>Should the export be exact. Exact export maintains cluster-specific fields like 'Namespace'.</TD></TR>
<TR><TD><CODE>export</CODE></TD><TD>Should this value be exported. Export strips fields that a user can not specify.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachment-v1alpha1-storage-k8s-io">VolumeAttachment</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="list-volumeattachment-v1alpha1-storage-k8s-io">List</H2>
<P>list or watch objects of kind VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1alpha1/volumeattachments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#volumeattachmentlist-v1alpha1-storage-k8s-io">VolumeAttachmentList</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-volumeattachment-v1alpha1-storage-k8s-io">Watch</H2>
<P>watch changes to an object of kind VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1alpha1/watch/volumeattachments/{name}</CODE>
<H3>Path Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>name</CODE></TD><TD>name of the VolumeAttachment</TD></TR>
</TBODY>
</TABLE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H2 id="watch-list-volumeattachment-v1alpha1-storage-k8s-io">Watch List</H2>
<P>watch individual changes to a list of VolumeAttachment</P>
<H3>HTTP Request</H3>
<CODE>GET /apis/storage.k8s.io/v1alpha1/watch/volumeattachments</CODE>
<H3>Query Parameters</H3>
<TABLE>
<THEAD><TR><TH>Parameter</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>continue</CODE></TD><TD>The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server the server will respond with a 410 ResourceExpired error indicating the client must restart their list without the continue field. This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.</TD></TR>
<TR><TD><CODE>fieldSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their fields. Defaults to everything.</TD></TR>
<TR><TD><CODE>includeUninitialized</CODE></TD><TD>If true, partially initialized resources are included in the response.</TD></TR>
<TR><TD><CODE>labelSelector</CODE></TD><TD>A selector to restrict the list of returned objects by their labels. Defaults to everything.</TD></TR>
<TR><TD><CODE>limit</CODE></TD><TD>limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.</TD></TR>
<TR><TD><CODE>pretty</CODE></TD><TD>If 'true', then the output is pretty printed.</TD></TR>
<TR><TD><CODE>resourceVersion</CODE></TD><TD>When specified with a watch call, shows changes that occur after that particular version of a resource. Defaults to changes from the beginning of history. When specified for list: - if unset, then the result is returned from remote storage based on quorum-read flag; - if it's 0, then we simply return what we currently have in cache, no guarantee; - if set to non zero, then the result is at least as fresh as given rv.</TD></TR>
<TR><TD><CODE>timeoutSeconds</CODE></TD><TD>Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.</TD></TR>
<TR><TD><CODE>watch</CODE></TD><TD>Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion.</TD></TR>
</TBODY>
</TABLE>
<H3>Response</H3>
<TABLE>
<THEAD><TR><TH>Code</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD>200<br /><I><a href="#watchevent-v1-meta">WatchEvent</a></I></TD><TD>OK</TD></TR>
</TBODY>
</TABLE>
<H1 id="volumeattachmentsource-v1alpha1-storage-k8s-io">VolumeAttachmentSource v1alpha1 storage.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>VolumeAttachmentSource</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#volumeattachmentsource-v1beta1-storage-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachmentspec-v1alpha1-storage-k8s-io">VolumeAttachmentSpec [storage/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>persistentVolumeName</CODE><BR /><I>string</I></TD><TD>Name of the persistent volume to attach.</TD></TR>
</TBODY>
</TABLE>
<H1 id="volumeerror-v1alpha1-storage-k8s-io">VolumeError v1alpha1 storage.k8s.io</H1>
<TABLE class="col-md-8">
<THEAD><TR><TH>Group</TH><TH>Version</TH><TH>Kind</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>storage.k8s.io</CODE></TD><TD><CODE>v1alpha1</CODE></TD><TD><CODE>VolumeError</CODE></TD></TR>
</TBODY>
</TABLE>
<DIV class="alert alert-success col-md-8"><I class="fa fa-toggle-right"></I> Other API versions of this object exist:
<a href="#volumeerror-v1beta1-storage-k8s-io">v1beta1</a>
</DIV>
<DIV class="alert alert-info col-md-8"><I class="fa fa-info-circle"></I> Appears In:
<UL>
<LI><a href="#volumeattachmentstatus-v1alpha1-storage-k8s-io">VolumeAttachmentStatus [storage/v1alpha1]</a></LI>
</UL>
</DIV>
<TABLE>
<THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD>
<TBODY>
<TR><TD><CODE>message</CODE><BR /><I>string</I></TD><TD>String detailing the error encountered during Attach or Detach operation. This string maybe logged, so it should not contain sensitive information.</TD></TR>
<TR><TD><CODE>time</CODE><BR /><I><a href="#time-v1-meta">Time</a></I></TD><TD>Time the error was encountered.</TD></TR>
</TBODY>
</TABLE>
</DIV>
</DIV>
<SCRIPT src="/js/jquery-3.2.1.min.js"></SCRIPT>
<SCRIPT src="jquery.scrollTo.min.js"></SCRIPT>
<SCRIPT src="/js/bootstrap-4.3.1.min.js"></SCRIPT>
<SCRIPT src="navData.js"></SCRIPT>
<SCRIPT src="scroll.js"></SCRIPT>
</BODY>
</HTML>
Reference in New Issue View Git Blame Copy Permalink